InM fhir messaging

Topics for FHIR

Introduced in Sept.2017 San Diego

GF#13848 Change messageheader.event data type from code to URI

• This allows the sender to link to the formal event definition
  • Lloyd: This seems way too heavy. It prevents just pointing to a code - with its accompanying standard display or any definition. It's far from intuitive for someone familiar with v2 or v3 messaging to have any clue how to fill out EventDefinition.

GF#13849 change event element in messagedefinition to URI, and make optional.

• This allows the sender to link to the formal event definition

• • Lloyd: I don't understand how a message definition could ever not identify an event.

GF#13850 add messagedefinition element to messageheader

This allows the message to contain a link to the appropriate definition.

GF#13851 align messageheader.extension-messageheader-response-request with MessageDefinition.responserequired

• messageheader.messageheader.extension-messageheader-response-request has the following codes

Code	Id	System	Parent	Display	Definition
always				Always	initiator expects a response for this message
on-error				Error/reject conditions only	initiator expects a response only if in error
never				Never	initiator does not expect a response
on-success				Successful completion only	initiator expects a response only if successful

• messageDefinition.responserequired
  • Boolean
• MessageDefinition.response-code has the following codes

Code	Id	System	Parent	Display	Definition
ok	1			OK	The message was accepted and processed without error.
transient-error	2			Transient Error	Some internal unexpected error occurred - wait and try again. Note - this is usually used for things like database unavailable, which may be expected to resolve, though human intervention may be required.
fatal-error	3			Fatal Error	The message was rejected because of some content in it. There is no point in re-sending without change. The response narrative SHALL describe the issue.

GF#13852 Change messagedefinition maturity level to 1, and ballot status to STU

===GF#13853 Change Maturity level on Messageheader to FMM4