Design a Table to map Event Codes / Conditions for the Hepatitis /Lyme + Arbo MMGs to be used for Validation/Transformation.

[mscaldas2012]

In Scope

• Updates to "LymeTBRDArboEventCodeMapping.xlsx"
• Arbo/Lyme MMG

Out of scope

• Hep, FDD MMG
• Table in Redis format
• Implementation in MMG Validator service

Event Code	MMG Name (Key in Redis)	MMG UUID	Program Folder
"11089"	-> "LYME"	MMG UUID	Folder Location
"11080"	-> "TBRD"	MMG UUID	Folder Location
"11088"	-> "TBRD"	MMG UUID	Folder Location
"11090"	-> "TBRD"	MMG UUID	Folder Location
"11091"	-> "TBRD"	MMG UUID	Folder Location
"10250"	-> "TBRD"	MMG UUID	Folder Location

and so on...

[rmharrison]

Psuedo code from Cosmin...

We'll need in Redis (I think) a table of : Event Code, MMG Name (key to retrieve it), MMG UUID Example on a HL7 message if GenV2, and event code is 11089, then the MMG Validator will apply GenV2 + Lyme MMG rules

// Event Code | MMG Name (Key in Redis) | MMG UUID

      "11089" -> "LYME" // | MMG UUID

      "11080" -> "TBRD" // | MMG UUID

      "11088" -> "TBRD" // | MMG UUID

      "11090" -> "TBRD" // | MMG UUID

      "11091" -> "TBRD" // | MMG UUID

      "10250" -> "TBRD" // | MMG UUID

      else -> HL7Error.EVENT_CODE_NOT_SUPPORTED_ERROR.message

[rmharrison]

FFR @lmcnabb assigned for sprint 22 Sep - Oct 5 @marcia-schulman assigned for sprint 6-19 Oct

[lmcnabb]

Received spreadsheet back from program on 9.30.2022. Requires follow up with program epi before proceeding and getting more questions answered.

[lmcnabb]

Here is the file received from Karen. It requires a deeper dive with her team and epis to get some questions answered. doc here

[marcia-schulman]

StateReportingRouteForDifferentCategoryData.xlsx LymeTBRDArboEventCodeMapping (1) (1).xlsx Updated information from NCZEID regarding Arbo spec usage (from Craig Mincic)

[marcia-schulman]

Did an element-by-element comparison of Arbo MMGs 1.3.0, 1.3.1, and 1.3.2. Conclusion: There is NO DIFFERENCE. The version change from 1.3.0 to 1.3.1 is an update to Race and Ethnicity value sets to include "UNK". However, the 1.3.0 implementation notes state that 'to send an unknown, use UNK' -- in other words, it was already accepting this code that is part of the PHVS_RaceCategory_CDC_Unk and PHVS_EthicityGroup_CDC_Unk value sets.

[lmcnabb]

Can you see the diff between 1.3.1 and 1.3.2 next? If it is truly another value set change and that is it, then what do you think about this?

We build out the validation one time and have it validate against all three (1.3.0, 1.3.1, or 1.3.2)

[marcia-schulman]

There is no difference between 1.3.1 and 1.3.2. The only revision was on the introductory page in the Resources section. So, we can safely use 1.3.2 for all 1.3.x validation.

[marcia-schulman]

Options Presented to Team on 11/4/22

Option A was the winner. options.txt

[marcia-schulman]

This issue is now closed, with the decision to use a namespaced key (with namespace "condition") and a JSON string value that contains all the MMG and program mapping information for the condition.

See "options.txt" referenced above for a full description of the selected option (Option A)

[marcia-schulman]

QED

[marcia-schulman]

We decided to update the JSON format of the mmg map record to use the profile name (normalized to lower case) as a key to the mmg list. New JSON format is this:

{
    "event_code": "11091",
    "name": "Ehrlichiosis/Anaplasmosis, undetermined",
    "program": "NCEZID",
    "category": "Vectorborne Diseases",
    "mmg_maps": [
        {
            "lyme_tbrd_mmg_v1.0": [
                "mmg:tbrd"
            ]
        }
    ]
}