Thread by @TravisOsterman

1/ Here is an update on the current status of #mCODE (thread format) based on the Cancer Data Summit @MITREcorp mitre.org/cancer-data-su…

2/ APPROVED: #mCODE 0.91 was approved by @HL7 as a Standard for Trial Use (STU) - congrats

3/ DATA GAPS: We still struggle to capture #cancer disease status in the #EHR. Cancer staging and status are not the same - stable disease, progression, etc.

4/ IMPLEMENTORS: If you're interested in building on the #mCODE data standard, check out the CodeX @HL7 #FHIR Accelerator confluence.hl7.org/download/attac… and here is the implement guide hl7.org/fhir/us/mcode/…

5/ INTERNATIONALIZATION: We need to ensure that #mCODE can be implemented in non-US countries. Specifically, this applies to which ontologies are tied to #mCODE

6/ PILOTS: Compass is running at @intermtncancer and was updated by @MVanMeterMD and iCARE icaredata.org is running at @ALLIANCE_org, both using @HL7 #FHIR R4

7/ CLINICAL TRIAL MATCHING: while #mCODE is more than clinical trial matching, lots of excitement about improving clinical trial matching through data standards. Specifically, a need to improve how we store inclusion/exclusion criteria about trials.

8/ MORE INFO: Current #mCODE version (0.91) and more information available at mcodeinitiative.org

9/ A giant thank you to so many for this effort @intermtncancer @MITREhealth @theNCI @HL7 @BrighamWomens @ASCO @FDAOncology @MITREcorp @ALLIANCE_org @MVanMeterMD @rsm2800 @cjaffemd @VictorDzau @bertagnollimm @jhalamka @davidbutlermd @rschilsky #mCODE