Stream: v2 to FHIR
Topic: Reporting minor typo's and inconsistencies in mapping tables
David McKillop (Mar 15 2022 at 05:52):
I've found the mapping tables associated with each resource quire useful and wondered what the best option was to have minor typo's and inconsistencies fixed - I'm assuming "Change request" for each resource would be the way to do it, but just wanted to confirm.
For example:
For the ServiceRequest V2 mappings :
- "priority" has "TQ1.9" but I think it should be "TQ.6"
- " performerType" has "RF!-3", but it should be "RF1-3"
For Observation V2 mappings (and similar inconsistencies in other resources) where the separator between segment and segment number is either a hypen (-) or a dot (.):
- "identifier" description has both "OBX.21" and "OBX-21"
- "performer" has both "OBX.15" and OBX-16"
I'm assuming the hypen (-) is the correct term, but just to clarify hypens (-) are used to separate segments and their respective field numbers and dots (.) are used to separate data types and their respective elements?
Riki Merrick (Mar 15 2022 at 14:49):
You are correct, that - should be used for the field and . should be used for component - we will need to update those mappings to be consistent (would you mind adding a jira for each resource, where you find it?).
Riki Merrick (Mar 15 2022 at 14:50):
As far as the identified mappings: priority should be TQ1-9, you are correct about the typo of! instead of 1.
Last updated: Apr 12 2022 at 19:14 UTC
