Problem and Target Outcome

Problem:

EHRs and other data systems are not yet capable of providing cancer patient data that conforms to the mCODE standard.

Target Outcome:

Patient mCODE data is available to any workflow in standard, HL7 FHIR resources.

mCODE Extraction Details
Actor	Any workflow where mCODE data is required for execution.
Description	A workflow requires access to a patient's data described by mCODE.
Trigger	Any CodeX or mCODE use case trigger.
Preconditions	Required patient data exists in a structured computable format in an EHR or other health IT application.
Postconditions	A set of FHIR resources populated with data as defined in the mCODE standard is available for any workflow.
Extensions	N/A
Assumptions	See precondition.
Scope	Retrieval of patient data as defined by mCODE.
Notes	The mCODE Extraction use case defines a software engineering framework and reference implementation for EHR or health IT developers to use as a basis for developing server specific mCODE extraction. A subset of mCODE elements is targeted for the first phase: Cancer Disease Status, Treatment Plan Change, general patient demographics and clinical trials data.

Quick Links:

mCODE++ Extraction One-Pager

mCODE++ Extraction Framework on Github

Conference Call Information

At this time, there are no specific conference calls for the extractor. If you'd like to learn more about the extractor, please reach out to any member of the use case team below. If you'd like to obtain or help develop the extractor, please join the effort on GitHub.

Important Dates

Event	Date/Time

Use Case Team

Role	Name	Organization	Email
Domain Co-Lead	Zeshan Rajput	The MITRE Corporation	zrajput@mitre.org
Technical Lead	Dylan Phelan	The MITRE Corporation	dphelan@mitre.org
Project Co-Lead	Maura Huff	The MITRE Corporation	mhuff@mitre.org

Space shortcuts

Page tree

Problem and Target Outcome

Quick Links:

Pilot Plan

Conference Call Information

Important Dates

Use Case Team