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

align medication route terms with CCDA

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Core (FHIR)
    • 6.0.0-ballot [deprecated]
    • Cross-Group Projects
    • US Core MedicationRequest Profile
    • Hide

      MedicationRequest.route is not profiled in US Core and therefore no guidance is given on the terminology binding.  This profile sets minimum expectations for the MedicationRequest resource to record, search, and fetch a patient’s medication to promote interoperability and adoption through common implementation. It provides the floor for standards development by other implementers and guides for specific use cases.

      Show
      MedicationRequest.route is not profiled in US Core and therefore no guidance is given on the terminology binding.  This profile sets minimum expectations for the MedicationRequest resource to record, search, and fetch a patient’s medication to promote interoperability and adoption through common implementation. It provides the floor for standards development by other implementers and guides for specific use cases.
    • Eric Haas/Brett Marquard: 13-0-1

    Description

      C-CDA stipulates the use of an NCI value set for medication route. FHIR US Core MedicationRequest has only the base example SNOMED CT binding. If data is received from FHIR implementers using SNOMED CT values, representation in C-CDA will require translation. While CDA "CD.translation" values may support semantics, they will clutter the provider view. We recommend adopting the NCI route value set in US Core.

      We further recommend that Immunization route codes also adopt values from NCIT, or at a minimum that a concept map be published to support deterministic translation.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jlyle Jay Lyle
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: