Automation index
How much of a Gastroenterologist’s job can AI already do?
A colonoscopy report comes earlier. Putting the scope in and not perforating do not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Gastroenterologist
22%
AI can already do 22% of this job.
#442 / 773
View rankingGastroenterologist
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Read endoscopies, labs and the transit study.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 48% | +7.7 |
Colonoscopy, gastroscopy and ERCP.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 10% | +2.2 |
IBD, hepatitis and reflux plans.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Abdomen clinic, occult blood and the fear of cancer.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
GI emergencies and the bleed that does not stop.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 18% | +2.9 |
Consent, perforation and signing the procedure.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 12% | +1.7 |
| Total | 100% | 22% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- do colonoscopies
- gastroscopy
- treat IBD
- ERCP
- GI clinic
- hepatitis plans
- GI bleed
- read endoscopies
Sources for this job· O*NET 29-1216.00· ESCO/ISCO 2212
IS WORK OVER?
Backend developer
27%
#153 / 773
View rankingBackend developer
Where the time goes
Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.
The time saving for each task is estimated separately.
| Task | Share | AI | Points |
|---|---|---|---|
Endpoint, the contract and the test.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 12% | +1.9 |
| Total | 100% | 27% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512