HL7 Message Message 1 1 Mandatory false A message that contains FHIR resources Many implementations are not prepared to use REST, and need a message based infrastructure Message.id 1 1 Mandatory id true Unique Id for this message Each message needs a unique identifier so other messages and underlying infrastructure can reference it must be unique within a channel, but should be globally unique. UUIDs are recommended Message.threadId 0 1 Optional id false Id of the thread - a series of messages that pertain to the same logical sequence, and are all identified by the same thread identifier Message.instant 1 1 Mandatory instant true Instant the message was sent Message.event 1 1 Mandatory code MessageEvent true Code that identifies the event this message represents, and connects it with the event definition in the FHIR specification Message.response 0 1 Optional true Information about the the message that this message is a response to - if it is a response Message.response.id 1 1 Mandatory id true The id of the message that this a response to this message must have the same threadId as the original message (including missing if the original message threadId was missing) Message.response.code 1 1 Mandatory code ResponseCode true Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or not This is a generic response to the request message. Specific data for the response will be found in Message.data Message.response.duplicate 1 1 Mandatory boolean true True if this is not the first response, because the request message has been received more than once The request shouldn't be received more than once if reliable message delivery applies, but mostly it doesn't Message.source 1 1 Mandatory Resource(Device) false The source application from which this message originated Message.destination 1 1 Mandatory Resource(Device) false The destination application which the message is intended for Message.enterer 0 1 Optional Resource(Person|Device) false The person or device that performd the data entry leading to this message. Where there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions Need to know for audit/traceback requirements Usually only for the request, but can be used in a response Message.author 0 1 Optional Resource(Person|Device) false The logical author of the message - the person or device that decided it should happen. Where there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions Need to know for audit/traceback requirements Usually only for the request, but can be used in a response Message.responsible 0 1 Optional Resource(Person|Organization) false The person or organization that accepts overall responsbility for the contents of the message. The implication is that the message event happened under the policies of the responsible party Need to know for audit/traceback requirements Usually only for the request, but can be used in a response Message.effective 0 1 Optional Interval(dateTime) false The effective time - the real world time of the even that the message represents. Usually this is just a starting time, but some message events also have an end time (do x for period y) Need to know for understanding the content of the message Usually only for the request, but can be used in a response Grahame thinks this is not 80/20. Also, that it reall should be domain modeled, not tucked away here Message.reason 0 1 Optional CodeableConcept EventReason false The cause of the event - a reason for why this message is being sent Need to be able to track why resources are being changed and report in the audit log / history of the resource ControlAct.reasonCode Message.data 0 1 Conditional Mandatory unless the message is a response, in which case the element is optional Resource(Any) true The actual data of the message - a reference to the focus class of the message. Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources The data is defined where the transaction type is defined. The transaction data is always aggregated with the transaction resource Message.extensions 0 1 Optional false See Extensions Message.text 1 1 Mandatory Narrative false