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

Medication termination reasons are not routinely documented at mCODE level of granularity

    XMLWordPrintableJSON

    Details

    • Type: Comment
    • Status: Resolved - No Change (View Workflow)
    • Priority: Medium
    • Resolution: Considered - No action required
    • Specification:
      US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • Raised in Version:
      1.16.0
    • Work Group:
      Clinical Interoperability Council
    • Related Artifact(s):
      Cancer-Related Medication Administration Profile
      Cancer-Related Medication Request Profile
    • Resolution Description:
      Hide

      Termination reason is 0..* MS on both medicationadministration and medicationrequest profiles.   Based on the http://build.fhir.org/ig/HL7/fhir-mCODE-ig/conformance-profiles.html termination reason is thus not required.

      Show
      Termination reason is 0..* MS on both medicationadministration and medicationrequest profiles.   Based on the http://build.fhir.org/ig/HL7/fhir-mCODE-ig/conformance-profiles.html  termination reason is thus not required.

      Description

      For medication administration and request profiles, we would not expect the reason for termination to be discretely documented in the chart as part of the medication data. Termination reason is routinely documented at the level of treatment plan, but not for individual medications within the plan. Requiring termination reason at the granularity of individual requests and administrations would be an obstacle to Epic EMRs sending data to mCODE requestors.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            samsahakian Sam Sahakian
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: