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

ReasonCode and ReasonReference in CancerSurgicalProcedure Required?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Interoperability Council
    • Profiles
    • Hide

      We believe the Reason elements should remain Must Support.

      • Recording of ReasonCode and/or ReasonReference for surgery occurs in billing data but may not be recorded in EHRs. If mCODE requires at least one of these, procedures that have no recorded reason could be missed. 
      • Even without a Reason, the code can identify potential cancer-related surgeries (for example, descendants of "Excision of Neoplasm" in SNOMED-CT). 
      Show
      We believe the Reason elements should remain Must Support. Recording of ReasonCode and/or ReasonReference for surgery occurs in billing data but may not be recorded in EHRs. If mCODE requires at least one of these, procedures that have no recorded reason could be missed.  Even without a Reason, the code can identify potential cancer-related surgeries (for example, descendants of "Excision of Neoplasm" in SNOMED-CT). 
    • Mark Kramer/Daniel Rutz: 7-0-0

    Description

      Both ReasonCode and ReasonReference are required if known for CancerRelatedSurgicalProcedure, yet it is one of these elements that determines the cancer-related nature of the procedure. From the profile's description:

      The scope of this profile has been narrowed to cancer-related procedures by constraining the ReasonReference and ReasonCode to cancer conditions.

      These elements are marked as MS, but we should consider an invariant/guidance indicating one of the fields must be populated.

      Attachments

        Activity

          People

            Unassigned Unassigned
            c.potteiger Caroline Potteiger
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: