Encounter-based imaging starts from the care event, not the order queue
Point-of-care ultrasound, bedside imaging, and emergency capture workflows often happen before the organization has created a traditional imaging order. The orchestration problem is therefore not “how do I schedule this?” but “how do I safely capture context while care is already underway?”
Encounter-based imaging context flow
Loading diagram...
The actor view is especially useful because it makes the encounter manager and results aggregator explicit. That is a reminder that encounter-based imaging usually needs more context assembly than a straightforward order-to-modality path.
IHE Encounter-Based Imaging Workflow supplement
IHE supplement describing actors and transactions for imaging that begins in the encounter rather than in a pre-ordered schedule.
Read the EBIW supplementA safe design includes a reconciliation lane before durable commit
Encounter-based workflows are useful precisely because they are fast, but that speed increases the chance of partial demographics, missing accessions, or a study being attached to the wrong encounter. The orchestrator should treat those conditions as repairable states rather than as acceptable final outputs.
Reconciliation checks that matter in encounter-based workflows
| Check | Purpose | Failure action |
|---|---|---|
| Patient identifier match | Make sure the study belongs to the intended patient | Hold for manual review or re-resolution |
| Encounter linkage | Attach the study to the active care episode | Create a repair task before final publication |
| Procedure labeling | Classify the study well enough for routing and follow-up | Route to correction queue or enrich from clinical context |
FHIR Encounter is useful here because it gives the orchestrator a resource-level contract for the care episode even when the imaging action did not start from a formal order. That lets the system stabilize the context before it exposes the study to downstream readers or analytics.
Encounter - FHIR R4
FHIR Encounter documents the care setting and status model that encounter-based workflows need to preserve.
Review EncounterWhat is AWS HealthLake?
HealthLake provides the managed FHIR store that commonly holds the normalized encounter and patient context used for reconciliation.
Review HealthLake in the developer guideAfter reconciliation, publish a stable study contract instead of a temporary staging record
Once the patient and encounter have been reconciled, the orchestrator should publish a stable contract for downstream retrieval and reporting. In a FHIR-aware architecture, ImagingStudy is a useful bridge because it carries study metadata and access endpoints while still leaving pixel delivery to DICOMweb or other image services.
Encounter-linked ImagingStudy example
A simplified FHIR ImagingStudy showing how the reconciled study can point back to the encounter and forward to a retrieval endpoint.
Click on an annotation to highlight it in the JSON
ImagingStudy - FHIR R4
FHIR ImagingStudy defines the study and series metadata bridge used after reconciliation in encounter-based workflows.
Review ImagingStudyKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.