Patient Request for Corrections Implementation Guide
1.0.0 - STU 1 International flag

Patient Request for Corrections Implementation Guide, published by HL7 International / Patient Empowerment. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-patient-correction/ and changes regularly. See the Directory of published versions

Resource Profile: Patient Correction Communication

Official URL: http://hl7.org/fhir/uv/patient-corrections/StructureDefinition/patient-correction-communication Version: 1.0.0
Standards status: Trial-use Maturity Level: 1 Computable Name: PatientCorrectionCommunication

A Communication between a patient and a fulfiller relating to a patient correction request.

This is the profile for the Patient Correction Communication, which is used for back and forth conversation about a patient’s request for correction to their medical record. Each Patient Correction Communication resource instance represents a message in the bidirectional conversation needed to complete a patient’s request for correction to their medical record or for logging their disagreement to a correction denial. This profile sets minimum expectations for the Communication resource to support this workflow. It is expected to be used in conjunction with the Patient Correction Task profile.

Mandatory and Must Support data elements

The following data-elements must always be present (Mandatory) definition or must be supported if the data is present (Must Support) definition. They are presented below in a simple human-readable explanation. Profile specific guidance is provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements. Refer to the Actors and Use Cases section of the guide for example resources provided in the context of an example workflow.

Each implementation of PatientCorrectionCommunication must provide:

  1. id: An id
  2. status: fixed to “completed”
  3. category: indicates whether it’s a “Request for Correction” or “Log Disagreement” process
  4. subject: the person whose record is to be corrected
  5. sender: who is sending this communication
  6. recipient: who is receiving this communication
  7. sent: date/time communication was sent
  8. about: When the initial Communication request for correction resource is created by the Requester, Communication.about will be empty. When the Fulfiller spawns a Task to support the request, the Fulfiller sets Communication.about to reference the spawned Task that represents the entire request for correction or log disagreement process. On all other Communication resources, Communication.about references the Communication resource that contained the initial request. When a Log Disagreement Task is created, the Fulfiller will update the Communication containing the Log Disagreement request such that Communication.about references the Log Disagreement Task as well as the original correction request Communication.
  9. topic: a heading/subject line for the message being sent. Could be thought of as the subject line in an email thread.
  10. inResponseTo: points to the prior Communication resource in a conversation thread.
  11. Payload: contains the actual message being communicated, including any attachments or references.

Profile-specific implementation guidance

  • If the Communication resource represents the start of a Request for Correction or Log Disagreement process, Communication.about will reference the Task representing the overall associated Fulfiller process. On the start of a Log Disagreement, Communication.about will also reference the Communication resource of the initial correction request that is being disagreed with.
  • Additional Communication resources are created to represent each component of the back and forth conversation between the Requester and Fulfiller. The sender and recipient is set appropriately based on the direction of the conversation. All Communication resources are stored and queryable on the Fulfiller.
  • The Communication resources associated with a request for correction or log disagreement can be assembled into a conversation by first referring to the Communication of the original request, and then finding any Communication resources that reference it in the about field. If there are any threads of conversation, these are connected via Communication.inResponseTo.

Usages:

Formal Views of Profile Content

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

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication Communication
... partOf S 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... inResponseTo S 0..1 Reference(Patient Correction Communication) Reply to
... status 1..1 code Fixed: completed.
Required Pattern: completed
... subject S 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... sent 1..1 dateTime When this communication was sent
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... payload S 0..* BackboneElement Contents of this communication.
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication 0..* Communication A record of information transmitted from a sender to a receiver
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... partOf SΣ 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... status ?!Σ 1..1 code Fixed: completed.
Binding: EventStatus (required): The status of the communication.
Required Pattern: completed
... category S 1..1 CodeableConcept Message category
Binding: Patient Correction Communication Types Value Set (required)
... subject SΣ 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... sent 1..1 dateTime When this communication was sent
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... payload S 0..* BackboneElement Contents of this communication.
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... content[x] 1..1 Message part content
..... contentString string
..... contentAttachment Attachment
..... contentReference Reference(Resource)
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Communication.statusrequiredPattern Value: completed
http://hl7.org/fhir/ValueSet/event-status|4.0.1
From the FHIR Standard
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG
Communication.topicexampleCommunicationTopic
http://hl7.org/fhir/ValueSet/communication-topic
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorCommunicationIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCommunicationIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCommunicationA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication 0..* Communication A record of information transmitted from a sender to a receiver
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text summary of the resource, for human interpretation
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier Unique identifier
... instantiatesCanonical Σ 0..* canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... basedOn Σ 0..* Reference(Resource) Request fulfilled by this communication
... partOf SΣ 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... inResponseTo S 0..1 Reference(Patient Correction Communication) Reply to
... status ?!Σ 1..1 code Fixed: completed.
Binding: EventStatus (required): The status of the communication.
Required Pattern: completed
... statusReason Σ 0..1 CodeableConcept Reason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.
... category S 1..1 CodeableConcept Message category
Binding: Patient Correction Communication Types Value Set (required)
... priority Σ 0..1 code routine | urgent | asap | stat
Binding: RequestPriority (required): Codes indicating the relative importance of a communication.
... medium 0..* CodeableConcept A channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject SΣ 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... encounter Σ 0..1 Reference(Encounter) Encounter created as part of
... sent 1..1 dateTime When this communication was sent
... received 0..1 dateTime When received
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... reasonCode Σ 0..* CodeableConcept Indication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Why was communication done?
... payload S 0..* BackboneElement Contents of this communication.
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... content[x] 1..1 Message part content
..... contentString string
..... contentAttachment Attachment
..... contentReference Reference(Resource)
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Communication.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
From the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
Communication.statusrequiredPattern Value: completed
http://hl7.org/fhir/ValueSet/event-status|4.0.1
From the FHIR Standard
Communication.statusReasonexampleCommunicationNotDoneReason
http://hl7.org/fhir/ValueSet/communication-not-done-reason
From the FHIR Standard
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG
Communication.priorityrequiredRequestPriority
http://hl7.org/fhir/ValueSet/request-priority|4.0.1
From the FHIR Standard
Communication.mediumexampleParticipationMode
http://terminology.hl7.org/ValueSet/v3-ParticipationMode
Communication.topicexampleCommunicationTopic
http://hl7.org/fhir/ValueSet/communication-topic
From the FHIR Standard
Communication.reasonCodeexampleSNOMEDCTClinicalFindings
http://hl7.org/fhir/ValueSet/clinical-findings
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorCommunicationIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCommunicationIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCommunicationA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from Communication

Summary

Mandatory: 5 elements
Must-Support: 9 elements

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Communication.about

Maturity: 1

Differential View

