QICoreCommunication

An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency that was notified about a reportable condition.

= Must Support, = Is Modifier, = QiCore defined extension

FieldCard.TypeDescription
identifier0..*List<Identifier>Business identifiers assigned to this communication by the performer or other systems which remain constant as the resource is updated and propagates from server to server.
instantiatesCanonical0..*List<canonical>The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.
instantiatesUri0..*List<String>The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Communication.
basedOn0..*List<Resource>An order, proposal or plan fulfilled in whole or in part by this Communication.
partOf0..*List<Resource>Part of this action.
inResponseTo0..*List<QICoreCommunication>Prior communication that this communication is in response to.
status1..1StringThe status of the transmission.
Binding: The status of the communication. (required)
statusReason0..1ConceptCaptures the reason for the current state of the Communication.
Binding: Codes for the reason why a communication did not happen. (example)
category0..*List<Concept>The type of message conveyed such as alert, notification, reminder, instruction, etc.
Binding: Codes for general categories of communications such as alerts, instructions, etc. (example)
priority0..1StringCharacterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine.
Binding: Codes indicating the relative importance of a communication. (required)
medium0..*List<Concept>A channel that was used for this communication (e.g. email, fax).
Binding: Codes for communication mediums such as phone, fax, email, in person, etc. (example)
subject0..1QICorePatient | GroupThe patient or group that was the focus of this communication.
topic0..1ConceptDescription of the purpose/content, similar to a subject line in an email.
Binding: Codes describing the purpose or content of the communication. (example)
about0..*List<Resource>Other resources that pertain to this communication and to which this communication should be associated.
encounter0..1QICoreEncounterThe Encounter during which this Communication was created or to which the creation of this record is tightly associated.
sent0..1DateTimeThe time when this communication was sent.
received0..1DateTimeThe time when this communication arrived at the destination.
recipient0..*List<QICoreDevice | QICoreOrganization | QICorePatient | QICorePractitioner | QICoreRelatedPerson | Group>The entity (e.g. person, organization, clinical information system, care team or device) which was the target of the communication. If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time).
sender0..1QICoreDevice | QICoreOrganization | QICorePatient | QICorePractitioner | QICoreRelatedPersonThe entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
reasonCode0..*List<Concept>The reason or justification for the communication.
Binding: Codes for describing reasons for the occurrence of a communication. (example)
reasonReference0..*List<QICoreCondition | QICoreObservation | QICoreDiagnosticReportLab | DocumentReference>Indicates another resource whose existence justifies this communication.
payload0..*List<payload>Text, attachment(s), or resource(s) that was communicated to the recipient.
note0..*List<Annotation>Additional notes or commentary about the communication by the sender, receiver or other interested parties.