order-dispatch.md

order-dispatch.md

order-dispatch

Metadata	Value
specificationVersion	2.0
hookVersion	1.0
hookMaturity	0 - Draft

Workflow

The order-dispatch hook fires when a practitioner is selecting a candidate performer for a pre-existing order that was not tied to a specific performer. For example, selecting an imaging center to satisfy a radiology order, selecting a cardiologist to satisfy a referral, etc. This hook only occurs in situations where the order is agnostic as to who the performer should be and a separate process (which might be performed by back-office staff, a central dispatch service, or even the ordering clincian themselves at a later time) is used to select and seek action by a specific performer. It is possible that the same order might be dispatched multiple times, either because initial selected targets refuse or are otherwise unable to satisfy the order, or because the performer is only asked to perform a 'portion' of what's authorized (the first monthly lab test of a year-long set, the first dispense of a 6 month order, etc.)

This "request for fulfillment" process is typically represented in FHIR using Task. This resource allows indication of the order to be acted upon, who is being asked to act on it, the time-period in which they're expected to act, and any limitations/qualifications to how much of the order should be acted on.

Decision support that may be relevant for this hook might include information related to coverage, prior-authorization and/or in-network/out-of-network evaluations with respect to the chosen performer; determination of practitioner availability or qualification; enforcement/guidance with respect to patient performer practitioners; etc.

Context

Define context values that are available when this hook occurs, and indicate whether they must be provided, and whether they are available for parameterizing prefetch templates.

Field	Optionality	Prefetch Token	Type	Description
patientId	REQUIRED	Yes	string	The FHIR Patient.id of the current patient in context
order	REQUIRED	Yes	string	The FHIR local reference for the Request resource for which fulfillment is sought E.g. ServiceRequest/123
performer	REQUIRED	Yes	string	The FHIR local reference for the Practitioner, PractitionerRole, Organization, CareTeam, etc. who is being asked to execute the order
task	OPTIONAL	No	object	DSTU2/STU3/R4 - Task instance that provides a full description of the fulfillment request - including the timing and any constraints on fulfillment

Examples

"context":{
  "patientId" : "1288992",
  "order" : "ServiceRequest/proc002",
  "performer" : "Organization/some-performingorganization",
  "task" : {
    "resourceType" : "Task",
    "status" : "draft",
    "intent" : "order",
    "code" : {
      "coding" : [{
        "system" : "",
        "code" : ""
      }]
    },
    "focus" : {
      "reference" : "ServiceRequest/proc002"
    },
    "for" : {
      "reference" : "Patient/1288992"
    },
    "authoredOn" : "2016-03-10T22:39:32-04:00",
    "lastModified" : "2016-03-10T22:39:32-04:00",
    "requester": {
      "reference" : "Practitioner/123"
    },
    "owner" : {
      "reference" : "Organziation/some-performingorganization"
    }
  }
}

Change Log

Version	Description
1.0	Initial Release