Union of http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication and http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication

This is the set of resources that conform to either of the profiles MedComCareCommunication (http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication) and MedComCareCommunication (http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-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 C0..*A record of information transmitted from a sender to a receiver
Constraints: medcom-careCommunication-5, medcom-careCommunication-6, medcom-careCommunication-7, medcom-careCommunication-8, medcom-careCommunication-9
... 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 S0..1Narrativeleft: Text summary of the resource, for human interpretation; right: The narrative text SHALL always be included when exchanging a MedCom FHIR Bundle.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... status S1..1codegenerated | extensions | additional | empty
Binding: ?? (required): The status of a resource narrative.
.... div SC1..1xhtmlLimited xhtml content
Constraints: txt-1, txt-2
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionExtension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣC1..1IdentifierThe communication identifier
Constraints: medcom-uuidv4
.... extension 0..*ExtensionAdditional content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: ?? (required): Identifies the purpose for this identifier, if known .
.... type Σ0..1CodeableConceptDescription of identifier
Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
.... system Σ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value SΣ1..1stringThe value that is unique
Example General: 123456
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... 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 ?!SΣ1..1codepreparation | 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 S1..1CodeableConceptThe category (Danish: kategori) describes the overall content of the message.
Binding: ?? (required)
.... extension 0..*ExtensionAdditional content defined by implementations
.... coding SΣ0..*CodingCode defined by a terminology system
..... extension 0..*ExtensionAdditional content defined by implementations
..... system SΣ1..1uriIdentity of the terminology system
..... version Σ0..1stringVersion of the system - if relevant
..... code SΣ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... priority SΣ0..1codeShall be present if the message priority is known to be ASAP, but is only allowed when the category is 'regarding referral', see medcom-careCommunication-5
Binding: ?? (required)
... medium 0..*CodeableConceptA channel of communication
Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject SΣ1..1Reference(MedComCorePatient | #sd-medcom-core-patient-medcom-core-patient) {b}Focus of message
... topic S0..1CodeableConceptThe topic (Danish: emne) may be added as a supplement to the category. Topic must be added in the text-element.
Binding: ?? (example): Codes describing the purpose or content of the communication.
.... extension 0..*ExtensionAdditional content defined by implementations
.... coding Σ0..*CodingCode defined by a terminology system
.... text SΣ1..1stringPlain text representation of the concept
... about 0..*Reference(Resource)Resources that pertain to this communication
... encounter SΣ0..1Reference(MedComCoreEncounter | #sd-medcom-core-encounter-medcom-core-encounter) {b}Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
... sent 0..1dateTimeWhen sent
... received 0..1dateTimeWhen received
... recipient S0..*Reference(MedComCorePractitionerRole | MedComCoreCareTeam | #sd-medcom-core-practitionerrole-medcom-core-practitionerrole) {b}Describes a more specific receiver than the MessageHeader.destination.reciever, called a recipient. It may be a careteam a homecare group in the municipality or a named general practitioner.
... sender 0..1Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)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 1..*BackboneElementEach payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included.
.... extension 0..*ExtensionExtension
.... 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