OpenEHR Base package
0.1.0 - First Draft International flag

OpenEHR Base package, published by openEHR + HL7. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/openehr-fhir/base-spec/ and changes regularly. See the Directory of published versions

Logical Model: MESSAGE

Official URL: http://openehr.org/fhir/StructureDefinition/MESSAGE Version: 0.1.0
Standards status: Informative Maturity Level: 3 Computable Name: MESSAGE

A “message” is an authored, possibly signed, piece of content intended for one or more recipients. Since the recipient may or may not be known directly, recipients are specified in the ADDRESSED_MESSAGE class.

Original Source: specifications.openehr.org

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format

This structure is derived from Any

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format

This structure is derived from Any

Summary

Mandatory: 0 element(3 nested mandatory elements)

Maturity: 3

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format

Differential View

This structure is derived from Any

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. MESSAGE 0..* Any A “message” is an authored, possibly signed, piece of content intended for one or more recipients.
... audit 1..1 AUDIT_DETAILS Details of who actually created the message and when.
... author 1..1 PARTY_PROXY Party responsible for the message content, who may or may not be technically responsible for its creation (e.
... content 1..1 MESSAGE_CONTENT Content of the message.

doco Documentation for this format

This structure is derived from Any

Summary

Mandatory: 0 element(3 nested mandatory elements)

Maturity: 3

 

Other representations of profile: CSV, Excel