FHIR Tooling Extensions IG
0.2.0 - Release 0.2.0 International flag

FHIR Tooling Extensions IG, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/FHIR/fhir-tools-ig/ and changes regularly. See the Directory of published versions

Logical Model: CDSHookOrderSignContext - Detailed Descriptions

Draft as of 2024-10-23 Maturity Level: 2

Definitions for the CDSHookOrderSignContext logical model.

Guidance on how to interpret the contents of this table can be found here

0. CDSHookOrderSignContext
ShortThe context for the order-sign hook
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CDSHookOrderSignContext.userId
Definition

For this hook, the user is expected to be of type Practitioner, PractitionerRole, Patient, or RelatedPerson. Patient or RelatedPerson are appropriate when a patient or their proxy are viewing the record. For example, Practitioner/abc or Patient/123.

ShortThe id of the current user. Must be in the format [ResourceType]/[id].
Control1..1
Typeurl
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CDSHookOrderSignContext.patientId
Definition

The FHIR Patient.id of the current patient in context

ShortThe FHIR Patient.id of the current patient in context
Control1..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CDSHookOrderSignContext.encounterId
Definition

The FHIR Encounter.id of the current encounter in context

ShortThe FHIR Encounter.id of the current encounter in context
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CDSHookOrderSignContext.draftOrders
Definition

FHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status

ShortFHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status
Control1..1
TypeBundle
ID ExpectationId may or not be present (this is the default for elements but not resources)

Guidance on how to interpret the contents of this table can be found here

0. CDSHookOrderSignContext
Definition

The context (hook specific)


Base definition for all types defined in FHIR type system.

ShortThe context for the order-sign hookBase for all types and resources
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CDSHookOrderSignContext.userId
Definition

For this hook, the user is expected to be of type Practitioner, PractitionerRole, Patient, or RelatedPerson. Patient or RelatedPerson are appropriate when a patient or their proxy are viewing the record. For example, Practitioner/abc or Patient/123.

ShortThe id of the current user. Must be in the format [ResourceType]/[id].
Control1..1
Typeurl
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CDSHookOrderSignContext.patientId
Definition

The FHIR Patient.id of the current patient in context

ShortThe FHIR Patient.id of the current patient in context
Control1..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CDSHookOrderSignContext.encounterId
Definition

The FHIR Encounter.id of the current encounter in context

ShortThe FHIR Encounter.id of the current encounter in context
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CDSHookOrderSignContext.draftOrders
Definition

FHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status

ShortFHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status
Control1..1
TypeBundle
ID ExpectationId may or not be present (this is the default for elements but not resources)

Guidance on how to interpret the contents of this table can be found here

0. CDSHookOrderSignContext
Definition

The context (hook specific)

ShortThe context for the order-sign hook
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. CDSHookOrderSignContext.userId
Definition

For this hook, the user is expected to be of type Practitioner, PractitionerRole, Patient, or RelatedPerson. Patient or RelatedPerson are appropriate when a patient or their proxy are viewing the record. For example, Practitioner/abc or Patient/123.

ShortThe id of the current user. Must be in the format [ResourceType]/[id].
Control1..1
Typeurl
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. CDSHookOrderSignContext.patientId
Definition

The FHIR Patient.id of the current patient in context

ShortThe FHIR Patient.id of the current patient in context
Control1..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. CDSHookOrderSignContext.encounterId
Definition

The FHIR Encounter.id of the current encounter in context

ShortThe FHIR Encounter.id of the current encounter in context
Control0..1
Typeid
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. CDSHookOrderSignContext.draftOrders
Definition

FHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status

ShortFHIR Bundle of MedicationRequest, NutritionOrder, ServiceRequest, VisionPrescription with draft status
Control1..1
TypeBundle
ID ExpectationId may or not be present (this is the default for elements but not resources)