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

Re: New extended patient journey example: Does this help readers understand how mCODE might be applied to the real world?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Published (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive
    • Specification:
      US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • Raised in Version:
      1.0.1
    • Work Group:
      Clinical Interoperability Council
    • Related Page(s):
      Extended Example
    • Grouping:
    • Resolution Description:
      Hide

      Need to restructure presentation of content of example. 

      Show
      Need to restructure presentation of content of example. 
    • Resolution Vote:
      Sharita Alai/Jimmy Tcheng:11-0-0
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Does this help readers understand how mCODE might be applied to the real world?  Frankly not much help at all.   It would be much more understandable if the reader was walked through the story by annotated in-line which profiles represented what part.   ( ie,  "here is patient x  represented by this MCode resource ...".) than just listing 2 dozen resources after it.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ehaas Eric Haas
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: