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

Ensure alignment with caDSR and EVS terminologies - MCODE #7

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • Clinical Interoperability Council
    • (NA)
    • Hide

      Over the past 4 year, a large community has come together around mCODE. It has been proven in multiple use cases, and other implementers and adopters are not raised this issue. Given the existence of multiple standards, any standard, mCODE included, will not please everyone all the time. So the recommendation is not to pursue changes to mCODE terminology and data structures along the lines indicated in this issue.

      Show
      Over the past 4 year, a large community has come together around mCODE. It has been proven in multiple use cases, and other implementers and adopters are not raised this issue. Given the existence of multiple standards, any standard, mCODE included, will not please everyone all the time. So the recommendation is not to pursue changes to mCODE terminology and data structures along the lines indicated in this issue.
    • Jim McClay/Saul Kravitz :8-0-0

    Description

      Comment:

      Hopefully NCI has been involved in this project because many institutions have to use their standards. We are mandated to use the caDSR and EVS terminologies!

      Summary:

      Ensure alignment with caDSR and EVS terminologies

      Attachments

        Activity

          People

            may_terry May Terry
            anita_walden2 Anita Walden
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: