Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-40892

suggest condition.verificationStatus mapping added to C-CDA to FHIR and FHIR to C-CDA tables.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US C-CDA on FHIR (FHIR)
    • 1.2.0-ballot
    • Cross-Group Projects
    • STU
    • C-CDA to FHIR Problems
    • 11 C-CDA to FHIR Problems
    • Hide

      While we understand the desire to capture verificationStatus in FHIR, there is no clear equivalent in C-CDA today. If a new template were created for C-CDA around "Problem Verification" this could be mapped to FHIR in the future, but currently the only equivalent in C-CDA is the @negationInd which is already included in the maps.

      Show
      While we understand the desire to capture verificationStatus in FHIR, there is no clear equivalent in C-CDA today. If a new template were created for C-CDA around "Problem Verification" this could be mapped to FHIR in the future, but currently the only equivalent in C-CDA is the @negationInd which is already included in the maps.
    • Jay Lyle/John D'Amore: 18-0-6

    Description

      It'll be great if a mapping for condition.verificationStatus is added to C-CDA to FHIR and FHIR to C-CDA tables. For our quality measures, condition.verifcationStatus needs be checked if it is not null. Thus it'll be helpful to provide the info on where to capture the value from C-CDA besides @negationInd=true is mapped to "refuted' in FHIR.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Hu Yanyan Hu
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: