Union of http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication and http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication

This is the set of resources that conform to either of the profiles QICore Communication (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication) and QICore Communication (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-communication). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication 0..*A record of information transmitted from a sender 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: ?? (preferred): A human language.
... text 0..1NarrativeText summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierUnique identifier
... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(Resource)Request fulfilled by this communication
... partOf Σ0..*Reference(Resource)Part of this action
... inResponseTo 0..*Reference(Communication)Reply to
... status ?!Σ1..1codeleft: (QI) preparation | in-progress | on-hold | stopped | completed | entered-in-error | unknown; right: (QI) preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: ?? (required): The status of the communication.
... statusReason Σ0..1CodeableConceptReason for current status
Binding: ?? (example): Codes for the reason why a communication did not happen.
... category 0..*CodeableConceptMessage category
Binding: ?? (example): Codes for general categories of communications such as alerts, instructions, etc.
... priority Σ0..1coderoutine | urgent | asap | stat
Binding: ?? (required): Codes indicating the relative importance of a communication.
... medium 0..*CodeableConceptA channel of communication
Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject Σ0..1Reference(QICore Patient | Group | #sd-qicore-patient-qicore-patient)(QI) Focus of message
... topic 0..1CodeableConcept(QI) Description of the purpose/content
Binding: ?? (preferred)
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
.... text Σ0..1stringPlain text representation of the concept
... about 0..*Reference(Resource)Resources that pertain to this communication
... encounter Σ0..1Reference(Encounter)Encounter created as part of
... sent 0..1dateTime(QI) When sent
... received 0..1dateTime(QI) When received
... recipient 0..*Reference(QICore Device | US Core Implantable Device Profile | QICore Organization | QICore Patient | QICore Practitioner | QICore RelatedPerson | Group), Reference(QICore CareTeam | QICore Device | US Core Implantable Device Profile | QICore Organization | QICore Patient | QICore Practitioner | QICore RelatedPerson | Group)(QI) Message recipient
... sender 0..1Reference(QICore Device | US Core Implantable Device Profile | QICore Organization | QICore Patient | QICore Practitioner | QICore RelatedPerson | #sd-qicore-device-qicore-device)(QI) Message sender
... reasonCode Σ0..*CodeableConceptIndication for message
Binding: ?? (example): Codes for describing reasons for the occurrence of a communication.
... reasonReference Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Why was communication done?
... payload 0..*BackboneElementMessage payload
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... content[x] 1..1Message part content
..... contentStringstring
..... contentAttachmentAttachment
..... contentReferenceReference(Resource)
... note 0..*AnnotationComments made about the communication

doco Documentation for this format