Uploaded image for project: 'MedMij Standaarden'
  1. MedMij Standaarden
  2. MM-148

AllergyIntolerance.AllergyReaction.Severity enumeration instead of codes

    Details

    • Blokkerend:
      Nee
    • Informatiestandaard:
      BgZ, Allergieintolerantie
    • Informatiestandaard onderdeel:
      FHIR
    • Impact:
      Geen
    • FHIR Category:
      Profiles
    • Voorgestelde oplossing:
      Hide
      The AllergyIntolerance.severity has a required terminology binding in FHIR to a different set than the HCIM. Because of the required binding we cannot profile it away. The HCIM is not made for FHIR specifically, it is meant to be a functional model.

      For the mapping, please have a look at https://simplifier.net/nictizstu3-zib2017/ernstcodelijst-to-allergyintoleranceseverity
      Show
      The AllergyIntolerance.severity has a required terminology binding in FHIR to a different set than the HCIM. Because of the required binding we cannot profile it away. The HCIM is not made for FHIR specifically, it is meant to be a functional model. For the mapping, please have a look at https://simplifier.net/nictizstu3-zib2017/ernstcodelijst-to-allergyintoleranceseverity

      Description

      I encountered something in AllergyIntolerance.AllergyReaction.Severity I had also encountered in one other question about TimeOfDay codelists.

      In the touchstone response for AllergyIntolerance there is the severity field with value severe. The HAPI parser recognizes this as one of the enum values of AllergyIntolerance.AllergyIntoleranceSeverity. The alleged code, that should coincide with one of the conceptcodes from the SeverityCodeList, is not found in the severity field.

      In short my question is:
      why are the conceptcodes in the SeverityCodeList defined if they are not used by the parser or touchstone responses.

      With kind regards,

      Yuri Bonanno

        Attachments

          Activity

            People

            Assignee:
            henket Alexander Henket
            Reporter:
            yuri.bonanno@curavista.nl Yuri Bonanno
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Estimations By Role

                No roles have been estimated yet.