Assessments of a health-related matter of interest, importance, or worry to a patient, patient’s family, or patient’s healthcare provider that could identify a need, problem, or condition.

Data Element
M3 Results
Description

M3 Results is the output from an evidence-based, 27 question, patient rated cross cutting mental health assessment. The output is a score that is highly predictive of any mental health condition, 4 clusters for risk of anxiety, PTSD, bipolar disorder and depression and the responses to the 27 questions. Together the data elements provide clinicians and patients results that enable de-stigmatized care by providing scores and longitudinal monitoring based on those scores to hopefully drive better outcomes. M3 is used by LabCorp and others and qualifies for a Standard based on its interoperability through their network.
Submitted By: Michael Byer / M-3 Information, LLC
Data Element Information
Rationale for Separate Consideration The are data elements for other mental health assessments such as the PHQ-9 and the GAD-7 which are siloed assessments looking to diagnose a single condition such as depression or anxiety. Research show that mental health is often a mix of symptoms so a cross-cutting measure that provides observations to the patients needs is more practical and clinically useful. Also M3 is amazingly compact meeting the sensitivity and specificity of the single condition assessments in less than half the questions while providing one organized overview.
Use Case Description(s)
Use Case Description For the most part mental health is detected and managed in primary care. Primary care has the responsibility of meeting a tough schedule and a long list of guidelines. The USPTF endorses that any person shown to be at risk of depression receive a deeper evaluation for other conditions such as anxiety, PTSD and bipolar disorder. The M3 meets this endorsement and having the data in the USCDI format would accelerate the access by clinicians of these needed metrics in the EMR with less specialty programming.

A secondary use case is in Behavioral Health which uses a different set of EMR's then primary or hospital system care and being included in the USCDI structure would provide the ability to provide a consistent measure that address these complex needs.
Estimate the breadth of applicability of the use case(s) for this data element All people above 18 should receive a mental health review each year. This would mean about 250 million people in the United States of which about 50 million would benefit from the more robust review provided by the M3.
Link to use case project page https://www.m3information.com/wp-content/uploads/m3process.pdf
Supporting Attachments M3-Checklist-Sample-Report-04232017.pdf
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) M3 has LOINC Codes

M3 Score is an algorithm to allow a person to take a rated self-test and their clinician receive a structured report which includes a score that shows: 1) an assessment of an individuals risk of suffering from any mood disorder, and 2) a patient on a clinical map showing if they have a low, medium or high risk for each of the following: Depression, Anxiety, Bipolar, PTSD. In addition to the clusters, the report the answers for each report are included as structured data with all scores and responses having LOINC codes.
https://loinc.org/71569-8/
Additional Specifications M3 is part of the Google Health Cloud where all elements have FHIR interoperability and for the elements not included there is a path back to HL-7. FHIR specifies a base set of resources that can be combined in various ways to meet the data model demands of healthcare providers. It also provides representations of clinical observations and documents. FHIR does not aim to encompass every possible document or data type; rather, FHIR first provides support for most clinical and billing use cases. You can then extend your FHIR implementation to meet additional clinical or organizational needs. M3 has an NPI Number allowing users to bill via a CPT code for scoring and reporting in all use cases leveraging the technical specs of FHIR R4. The Cloud Healthcare API’s FHIR implementation provides full support for FHIR DSTU2, STU3, and R4 resources.
Current Use This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders
Supporting Artifacts M3 is currently used in many settings including the assessment core of The Wounded Warriors, several Behavioral Health Centers, Population Management Health providers, Telehealth providers, and others.
https://www.ehcmp.com/
Extent of exchange 4
Supporting Artifacts LabCorp licenses the M3 and has provided the test to several of its practice clients through their API. Please see the supporting link below showing a "lab-like" report for each of the data elements in the M3 LOINC structure and the M3 report. This format is standard through all delivery settings.
https://www.labcorp.com/provider-services/programs/m3-checklist-multi-condition-mental-health-screening-tool
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) The use of the data elements is limited by the terms of the license described below.
Restrictions on Use (e.g. licensing, user fees) The M3 is a copy written assessment and is licensed to health organizations. M3 has a CPT Code to direct bill payers so users are able to license without charge.
Privacy and Security Concerns M3 is HIPPA compliant and provide best in class encryption to facilitate the safe exchange of information.
Estimate of Overall Burden We routinely provide organizations near-instant access to be able to administer, collect the individual reports, and aggregate the data with all types of care settings on a regular basis. in smaller settings there is a preference to use our links and data collection module and for larger systems to embed the M3 in their platform and map the results. The time to bring up either after the paperwork is less than an hour.
Other Implementation Challenges Other than the normal woes of the IT cue at many hospitals can think of few. Being able to provide several alternatives to interoperability has been useful in meeting the goals of a range of providers

Comment

Log in or register to post comments