Document field-level transformations

[scleary1cs]

Backlog Task

Document the HL7 to FHIR conversion at the field-level and the FHIR to HL7 conversion at the field-level.

Completion Criteria

• [ ] Our IG update with the field-level conversion for orders and results

Tasks

• [ ] Brainstorm how this documentation will be provided
  • [ ] Update the mappings tab under the IG for the ORU, ORM and OML

Other Notes

• Conversions can be documented in our IG documentation using StructureMaps and FHIR Mapping Language
• StructureMap Resource: https://build.fhir.org/structuremap.html
• FHIR Mapping Language: https://build.fhir.org/mapping-language.html
• FHIR Mapping Language Tutorial: https://build.fhir.org/mapping-tutorial.html

[basiliskus]

https://slack.com/archives/C055XTF22B0/p1692222960144869

[JohnNKing]

As part of this, document what we found with OBX-4 during https://github.com/CDCgov/trusted-intermediary/issues/641

Specifically, ReportStream currently supports OBX-4 if it's a string. The sub-fields as utilized by Natus, however, are an issue. Currently this information is being lost during transformation. See "OG" data type as referenced by the LOI/LRI.

[JohnNKing]

For example, document creation of SPM segment. Also NK1 via either NK1 or PID.6.

[saquino0827]

After some research into the task we need to do the following:

• Determine priority of when this work needs to be done.
• Determine how to split this task.(possibly by Segments of ORU/ORM).
• Determine which fields are required for NBS documentation.
• Research & Implement self-documentation for future updates.