Skip to end of metadata
Go to start of metadata

In order to speed up the review of the initial vocabulary, data type, segment and field mappings, we want to implement a new review process. We will leverage the standard data type and segment spreadsheet format that was developed in Montreal. We want to make sure that everyone has a chance to provide input into the initial mapping as well as comment on the proposed mapping.

The proposed review process is based on a few fundamental principles:

  • If mappings already exist, we want to utilize them
  • Each data type/segment/message should have an "owner" who is responsible for documenting the proposed mapping
    • This will prevent multiple people from stepping on each other's toes as they contribute to the mapping
  • The proposed mappings we come up with will be part of future ballots so that everyone will have multiple times to contribute their thoughts

We would like to propose the following stages of the review process. For now, we will focus on the review of segment mappings as we are still working on the format for the message level spreadsheets. Data types and vocabulary being used by the segment under review will be fair game for review and comment as well.

  1. The segment owner creates initial mapping for the segment at hand and put into GoogleSheets.
  2. The segment being reviewed will be announced to the v2-FHIR listserv and posted on the Confluence site and Zulip
  3. Individuals or organizations will have 1 week to perform an initial review comparing their mappings with the initial HL7 mapping
    1. The reviewer will perform the comparison with the GoogleSheet
    2. If mappings for the segment vary, the reviewer will highlight those differences in the initial HL7 mapping using the comments feature in GoogleSheets.
      1. Sample spreadsheet comparison tools to use:
        1. BeyondCompare 4 -
        2. Other?
  4. The segment owner will have 1 week to review the submitted comments and identify potential solutions.
    1. update the GoogleSheet accordingly.
  5. The initial proposed mappings will be distributed to the v2-FHIR listserv and posted to a Confluence site
    1. The community will have 2 weeks to review the proposed initial mapping and submit comments and thoughts to the segment owner
    2. When available, the review can be expanded with running actual v2 segments / messages through a transform that creates a populated FHIR Resource / Bundle  (v2 segment/message-FHIR resource/bundle pair)
  6. After the 2 week comment period, any remaining differences or comments will be reviewed on one (or more) of the weekly calls
    1. These calls will not go over each field mapping individually but rather only touch on the places where the community has questions or comments. Hopefully this will speed up the process.
  7. As one segment is being reviewed and discussed, a call for the next segment will be distributed so that we continually have a new segment maturing to the point of being discussed on the weekly calls.
    1. Note that the staggering of segments may vary (sometime by 1 week, sometimes by 2 or more) depending on the amount of discussion we think they might evoke

An initial proposed set of timelines using this process is given below:

  • No labels