This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

StructureDefinition: QICore-CommunicationRequest

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/communicationrequest-qicore-qicore-communicationrequest

Profile of CommunicationRequest for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.

This profile was published on Fri, Feb 27, 2015 00:00+1100 as a draft by Health Level Seven, Inc. - CQI WG.

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from CommunicationRequest.

unable to summarise extension (wrong count)

NameFlagsCard.TypeDescription & Constraintsdoco
.. CommunicationRequest 1..1CommunicationRequestA request for information to be sent to a receiver
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... communicationrequest-orderedBy 0..*Practitioner, Organization, Device, PatientExtension
... communicationrequest-reasonRejected 0..*CodeableConceptExtension
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierUnique identifier
... category S0..1CodeableConceptMessage category
... sender S0..1practitioner-qicore-qicore-practitioner, patient-qicore-qicore-patient, device-qicore-qicore-device, relatedperson-qicore-qicore-relatedperson, organization-qicore-qicore-organizationMessage sender
... recipient S0..*patient-qicore-qicore-patient, device-qicore-qicore-device, relatedperson-qicore-qicore-relatedperson, practitioner-qicore-qicore-practitionerMessage recipient
... payload 0..*Message payload
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... content[x] 1..1string, Attachment, ResourceMessage part content
... medium 0..*CodeableConceptCommunication medium
... requester 0..1patient-qicore-qicore-patient, practitioner-qicore-qicore-practitioner, relatedperson-qicore-qicore-relatedpersonRequester of communication
... status ?! S0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed
Binding: CommunicationRequestStatus (required)
... encounter S0..1encounter-qicore-qicore-encounterEncounter leading to message
... scheduledTime 0..1dateTimeWhen scheduled
... reason 0..*CodeableConceptIndication for message
... orderedOn S0..1dateTimeWhen ordered or proposed
... subject S0..1PatientFocus of message
... priority 0..1CodeableConceptMessage urgency

todo

This structure is derived from CommunicationRequest.

unable to summarise extension (wrong count)

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. CommunicationRequest 1..1CommunicationRequestA request for information to be sent to a receiver
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... communicationrequest-orderedBy 0..*Practitioner, Organization, Device, PatientExtension
... communicationrequest-reasonRejected 0..*CodeableConceptExtension
... modifierExtension 0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierUnique identifier
... category S0..1CodeableConceptMessage category
... sender S0..1practitioner-qicore-qicore-practitioner, patient-qicore-qicore-patient, device-qicore-qicore-device, relatedperson-qicore-qicore-relatedperson, organization-qicore-qicore-organizationMessage sender
... recipient S0..*patient-qicore-qicore-patient, device-qicore-qicore-device, relatedperson-qicore-qicore-relatedperson, practitioner-qicore-qicore-practitionerMessage recipient
... payload 0..*Message payload
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... content[x] 1..1string, Attachment, ResourceMessage part content
... medium 0..*CodeableConceptCommunication medium
... requester 0..1patient-qicore-qicore-patient, practitioner-qicore-qicore-practitioner, relatedperson-qicore-qicore-relatedpersonRequester of communication
... status ?! S0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | failed
Binding: CommunicationRequestStatus (required)
... encounter S0..1encounter-qicore-qicore-encounterEncounter leading to message
... scheduledTime 0..1dateTimeWhen scheduled
... reason 0..*CodeableConceptIndication for message
... orderedOn S0..1dateTimeWhen ordered or proposed
... subject S0..1PatientFocus of message
... priority 0..1CodeableConceptMessage urgency

XML Template

JSON Template

todo

 

Other representations of profile: (todo)

Terminology Bindings

PathNameConformanceValueSet
CommunicationRequest.languageLanguagerequiredhttp://tools.ietf.org/html/bcp47
CommunicationRequest.statusCommunicationRequestStatusrequiredCommunicationRequestStatus

Constraints

IdPathNameDetails
.