ServiceRequest
Readiness: In review.
Open ServiceRequest profile on Simplifier
Profile base: FHIR R4 ServiceRequest. The selected no-basis 2.2.2 package has no ServiceRequest profile.
Design choices
DigiDOT reuses one request model for recall, specified treatment, follow-up and dental referrals. A request can exist before a booking and can be fulfilled through more than one visit. Its clinical scope determines when it is complete.
General recall is an exception to the specific-service coding requirement: the recall category and timing identify the need without an invented procedure code. For specific services, the current profile uses a SNOMED CT planned-procedure Situation. That is a DigiDOT coding convention, not a requirement imposed by FHIR or EHDS. The shared coding rationale is in Clinical coding.
Ongoing recall and targeted follow-up
In the recall-to-treatment scenario, annual recall and a restoration request coexist. The restoration fulfils the treatment request; it does not finish the ongoing recall plan.
The schedule records a clinical decision, not the EHR's booking algorithm. For example, a first examination due on 16 September followed by a twelve-month interval has that date as its anchor. A late appointment does not silently move the original anchor. Changing the interval is an explicit plan change whose earlier state must remain traceable. The intervals in the examples are illustrative, not default clinical recommendations.
A targeted three-month follow-up specifies the service to repeat. A single due date, a finite course and an ongoing recurrence are different intentions; use the representation defined by the profile and the actual decision. See the complete scenario JSON for the recurring plan.
Declining an offer of dental care
| Patient decision or event | Workflow |
|---|---|
| Explicit refusal ends the offer or recall before fulfilment | Revoke the relevant request and record the decision in an attributed, dated note. |
| Temporary pause, with resumption intended | Keep the request on hold with the agreed follow-up. |
| Appointment cancelled, but care still wanted | Update the booking without automatically ending the request. |
| Patient does not attend | Record the Appointment no-show; this alone does not establish refusal of further care. |
The note should identify what was declined, the decision date, any stated reason and agreed follow-up. Preserve the original request and its history. Apply the decision to its actual scope: ending one request does not automatically end other care, health-group eligibility or organisational responsibility. A separate Consent record is not introduced for this workflow.
The declined-recall example, with its reference context, records a patient's decision to stop routine recall and arrange private care. It preserves the earlier schedule without treating it as an instruction for further bookings.
Recall automation must distinguish refusal from other reasons for revocation. The status alone cannot do that. A later offer is a new request; automatic selection by refusal reason needs an agreed structured representation or workflow beyond this example.
Dental referrals
The current assessment reuses ServiceRequest for a referral requesting a specified dental service, rather than introducing a separate referral profile. The requested service, its clinical reason, the retained letter and actual sending are different information.
The referral example requests a restoration. The complete referral and disclosure collection also shows the supporting records and note of actual sending. Sending the letter does not complete the requested treatment; receipt, acceptance, booking and fulfilment remain separate events.
An uncoded historical letter can be retained as a document without inventing a requested service or classifying it as routine recall. Referenced medication information keeps its original source and scope; imported SFM/PLL data must not be relabelled as a local reported-medication statement. See Medication and allergy and Documents and attachments.
EHDS and later FHIR versions
The EHDS Service request model describes the requested service, reason and target anatomy. It does not require DigiDOT's planned-Situation coding. That convention needs an explicit terminology mapping or reassessment for European exchange. A broader plan with goals and several activities may instead need EHDS Care plan mapping; one recall request does not claim that wider scope.
FHIR R5 ServiceRequest changes code, reasons and supporting information to CodeableReference and introduces a BodyStructure option. The R6 development model changes anatomy further. These affect the coding slices and anatomical mapping, not the distinction between an intended service and delivered care. See the shared assessment.
Further examples
- Planned replantation as a concept or as an expression.
- Proposed restoration.
- Restoration with a separate clinical reason.
- Profile connections shows the directions of request, booking and treatment links; References and identifiers defines their common representation.