Guidance

Reference Guidance for use of the Service Request profile can be found here.

• See the Social Determinants of Health (SDOH) Guidance Page for more information when exchanging Social Determinants of Health (SDOH) Service Requests.
• The ServiceRequest.category binding must support at a minimum the US Core ServiceRequest Category Codes. However, this valueset can be treated as extensible and other category codes can be used instead.
• The ServiceRequest.code valueset is broad to accommodate a wide variety of use cases and should be constrained to a subset for a particular use case or domain. (for example, LOINC for laboratory orders.)
• The ServiceRequest.subject is Must Support with Must Support reference to QI Core Patient

To create an expression specifically requesting information that a ServiceRequest intentionally did not occur for a medical, patient or system reason, use the profile QICore-Servicenotrequested.

The ServiceRequest and ServiceNotRequested profiles represent the positive and negative statements for a service request. To ensure instances retrieved meet positive intent, applications should check the status and doNotPerform elements as illustrated in this example:

define ServiceRequest:
  [ServiceRequest] SR
    where SR.status in { 'draft', 'active', 'on-hold', 'completed' }
      and SR.doNotPerform is not true

The following example illustrates the use of the ServiceRequest profile:

define "Intervention Comfort Measures":
  (["ServiceRequest": "Comfort Measures"] P
    where P.intent = 'order'
      and P.doNotPerform is not true
  )
    union (["Procedure": "Comfort Measures"] InterventionPerformed
      where InterventionPerformed.status in {'completed', 'in-progress'}
    )

See the patterns page for implementation and usage patterns.

Examples