Skip to end of metadata
Go to start of metadata

Topics


Connectathon Pages:

Other Helpful/Insightful Links:

Approach:

  • Data Type Mapping
    • Initially target creating worksheets/templates to assist Segment/Field mapping.
    • Do so as we go, i.e., work on a segment and populate the data type mappings as we run into them.
    • Create flavors as needed.
  • Segment/Field Mapping
    • Target this as balloted content.
    • Create flavors as needed based on use in various messages.
    • Segments in priority order for now: MSH, PID, PD1, NK1(RelatePerson/Patient.contact), ROL/PRT, (IN1), PV1, PV2, ORC, OBR, OBX, RXO?, RXE?, RDS?, RXA, RXR, SPM, NTE
  • Messages

Mapping topics to discuss

  • The use of the Provenance resource when "entering" information is part of the segment (e.g. ORC-10)
  • How to best populate Resource.id and what are the implications for future FHIR queries/searches
    • Technically this doesn't seem to be required, but it seems pretty foundational
    • If we do decide to populate this, how do it for resources that are the central focus of the v2 message (eg. what is Provider.id for the administering provider of an immunization?)

Attachments

  • No labels