This wiki has undergone a migration to Confluence found Here
Difference between revisions of "MCODE FHIR IG Proposal"
Jump to navigation
Jump to search
| (30 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR IG Proposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR IG Proposal]] | [[Category:FHIR IG Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR IG Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE)= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 31: | Line 31: | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | ||
| + | May 23 2019 | ||
==Publishing Lead== | ==Publishing Lead== | ||
<!--Name and email of the primary contact for the FMG with respect to publishing for this IG?--> | <!--Name and email of the primary contact for the FMG with respect to publishing for this IG?--> | ||
| + | Publishing Facilitator (per PSS): Laura Heerman Langford (Laura dot Heermann at imail dot org) | ||
| + | |||
| + | Technical IG Publisher Lead: Chris Moesel (cmoesel at mitre dot org) | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | ||
| − | * | + | * Clinical Information Modeling Initiative WG |
| − | * | + | * Clinical Genomics WG |
| − | * | + | * Public Health WG |
==FHIR Development Project Insight ID== | ==FHIR Development Project Insight ID== | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
| + | 1509 [https://confluence.hl7.org/pages/viewpage.action?pageId=40737853] | ||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 58: | Line 63: | ||
* Locale: Country, region | * Locale: Country, region | ||
--> | --> | ||
| + | This IG covers elements that are key for cancer management and care according to US clinical practice, including patient demographics, details about the disease and treatment, as well as outcomes. It is intended to provide a standard for data gathered from clinician-patient interactions that take place during routine healthcare delivery, and leveraging this "real world data" for other applications, such as quality measurement, comparative effectiveness research, and shared decision making. The IG aligns with other relevant US-realm FHIR IGs, such as the Argonaut Data Query IG. | ||
==Content location== | ==Content location== | ||
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | <!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | ||
| − | + | https://github.com/HL7/fhir-mCODE-ig | |
==Proposed IG realm and code== | ==Proposed IG realm and code== | ||
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir? E.g. us/ccda --> | <!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir? E.g. us/ccda --> | ||
| + | us/mcode | ||
==Maintenance Plan== | ==Maintenance Plan== | ||
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources. I.e. Who will be maintaining this IG content 5 years after it's published? --> | <!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources. I.e. Who will be maintaining this IG content 5 years after it's published? --> | ||
| + | |||
| + | mCODE is a large, highly visible initiative sponsored by the American Society of Clinical Oncology (ASCO) and developed in partership with the MITRE Corporation, in consultation with the Biden Cancer Initiative and the National Cancer Institute (NCI). ASCO has has established a governance body for mCODE through its Executive Committee, and there is commitment from the CIC WG to maintain the IG. Specifically, the MITRE Corporation is committed to maintaining the mCODE IG. | ||
==Short Description== | ==Short Description== | ||
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry- this is the sentence that will be used here: http://www.fhir.org/guides/registry. This must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. --> | <!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry- this is the sentence that will be used here: http://www.fhir.org/guides/registry. This must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. --> | ||
| − | + | This IG specifies a core set of common data elements for cancer that is clinically applicable in every electronic patient record with a cancer diagnosis. It is intended to enable standardized information exchange among EHRs/oncology information systems and reuse of data by other stakeholders (e.g. quality measurement, research). | |
==Long Description== | ==Long Description== | ||
<!-- 1-2 paragraphs describing the purpose/scope of the IG in more detail for inclusion in the version history - this is content that will be used in your IG's equivalent of this: http://www.hl7.org/fhir/us/core/history.cfml. Again, this must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. --> | <!-- 1-2 paragraphs describing the purpose/scope of the IG in more detail for inclusion in the version history - this is content that will be used in your IG's equivalent of this: http://www.hl7.org/fhir/us/core/history.cfml. Again, this must describe the IG from the perspective of an implementer scanning a registry, it should not talk about the project and should NOT be copied from the PSS. --> | ||
| − | + | mCODE™ —short for Minimal Common Oncology Data Elements—is an initiative intended to assemble a core set of structured data elements for oncology electronic health records (EHRs). The goal is to facilitate cancer data interoperability and improve overall cancer data quality for patient care and research by establishing a set of elements that would form the basic data that would populate all EHRs for patients with cancer. mCODE™ has been created and is being supported by the American Society of Clinical Oncology (ASCO®) in collaboration with the MITRE Corporation. | |
| + | mCODE™ consists of a core set of structured data elements necessary to support clinical care and oncology research across all cancers. | ||
==Involved parties== | ==Involved parties== | ||
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG **for inclusion in the version history**. Don't copy from the PSS - think about the specific language you want to appear in the registry. --> | <!-- 1 paragraph describing who is sponsoring or involved in creating the IG **for inclusion in the version history**. Don't copy from the PSS - think about the specific language you want to appear in the registry. --> | ||
| − | + | This guide was authored by the MITRE Corporation with extensive content expertise provided by the American Society for Clinical Oncology (ASCO), CancerLinQ, and with input and contributions from the HL7 community, including the Clinical Interoperability Council WG (sponsor), the Cancer Interoperability Project Group, Clinical Information Modeling Initiative WG (co-sponsor), the Clinical Genomics WG, and the Public Health WG. | |
==Expected implementations== | ==Expected implementations== | ||
<!--Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | This IG is already being used for a couple of applications: | ||
| + | |||
| + | * Creating a “patients like this” comparative effectiveness tool, designed to be used by clinicians and patients to improve shared decision-making when it comes to cancer treatment options. The tool extracts mCODE data and deliver reports to providers and patients—empowering shared decision making (currently under implementation with Intermountain Health Care) | ||
| + | * Using mCODE to support data collection for clinical trials with the goal to validate the clinical endpoint data collected via the EHR, by showing that it matches the results obtained using standard study-specific electronic case report forms (currently being implemented in iCAREData project, in partnership with the Alliance for Clinical Trials in Oncology, Brigham and Women's Hospital and the Dana-Farber Cancer Institute). | ||
==Content sources== | ==Content sources== | ||
| Line 96: | Line 110: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | * North American Association of Central Cancer Registries (NAACCR) version 18 | ||
| + | * American Joint Committee on Cancer (AJCC) Staging Manual (8th Edition) | ||
| + | * HL7 FHIR Implementation Guide: Genetic Reporting STU 1 | ||
| + | * HL7 Domain Analysis Model: Clinical Genomics Release 1 | ||
| + | * HL7 CDA® Release 2 Implementation Guide: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1, DSTU Release 1.1 – US Realm | ||
| + | * HL7 FHIR Implementation Guide: Breast Cancer Data, Release 1 - US Realm | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | ||
| + | * Use in comparative effectiveness and shared-decision making tools | ||
| + | * Data collection for clinical trials | ||
==IG Relationships== | ==IG Relationships== | ||
<!-- Are there any IGs this resource depends on or that depend on this IG? --> | <!-- Are there any IGs this resource depends on or that depend on this IG? --> | ||
| + | This IG depends on Argonaut Data Query IG/US Core. There are also some inter-dependencies with the Genomics Reporting FHIR IG. | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | Currently targeting the September 2019 ballot, so IG would be ready by early August. | ||
==When IG Proposal Is Complete== | ==When IG Proposal Is Complete== | ||
Latest revision as of 21:49, 29 May 2019
This page documents a Approved FHIR IG Proposal
Contents
- 1 HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE)
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Publishing Lead
- 1.4 Contributing or Reviewing Work Groups
- 1.5 FHIR Development Project Insight ID
- 1.6 Scope of coverage
- 1.7 Content location
- 1.8 Proposed IG realm and code
- 1.9 Maintenance Plan
- 1.10 Short Description
- 1.11 Long Description
- 1.12 Involved parties
- 1.13 Expected implementations
- 1.14 Content sources
- 1.15 Example Scenarios
- 1.16 IG Relationships
- 1.17 Timelines
- 1.18 When IG Proposal Is Complete
- 1.19 FMG Notes
HL7 FHIR Implementation Guide: minimal Common Oncology Data Elements (mCODE)
Owning work group name
Clinical Interoperability Council
Committee Approval Date:
May 23 2019
Publishing Lead
Publishing Facilitator (per PSS): Laura Heerman Langford (Laura dot Heermann at imail dot org)
Technical IG Publisher Lead: Chris Moesel (cmoesel at mitre dot org)
Contributing or Reviewing Work Groups
- Clinical Information Modeling Initiative WG
- Clinical Genomics WG
- Public Health WG
FHIR Development Project Insight ID
1509 [1]
Scope of coverage
This IG covers elements that are key for cancer management and care according to US clinical practice, including patient demographics, details about the disease and treatment, as well as outcomes. It is intended to provide a standard for data gathered from clinician-patient interactions that take place during routine healthcare delivery, and leveraging this "real world data" for other applications, such as quality measurement, comparative effectiveness research, and shared decision making. The IG aligns with other relevant US-realm FHIR IGs, such as the Argonaut Data Query IG.
Content location
https://github.com/HL7/fhir-mCODE-ig
Proposed IG realm and code
us/mcode
Maintenance Plan
mCODE is a large, highly visible initiative sponsored by the American Society of Clinical Oncology (ASCO) and developed in partership with the MITRE Corporation, in consultation with the Biden Cancer Initiative and the National Cancer Institute (NCI). ASCO has has established a governance body for mCODE through its Executive Committee, and there is commitment from the CIC WG to maintain the IG. Specifically, the MITRE Corporation is committed to maintaining the mCODE IG.
Short Description
This IG specifies a core set of common data elements for cancer that is clinically applicable in every electronic patient record with a cancer diagnosis. It is intended to enable standardized information exchange among EHRs/oncology information systems and reuse of data by other stakeholders (e.g. quality measurement, research).
Long Description
mCODE™ —short for Minimal Common Oncology Data Elements—is an initiative intended to assemble a core set of structured data elements for oncology electronic health records (EHRs). The goal is to facilitate cancer data interoperability and improve overall cancer data quality for patient care and research by establishing a set of elements that would form the basic data that would populate all EHRs for patients with cancer. mCODE™ has been created and is being supported by the American Society of Clinical Oncology (ASCO®) in collaboration with the MITRE Corporation. mCODE™ consists of a core set of structured data elements necessary to support clinical care and oncology research across all cancers.
Involved parties
This guide was authored by the MITRE Corporation with extensive content expertise provided by the American Society for Clinical Oncology (ASCO), CancerLinQ, and with input and contributions from the HL7 community, including the Clinical Interoperability Council WG (sponsor), the Cancer Interoperability Project Group, Clinical Information Modeling Initiative WG (co-sponsor), the Clinical Genomics WG, and the Public Health WG.
Expected implementations
This IG is already being used for a couple of applications:
- Creating a “patients like this” comparative effectiveness tool, designed to be used by clinicians and patients to improve shared decision-making when it comes to cancer treatment options. The tool extracts mCODE data and deliver reports to providers and patients—empowering shared decision making (currently under implementation with Intermountain Health Care)
- Using mCODE to support data collection for clinical trials with the goal to validate the clinical endpoint data collected via the EHR, by showing that it matches the results obtained using standard study-specific electronic case report forms (currently being implemented in iCAREData project, in partnership with the Alliance for Clinical Trials in Oncology, Brigham and Women's Hospital and the Dana-Farber Cancer Institute).
Content sources
- North American Association of Central Cancer Registries (NAACCR) version 18
- American Joint Committee on Cancer (AJCC) Staging Manual (8th Edition)
- HL7 FHIR Implementation Guide: Genetic Reporting STU 1
- HL7 Domain Analysis Model: Clinical Genomics Release 1
- HL7 CDA® Release 2 Implementation Guide: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1, DSTU Release 1.1 – US Realm
- HL7 FHIR Implementation Guide: Breast Cancer Data, Release 1 - US Realm
Example Scenarios
- Use in comparative effectiveness and shared-decision making tools
- Data collection for clinical trials
IG Relationships
This IG depends on Argonaut Data Query IG/US Core. There are also some inter-dependencies with the Genomics Reporting FHIR IG.
Timelines
Currently targeting the September 2019 ballot, so IG would be ready by early August.
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