This structure is derived from Communication

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication Communication
... partOf S 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... inResponseTo S 0..1 Reference(Patient Correction Communication) Reply to
... status 1..1 code Fixed: completed.
Required Pattern: completed
... subject S 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... sent 1..1 dateTime When this communication was sent
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... payload S 0..* BackboneElement Contents of this communication.
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication 0..* Communication A record of information transmitted from a sender to a receiver
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... partOf SΣ 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... status ?!Σ 1..1 code Fixed: completed.
Binding: EventStatus (required): The status of the communication.
Required Pattern: completed
... category S 1..1 CodeableConcept Message category
Binding: Patient Correction Communication Types Value Set (required)
... subject SΣ 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... sent 1..1 dateTime When this communication was sent
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... payload S 0..* BackboneElement Contents of this communication.
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... content[x] 1..1 Message part content
..... contentString string
..... contentAttachment Attachment
..... contentReference Reference(Resource)
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Communication.statusrequiredPattern Value: completed
http://hl7.org/fhir/ValueSet/event-status|4.0.1
From the FHIR Standard
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG
Communication.topicexampleCommunicationTopic
http://hl7.org/fhir/ValueSet/communication-topic
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorCommunicationIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCommunicationIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCommunicationA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Communication 0..* Communication A record of information transmitted from a sender to a receiver
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... language 0..1 code Language of the resource content
Binding: CommonLanguages (preferred): A human language.
Additional BindingsPurpose
AllLanguages Max Binding
... text 0..1 Narrative Text summary of the resource, for human interpretation
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier Unique identifier
... instantiatesCanonical Σ 0..* canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire) Instantiates FHIR protocol or definition
... instantiatesUri Σ 0..* uri Instantiates external protocol or definition
... basedOn Σ 0..* Reference(Resource) Request fulfilled by this communication
... partOf SΣ 0..1 Reference(Patient Correction Communication) Initial Patient Correction Communication resource for this request.
... inResponseTo S 0..1 Reference(Patient Correction Communication) Reply to
... status ?!Σ 1..1 code Fixed: completed.
Binding: EventStatus (required): The status of the communication.
Required Pattern: completed
... statusReason Σ 0..1 CodeableConcept Reason for current status
Binding: CommunicationNotDoneReason (example): Codes for the reason why a communication did not happen.
... category S 1..1 CodeableConcept Message category
Binding: Patient Correction Communication Types Value Set (required)
... priority Σ 0..1 code routine | urgent | asap | stat
Binding: RequestPriority (required): Codes indicating the relative importance of a communication.
... medium 0..* CodeableConcept A channel of communication
Binding: ParticipationMode (example): Codes for communication mediums such as phone, fax, email, in person, etc.
... subject SΣ 1..1 Reference(Patient) The Patient that the correction request or the log disagreement applies to.
... topic S 0..1 CodeableConcept A heading/subject line for the message being sent.
Binding: CommunicationTopic (example): Codes describing the purpose or content of the communication.
... Slices for about 0..* Reference(Resource) Resources that pertain to this communication
Slice: Unordered, Open by type:reference
.... about:correctionTask S 0..1 Reference(Patient Correction Task) Patient Correction Task requesting a correction.
... encounter Σ 0..1 Reference(Encounter) Encounter created as part of
... sent 1..1 dateTime When this communication was sent
... received 0..1 dateTime When received
... recipient S 1..* Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService) Message recipient: either a Requestor or a Fulfiller
... sender S 1..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization | HealthcareService) Message sender: either a Requestor or a Fulfiller
... reasonCode Σ 0..* CodeableConcept Indication for message
Binding: SNOMEDCTClinicalFindings (example): Codes for describing reasons for the occurrence of a communication.
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference) Why was communication done?
... payload S 0..* BackboneElement Contents of this communication.
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... content[x] 1..1 Message part content
..... contentString string
..... contentAttachment Attachment
..... contentReference Reference(Resource)
... note 0..* Annotation Non-actionable notes about this communication.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Communication.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
From the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
Communication.statusrequiredPattern Value: completed
http://hl7.org/fhir/ValueSet/event-status|4.0.1
From the FHIR Standard
Communication.statusReasonexampleCommunicationNotDoneReason
http://hl7.org/fhir/ValueSet/communication-not-done-reason
From the FHIR Standard
Communication.categoryrequiredPatientCorrectionCommunicationTypesVS
http://hl7.org/fhir/uv/patient-corrections/ValueSet/PatientCorrectionCommunicationTypesVS
From this IG
Communication.priorityrequiredRequestPriority
http://hl7.org/fhir/ValueSet/request-priority|4.0.1
From the FHIR Standard
Communication.mediumexampleParticipationMode
http://terminology.hl7.org/ValueSet/v3-ParticipationMode
Communication.topicexampleCommunicationTopic
http://hl7.org/fhir/ValueSet/communication-topic
From the FHIR Standard
Communication.reasonCodeexampleSNOMEDCTClinicalFindings
http://hl7.org/fhir/ValueSet/clinical-findings
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorCommunicationIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCommunicationIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCommunicationIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCommunicationA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

This structure is derived from Communication

Summary

Mandatory: 5 elements
Must-Support: 9 elements

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Communication.about

Maturity: 1

 

Other representations of profile: CSV, Excel, Schematron