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

Purpose and intended users should be more clearly stated - MCODE #2

    XMLWordPrintableJSON

Details

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

      We thank the user for this comment. Grahame Grieve has said there are four types of IGs:

      • Base National Implementation Guide
      • Domain of Knowledge IG
      • Community of Implementation
      • Product Implementation Guide

      The definitions are given here: https://github.com/FHIR/documents/blob/master/presentations/2019-09%20IG%20Training/2019-09%20FHIR%20IG%20Review.pptx

      In these terms, the mCODE is a "Domain of Knowledge" IG. It shows how to represent clinical concepts generally, but does not have a complete set of specific agreements for interoperable exchanges. The purpose is to provide consistent data definitions for many or all exchanges involving cancer data. mCODE is the foundation for later definition of these exchanges.

      We will document this purpose more explicitly and completely in the introduction to mCODE.

      Resolution: Persuasive.

      Show
      We thank the user for this comment. Grahame Grieve has said there are four types of IGs: Base National Implementation Guide Domain of Knowledge IG Community of Implementation Product Implementation Guide The definitions are given here:  https://github.com/FHIR/documents/blob/master/presentations/2019-09%20IG%20Training/2019-09%20FHIR%20IG%20Review.pptx In these terms, the mCODE is a "Domain of Knowledge" IG. It shows how to represent clinical concepts generally, but does not have a complete set of specific agreements for interoperable exchanges. The purpose is to provide consistent data definitions for many or all exchanges involving cancer data. mCODE is the foundation for later definition of these exchanges. We will document this purpose more explicitly and completely in the introduction to mCODE. Resolution: Persuasive.
    • Richard Esmond/Kurt Allen: 10-0-1
    • Clarification
    • Non-substantive

    Description

      Comment:

      The purpose of this IG is not entirely clear. Who are the intended users, especially who are the intended receivers? The sending/receiving details can only be found in the implementation notes, so it's not even clear that the focus is on data exchange. The existing wording in the background makes it sound like the purpose is to define what information EHRs should capture, rather than on what and how they should exchange the information. The purpose and intended users should be clearly stated on the home page.

      Summary:

      Purpose and intended users should be more clearly stated

      Attachments

        Activity

          People

            c.potteiger Caroline Potteiger
            nedragarrett Nedra Garrett (Inactive)
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: