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

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

An Extension

R5: Communication.instantiatesUri (new:uri)

Element Communication.instantiatesUri has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.instantiatesUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

R5: Communication.inResponseTo (new:Reference(Communication))

Element Communication.inResponseTo has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.inResponseTo has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: Communication.priority (new:code)

Element Communication.priority has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.priority has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress.

R5: Communication.about (new:Reference(Resource))

Element Communication.about has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.about has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference.

An Extension

R5: Communication.status additional codes

Element Communication.status is mapped to FHIR STU3 element Communication.status as RelatedTo. Element Communication.status is mapped to FHIR STU3 element Communication.notDone as SourceIsBroaderThanTarget. The mappings for Communication.status do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

The status of the transmission.

This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

The codes SHALL be taken from EventStatus http://hl7.org/fhir/ValueSet/event-status|3.0.2
(required to http://hl7.org/fhir/ValueSet/event-status|3.0.2)

The status of the communication.

If true, indicates that the described communication event did not actually occur.

This element is labeled as a modifier because it marks the communication as a communication that did not occur. The more attributes are populated, the more constrained the negated statement is.

Creating a Communication where notDone is true is intended for situations where there's a need for a specific statement in the record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task.

R5: Communication.instantiatesUri (new:uri)

Element Communication.instantiatesUri has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.instantiatesUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

R5: Communication.inResponseTo (new:Reference(Communication))

Element Communication.inResponseTo has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.inResponseTo has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: Communication.priority (new:code)

Element Communication.priority has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.priority has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress.

R5: Communication.about (new:Reference(Resource))

Element Communication.about has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.about has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference.

R5: Communication.status additional codes

Element Communication.status is mapped to FHIR STU3 element Communication.status as RelatedTo. Element Communication.status is mapped to FHIR STU3 element Communication.notDone as SourceIsBroaderThanTarget. The mappings for Communication.status do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

R5: Communication.instantiatesCanonical additional types (canonical(http://hl7.org/fhir/StructureDefinition/PlanDefinition), canonical(http://hl7.org/fhir/StructureDefinition/ActivityDefinition), canonical(http://hl7.org/fhir/StructureDefinition/Measure), canonical(http://hl7.org/fhir/StructureDefinition/OperationDefinition), canonical(http://hl7.org/fhir/StructureDefinition/Questionnaire))

Element Communication.instantiatesCanonical is mapped to FHIR STU3 element Communication.definition as SourceIsBroaderThanTarget. The mappings for Communication.instantiatesCanonical do not cover the following types: canonical.

R5: Communication.basedOn additional types from child elements (display, identifier, reference, type)

Element Communication.basedOn is mapped to FHIR STU3 element Communication.basedOn as SourceIsBroaderThanTarget. The mappings for Communication.basedOn do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.basedOn with unmapped reference targets: Resource. This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc.

R5: Communication.partOf additional types from child elements (display, identifier, reference, type)

Element Communication.partOf is mapped to FHIR STU3 element Communication.partOf as SourceIsBroaderThanTarget. The mappings for Communication.partOf do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.partOf with unmapped reference targets: Resource. The event the communication was part of - e.g. if you disclosed as "part" of counselling, it would be partOf that Procedure.

R5: Communication.subject additional types from child elements (display, identifier, reference, type)

Element Communication.subject is mapped to FHIR STU3 element Communication.subject as SourceIsBroaderThanTarget. The mappings for Communication.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.subject with unmapped reference targets: Group, Patient.

R5: Communication.recipient

Element Communication.recipient is mapped to FHIR STU3 element Communication.recipient as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.recipient with unmapped reference targets: CareTeam, Device, Endpoint, Group, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. 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).

R5: Communication.topic additional types (CodeableConcept) additional types from child elements (coding, text)

Element Communication.topic is mapped to FHIR STU3 element Communication.topic as RelatedTo. The mappings for Communication.topic do not cover the following types: CodeableConcept. The mappings for Communication.topic do not cover the following types based on type expansion: coding, text. Communication.topic.text can be used without any codings.

R5: Communication.encounter additional types from child elements (display, identifier, reference, type)

Element Communication.encounter is mapped to FHIR STU3 element Communication.context as SourceIsBroaderThanTarget. The mappings for Communication.encounter do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.encounter with unmapped reference targets: Encounter. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.

R5: Communication.sender

Element Communication.sender is mapped to FHIR STU3 element Communication.sender as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.sender with unmapped reference targets: CareTeam, Device, Endpoint, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.

R5: Communication.payload.content[x] additional types (CodeableConcept)

Element Communication.payload.content[x] is mapped to FHIR STU3 element Communication.payload.content[x] as SourceIsBroaderThanTarget. The mappings for Communication.payload.content[x] do not cover the following types: CodeableConcept. The target context Communication.payload.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Communication.payload. The standard extension alternate-reference has been mapped as PART of the representation of FHIR R5 element Communication.payload.content[x] with unmapped reference targets: Resource. Source element Communication.payload.content[x] has unmapped reference types. While the target element Communication.payload.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

If the content isn't codified, contentCodeableConcept.text can be used.

When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

R5: Communication.payload.content[x] additional types (CodeableConcept)

Element Communication.payload.content[x] is mapped to FHIR STU3 element Communication.payload.content[x] as SourceIsBroaderThanTarget. The mappings for Communication.payload.content[x] do not cover the following types: CodeableConcept. The target context Communication.payload.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Communication.payload. The standard extension alternate-reference has been mapped as PART of the representation of FHIR R5 element Communication.payload.content[x] with unmapped reference targets: Resource. Source element Communication.payload.content[x] has unmapped reference types. While the target element Communication.payload.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

If the content isn't codified, contentCodeableConcept.text can be used.

When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

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

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

Unless not suitable, these codes SHALL be taken from Common Languages
(extensible to http://hl7.org/fhir/ValueSet/languages|3.0.2)

A human language.

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

An Extension

R5: Communication.instantiatesUri (new:uri)

Element Communication.instantiatesUri has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.instantiatesUri has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

R5: Communication.inResponseTo (new:Reference(Communication))

Element Communication.inResponseTo has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.inResponseTo has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

R5: Communication.priority (new:code)

Element Communication.priority has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.priority has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress.

R5: Communication.about (new:Reference(Resource))

Element Communication.about has a context of Communication based on following the parent source element upwards and mapping to Communication. Element Communication.about has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference.

An Extension

R5: Communication.status additional codes

Element Communication.status is mapped to FHIR STU3 element Communication.status as RelatedTo. Element Communication.status is mapped to FHIR STU3 element Communication.notDone as SourceIsBroaderThanTarget. The mappings for Communication.status do not allow expression of the necessary codes, per the bindings on the source and target. This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

Identifiers associated with this Communication that are defined by business processes and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

A protocol, guideline, or other definition that was adhered to in whole or in part by this communication event.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.instantiatesCanonical additional types (canonical(http://hl7.org/fhir/StructureDefinition/PlanDefinition), canonical(http://hl7.org/fhir/StructureDefinition/ActivityDefinition), canonical(http://hl7.org/fhir/StructureDefinition/Measure), canonical(http://hl7.org/fhir/StructureDefinition/OperationDefinition), canonical(http://hl7.org/fhir/StructureDefinition/Questionnaire))

Element Communication.instantiatesCanonical is mapped to FHIR STU3 element Communication.definition as SourceIsBroaderThanTarget. The mappings for Communication.instantiatesCanonical do not cover the following types: canonical.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

An order, proposal or plan fulfilled in whole or in part by this Communication.

This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ReferralRequest, MedicationRequest, etc.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.basedOn additional types from child elements (display, identifier, reference, type)

Element Communication.basedOn is mapped to FHIR STU3 element Communication.basedOn as SourceIsBroaderThanTarget. The mappings for Communication.basedOn do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.basedOn with unmapped reference targets: Resource. This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Part of this action.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.partOf additional types from child elements (display, identifier, reference, type)

Element Communication.partOf is mapped to FHIR STU3 element Communication.partOf as SourceIsBroaderThanTarget. The mappings for Communication.partOf do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.partOf with unmapped reference targets: Resource. The event the communication was part of - e.g. if you disclosed as "part" of counselling, it would be partOf that Procedure.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The status of the transmission.

This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid.

The codes SHALL be taken from EventStatus
(required to http://hl7.org/fhir/ValueSet/event-status|3.0.2)

The status of the communication.

If true, indicates that the described communication event did not actually occur.

This element is labeled as a modifier because it marks the communication as a communication that did not occur. The more attributes are populated, the more constrained the negated statement is.

Creating a Communication where notDone is true is intended for situations where there's a need for a specific statement in the record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task.

Describes why the communication event did not occur in coded and/or textual form.

Codes for the reason why a communication was not done.

The type of message conveyed such as alert, notification, reminder, instruction, etc.

There may be multiple axes of categorization and one communication may serve multiple purposes.

Codes for general categories of communications such as alerts, instruction, etc.

A channel that was used for this communication (e.g. email, fax).

Codes for communication mediums such as phone, fax, email, in person, etc.

The patient or group that was the focus of this communication.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.subject additional types from child elements (display, identifier, reference, type)

Element Communication.subject is mapped to FHIR STU3 element Communication.subject as SourceIsBroaderThanTarget. The mappings for Communication.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.subject with unmapped reference targets: Group, Patient.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The entity (e.g. person, organization, clinical information system, or device) which was the target of the communication. If receipts need to be tracked by individual, a separate resource instance will need to be created for each recipient.  Multiple recipient communications are intended where either a receipt(s) is not tracked (e.g. a mass mail-out) or is captured in aggregate (all emails confirmed received by a particular time).

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.recipient

Element Communication.recipient is mapped to FHIR STU3 element Communication.recipient as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.recipient with unmapped reference targets: CareTeam, Device, Endpoint, Group, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. 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).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The resources which were responsible for or related to producing this communication.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.topic additional types (CodeableConcept) additional types from child elements (coding, text)

Element Communication.topic is mapped to FHIR STU3 element Communication.topic as RelatedTo. The mappings for Communication.topic do not cover the following types: CodeableConcept. The mappings for Communication.topic do not cover the following types based on type expansion: coding, text. Communication.topic.text can be used without any codings.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The encounter within which the communication was sent.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.encounter additional types from child elements (display, identifier, reference, type)

Element Communication.encounter is mapped to FHIR STU3 element Communication.context as SourceIsBroaderThanTarget. The mappings for Communication.encounter do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.encounter with unmapped reference targets: Encounter. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The time when this communication was sent.

The time when this communication arrived at the destination.

The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.sender

Element Communication.sender is mapped to FHIR STU3 element Communication.sender as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element Communication.sender with unmapped reference targets: CareTeam, Device, Endpoint, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The reason or justification for the communication.

Textual reasons can be caprued using reasonCode.text.

Codes for describing reasons for the occurrence of a communication.

Indicates another resource whose existence justifies this communication.

Text, attachment(s), or resource(s) that was communicated to the recipient.

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

R5: Communication.payload.content[x] additional types (CodeableConcept)

Element Communication.payload.content[x] is mapped to FHIR STU3 element Communication.payload.content[x] as SourceIsBroaderThanTarget. The mappings for Communication.payload.content[x] do not cover the following types: CodeableConcept. The target context Communication.payload.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Communication.payload. The standard extension alternate-reference has been mapped as PART of the representation of FHIR R5 element Communication.payload.content[x] with unmapped reference targets: Resource. Source element Communication.payload.content[x] has unmapped reference types. While the target element Communication.payload.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

If the content isn't codified, contentCodeableConcept.text can be used.

When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

A communicated content (or for multi-part communications, one portion of the communication).

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

R5: Communication.payload.content[x] additional types (CodeableConcept)

Element Communication.payload.content[x] is mapped to FHIR STU3 element Communication.payload.content[x] as SourceIsBroaderThanTarget. The mappings for Communication.payload.content[x] do not cover the following types: CodeableConcept. The target context Communication.payload.content[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element Communication.payload. The standard extension alternate-reference has been mapped as PART of the representation of FHIR R5 element Communication.payload.content[x] with unmapped reference targets: Resource. Source element Communication.payload.content[x] has unmapped reference types. While the target element Communication.payload.content[x] is a choice type and does not allow extensions, the alternate-reference extension can be applied to Reference values within it. The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

If the content isn't codified, contentCodeableConcept.text can be used.

When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

Additional notes or commentary about the communication by the sender, receiver or other interested parties.