Loading...

XML

Word

Printable

JSON

Specification:

V2 to FHIR (V2)
Raised in Version:

1.0
Work Group:

Orders & Observations
Related Artifact(s):

Processing Type to FHIR MessageHeader (PT)
Related Section(s):
18.153.1
Grouping:
- Feb2024
- OO-FHIR-Block-Vote
Resolution Description:

Hide

Motion to find not persuasive as this is already mapped to Bundle.identifier that is more suitable. Given the use and purpose of a .id in FHIR it would not be appropriate to map a business concept to that, rather use a .identifier that is most suitable. Note that in every message there is a MSH[Bundle] segment included to map, among other things, the Control ID.

Show
Motion to find not persuasive as this is already mapped to Bundle.identifier that is more suitable. Given the use and purpose of a .id in FHIR it would not be appropriate to map a business concept to that, rather use a .identifier that is most suitable. Note that in every message there is a MSH [Bundle] segment included to map, among other things, the Control ID.
Resolution Vote:
Hans Buitendijk / Riki Merrick: 8-0-1

Existing Wording	Proposed Wording	Ballot Comment
	MessageHeader.id	messageHeader.id is unique for instance of that message, which is some cases could be useful to track. Propose to map message control id to messageheader.id. It will also allow uniqueness of the message maintained at FHIR server level, avoid duplicates post mapping with the use of back-end store.