This wiki has undergone a migration to Confluence found Here
Difference between revisions of "InM fhir messaging"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
==Introduced in Sept.2017 San Diego== | ==Introduced in Sept.2017 San Diego== | ||
===GF#13848 Change messageheader.event data type from code to URI=== | ===GF#13848 Change messageheader.event data type from code to URI=== | ||
| + | *This allows the sender to link to the formal event definition | ||
===GF#13849 change event element in messagedefinition to URI, and make optional.=== | ===GF#13849 change event element in messagedefinition to URI, and make optional.=== | ||
Revision as of 15:46, 15 September 2017
Contents
- 1 Topics for FHIR
- 1.1 Introduced in Sept.2017 San Diego
- 1.1.1 GF#13848 Change messageheader.event data type from code to URI
- 1.1.2 GF#13849 change event element in messagedefinition to URI, and make optional.
- 1.1.3 GF#13850 add messagedefinition element to messageheader
- 1.1.4 GF#13851 align messageheader.extension-messageheader-response-request with MessageDefinition.responserequired
- 1.1.5 GF#13852 Change messagedefinition maturity level to 1, and ballot status to STU
- 1.1 Introduced in Sept.2017 San Diego
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
GF#13849 change event element in messagedefinition to URI, and make optional.
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
GF#13852 Change messagedefinition maturity level to 1, and ballot status to STU
===GF#13853 Change Maturity level on Messageheader to FMM4
