Clinical order and service request
Record what was requested, by whom and why, and connect it to who performed it and what the result was, so that no request is lost or misread.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Order What was requested and by whom.
Request
Request details, ordering practitioner and signature.
Request details
Requested service, priority, ordering practitioner and encounter.
- Which test, procedure or referral was requested in this order, and with what priority?
- Who placed this order, when and in which encounter?
Signature
Verbal orders and their later signature.
- Was this order given verbally, and who signed it later and when?
Fulfilment Who performs the order and what came back.
Status and results
Status changes, performers, specimens and results.
Status
Current status, performer and changes.
- What is the current status of this order, and which party is performing it?
- Who cancelled or changed this order, and why?
Results
Results, specimens and acknowledgment.
- Which results or reports answer this order?
- Which specimens were collected for this order?
- Was the result of this order acknowledged by the ordering practitioner or a delegate?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseHCP
- Industry
- Healthcare provider
- Tags
- EM-HCP-05W-INDsubjectServiceRequestOrderDetailReferralOrderStatusChangePerformerAssignment
What it is Filled
A request by an authorized practitioner for a diagnostic test, imaging, a procedure, a consultation or a referral, with its status, the performing party and the link to results. Medication prescriptions are a separate contour.
Why it exists Filled
Record what was requested, by whom and why, and connect it to who performed it and what the result was, so that no request is lost or misread.
Distinguishing features Filled
- An order records the request, and its performance and results are linked records.
- Verbal orders are recorded and signed later.
- Results reference the order they answer.
- Medication prescriptions are recorded in a separate contour.
What robots and AI may and may not do Filled
Must not
- Place, change or cancel clinical orders.
- Interpret results for patients or give clinical advice.
- Attach a result to an order without a reliable match.
Only with a human decision
- Only authorized practitioners place and sign clinical orders.
- Results without a matching order must be resolved by laboratory or clinical staff.
May
- Track open orders and results that wait for acknowledgment.
- Check that orders name the ordering practitioner and time.
- Route orders to the performing department as configured.
Moral aspects Filled
- Results that are never acknowledged can cause harm through delayed treatment.
- Order data reveals sensitive health conditions.
Who is affected
- Patients
- Ordering practitioners
- Laboratory and imaging staff
Owners Filled
Steward
The medical director who answers for ordering and result follow-up.
Master systems
- Electronic health record system
- Laboratory information system
- Radiology information system
Links to other meta-models Filled
neighbor
- EM-HCP-03
- EM-HCP-04
- EM-HCP-08
- EM-HCP-02
- EM-HCP-06
references
- WM-MAT-007 - conceptual-candidate
- WM-ACT-047 - conceptual-candidate
- WM-LIV-023 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- An order has an identifier unique within the ordering system, and often a second identifier from the performing system.
- Each order references one patient record and the ordering practitioner.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- Records show what was requested, its priority, the ordering practitioner, the status and the performer.
- An order must be distinguished from its result, from an appointment and from a charge.
Capabilities and actions required Filled
- The contour supports order tracking, result routing and acknowledgment follow-up.
Hazards and failure modes required Filled
- Mismatched results can lead to wrong clinical decisions.
- Lost referrals can delay diagnosis.
Standards and interfaces optional Filled
- HL7 International publishes the FHIR ServiceRequest resource.
- Regenstrief Institute publishes LOINC codes for laboratory tests and clinical observations.
Context of use required Filled
- The contour is used for laboratory tests, imaging, procedures and referrals.
- Ordering rights depend on professional licensing in each jurisdiction.
Sources Filled
- HL7 FHIR: ServiceRequest resource
- IHE laboratory and radiology workflow profiles
- LOINC: codes for laboratory and clinical observations
- HL7 FHIR R4 ServiceRequest resource - Checked live (HTTP 200) on 2026-10-21.
- LOINC - Checked live (HTTP 200) on 2026-10-21.
Open questions
- How is an order kept separate from its fulfilment by another department or provider?
- How are verbal orders recorded and later signed?
- How is a result linked to the order without the order changing its meaning?
- Settle the boundary and the reuse, extend or new decision against the current specifications.
- Confirm the semantic crosswalk, rights and source mastership.
- Choose immutable references and run fixture checks before claiming publication readiness.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-hcp-05/brief.json, ver-cy/world-models/card-supplements/em-hcp-05.json