Profile Comparison between http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication vs http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Communication
copyright
date	2023-10-04T16:21:05+02:00	2024-06-28T11:24:18+02:00	Values Differ
description	Care related communication between two or more parties in Danish healthcare
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#DK
kind	resource
name	MedComCareCommunication
publisher	MedCom
purpose
status	active
title
type	Communication
url	http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-communication
version	3.0.0	4.0.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	R Type	R Description & Constraints	Comments
Communication	C	0..*	Communication	A record of information transmitted from a sender to a receiver medcom-careCommunication-5: Priority is only allowed when Communication.category = 'regarding-referral' medcom-careCommunication-6: There shall exist a Communication.topic when Communication.category = 'other' medcom-careCommunication-7: There shall exist a practitioner role when using a PractitionerRole as author in a message segment. medcom-careCommunication-8: There shall exist a practitioner name when using a Practitioner as author in a message segment. medcom-careCommunication-10: The status shall be 'unknown' or 'entered-in-error'.	C	0..*	Communication	A record of information transmitted from a sender to a receiver medcom-careCommunication-5: Priority must not be present when Communication.category is other than 'regarding-referral' medcom-careCommunication-6: There shall exist a Communication.topic when Communication.category = 'other' medcom-careCommunication-7: There shall exist a practitioner role when using a PractitionerRole as author in a message segment. medcom-careCommunication-8: There shall exist a practitioner name when using a Practitioner as author in a message segment. medcom-careCommunication-9: An episodeOfCare-identifier must be included when an Encounter instance is included.
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Unique identifier	SΣC	1..1	Identifier	The communication identifier medcom-uuidv4: The value shall correspond to the structure of an UUID version 4	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1' Element maximum cardinalities differ: '2147483647' vs '1'
id						0..1	string	Unique id for inter-element referencing	Added this element
Slices for extension						0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url	Added this element
use					?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: ?? (required): Identifies the purpose for this identifier, if known .	Added this element
type					Σ	0..1	CodeableConcept	Description of identifier Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.	Added this element
system					Σ	0..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient	Added this element
value					SΣ	1..1	string	The value that is unique Example General: 123456	Added this element
period					Σ	0..1	Period	Time period when id is/was valid for use	Added this element
assigner					Σ	0..1	Reference(Organization)	Organization that issued id (may be just text)	Added this element
instantiatesCanonical	Σ	0..*	canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)	Instantiates FHIR protocol or definition	Σ	0..*	canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this communication	Σ	0..*	Reference(Resource)	Request fulfilled by this communication
partOf	Σ	0..*	Reference(Resource)	Part of this action	Σ	0..*	Reference(Resource)	Part of this action
inResponseTo		0..*	Reference(Communication)	Reply to		0..*	Reference(Communication)	Reply to
status	?!SΣ	1..1	code	The status may be 'unknown' or 'entered-in-error', dependning on the type of message. status is required because of basic FHIR profile requirement Binding: ?? (required): The status of the communication.	?!SΣ	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: ?? (required): The status of the communication. Required Pattern: unknown
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding: ?? (example): Codes for the reason why a communication did not happen.	Σ	0..1	CodeableConcept	Reason for current status Binding: ?? (example): Codes for the reason why a communication did not happen.
category	S	1..1	CodeableConcept	The category (Danish: kategori) describes the overall content of the message. Binding: ?? (required)	S	1..1	CodeableConcept	The category (Danish: kategori) describes the overall content of the message. Binding: ?? (required)
id						0..1	string	Unique id for inter-element referencing	Added this element
Slices for extension						0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url	Added this element
coding					Σ	0..*	Coding	Code defined by a terminology system	Added this element
text					Σ	0..1	string	Plain text representation of the concept	Added this element
priority	SΣ	0..1	code	Shall 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)	SΣ	0..1	code	Shall 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..*	CodeableConcept	A channel of communication Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.		0..*	CodeableConcept	A channel of communication Binding: ?? (example): Codes for communication mediums such as phone, fax, email, in person, etc.
subject	SΣ	1..1	Reference(MedComCorePatient(2.2.0)) {b}	Focus of message	SΣ	1..1	Reference(MedComCorePatient) {b}	Focus of message
topic	S	0..1	CodeableConcept	The topic (Danish: emne) may be added as a supplement to the category. Binding: ?? (example): Codes describing the purpose or content of the communication.	S	0..1	CodeableConcept	The 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.
id						0..1	string	Unique id for inter-element referencing	Added this element
Slices for extension						0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url	Added this element
coding					Σ	0..*	Coding	Code defined by a terminology system	Added this element
text					SΣ	1..1	string	Plain text representation of the concept	Added this element
about		0..*	Reference(Resource)	Resources that pertain to this communication		0..*	Reference(Resource)	Resources that pertain to this communication
encounter	SΣ	0..1	Reference(MedComCoreEncounter(2.2.0)) {b}	Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.	SΣ	0..1	Reference(MedComCoreEncounter) {b}	Shall contain a reference to an Encounter resource with a episodeOfCare-identifier, if the identifier is included in a previous message.
sent		0..1	dateTime	When sent		0..1	dateTime	When sent
received		0..1	dateTime	When received		0..1	dateTime	When received
recipient	S	0..*	Reference(MedComCorePractitionerRole(2.2.0) | MedComCoreCareTeam) {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.	S	0..*	Reference(MedComCorePractitionerRole | MedComCoreCareTeam) {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..1	Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)	Message sender		0..1	Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | HealthcareService)	Message sender
reasonCode	Σ	0..*	CodeableConcept	Indication for message Binding: ?? (example): Codes for describing reasons for the occurrence of a communication.	Σ	0..*	CodeableConcept	Indication 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?	Σ	0..*	Reference(Condition | Observation | DiagnosticReport | DocumentReference)	Why was communication done?
Slices for payload		1..*	BackboneElement	Each payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included. Slice: Ordered, Open by type:$this.content		1..*	BackboneElement	Each payload corresponds to a message segment with a message text or an attachment. At least one payload with a message text shall be included. Slice: Unordered, Open by type:$this.content
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url		0..*	Extension	Extension Slice: Unordered, Open by value:url
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
content[x]		1..1	string, Attachment, Reference(Resource)	Message part content		1..1	string, Attachment, Reference(Resource)	Message part content
note		0..*	Annotation	Comments made about the communication		0..*	Annotation	Comments made about the communication
Documentation for this format