Orders and Observations
Laboratory (Archived) Anatomic Pathology (Archived) Clinical Statement (Archived)Project Summary for Medicaid Information Technology Architecture (MITA) Project
Visit Project Insight to see the full project details.
Project Details
Number | 332 View Ballot Items List (with NIBs) |
---|---|
Name | Medicaid Information Technology Architecture (MITA) Project |
Sponsor(s) | Financial Management Work Group |
Co-Sponsor(s) | |
Steering Division | Administrative |
Description | Within the context of the Medicaid Information Technology Architecture [MITA] this project will demonstrate that following the HL7 Development Methodology, building interoperable Models using UML and Standard tools, with Open Collaboration results in products that are sufficient to meet the needs of the Medicaid Community. Brief Background: CMS believes improved Data Quality and Interoperability is the key to our future and that the true value of data is realized only to the extent it can be shared across 'organizational silos'. System interoperability is absolutely essential to facilitate changes. CMS and Medicaid administrators recognized the lack of a comprehensive view of the overarching Medicaid world. Medicaid Management Information Systems [MMIS] were not keeping pace with a rapidly changing health care environment. Medicaid recipients come from a variety of backgrounds with many, and in some cases complex, care coordination needs. Clinical information to make decisions has been difficult to obtain and share among the agencies responsible [Medicare, Medicaid, Commercial Insurance, Indian Health Services, etc.] CMS recognized the need to re-tool the MMIS. The result is The MITA: - Web-based, patient-centric, interoperable system based on industry IT standards - Enterprise-oriented, rather than organization - Data shared across boundaries - Provides basis for HIT/E -- EHR, eRx, PHR - Technology Neutral Additional information regarding the MITA can be found at: http://www.cms.hhs.gov/MedicaidInfoTechArch/ Recognizing the need to re-tool and creation of the MITA goals identified additional needs: - Introduction of consistency. - Broad-based participation of a variety of stakeholders - Defined steps - for achieving consensus and development of shared information - Processes for sharing information 'beyond the walls' of established partner relationships - Tools for building, sharing, storing, etc. information - Access to individuals with key industry, development and design knowledge will the ability and will to mentor These needs can be met by HL7. HL7 provides the MITA a 'sandbox' and the tools needed for successful transformation to MITA, There are a vast array of capabilities needed to transform the MITA Business Architecture into the MITA Information Architecture including tools for capturing business process artifacts - the trigger events, preconditions, post conditions, steps, shared data - and converting these into the UML models needed to generate WSDLs. HL7 follows the ANSI consensus process to ensure that all stakeholders have an opportunity to collaborate and have their business requirements addressed. HL7 comes 'pre-loaded' with data models for many of the types of business processes that MITA will use, e.g., Member and Provider Registries, Accounting, Billing, Care Management, Clinical Models for Medications, Summary Records, as well as support for Privacy Consents and Security. The MITA Project can refine these models, add Medicaid classes and attributes, - and adapt and extend the sizable HL7 vocabulary for Medicaid purposes, working within HL7 to ensure that the MITA is aligned with other national healthcare initiatives such as the National Health Information Network being developed through the Office of the National Coordinator. |
Project Facilitator | Mary Kay McDaniel, |
Status | Archived |
SD Approval Date | Sep 24, 2007 |
TSC Approval Date | Sep 24, 2007 |
Project Type | |
Objectives / Deliverables | Target MITA Business Process Models and produce all HL7 Development Framework [HDF] [V.3] artefacts: - Storyboard, storyboard example - State Transition Diagrams, trigger events - Interaction Diagram, interactions - Message Information Models, Refined Message Information Models - Hierarchical Message Definitions This project will model a select subset of MITA business processes, e.g. provider enrolment business process model and information models using the HDF. The selected subset will be limited to one business process model from the following Financial Management list: 1. Accounts, including patient billing, bad debt, credit card, general ledger and cash accounts. Accounts may be referenced either singularly or in combination by cost center, fiscal year, accounting period, guarantor, patient and/or encounter, 2. Financial transactions such as journal or voucher entries, funds transfer requests and posted transactions including charges and payments, 3. Claims or Invoices for services provided and/or goods delivered including adjudication results, 4. Confirmations including authorizations and eligibility queries, and 5. Financial contracts such as insurance plans, enrolments, insurance policies and fee schedules. Interim Goal: Provider Enrolment Business Model completed by September 2008 Style Guide. The style guide, as the name suggests, is the precursor to any future domain-specific work. To ensure that each team participating in the MITA project is developing consistent artifacts, we need a common style guide. The style guide will include patterns and guidances on the use of the modeling language and tools. It needs to be reviewed and vetted to ensure that it meets the needs of this community. |
Next Milestone Date | Date Not Determined |
Project End Date | Date Not Determined |
Project Intent | |
Project Need | |
Success Criteria | |
Dependancies | Volunteers with SME MITA knowledge and other volunteers with HL7 development methodology to mentor the group. |
Collaboration Efforts | |
Ballot Cycle Info | |
Misc Notes | May 2011: The TSC approved a petition to withdraw a proposed ANS (American National Standard), previously balloted as DSTU under Project Insight ID# 332 as both projects have been terminated: HL7 Version 3 Standard: Medicaid Information Technology Architecture (MITA) Style Guide, Release 1, from September 2008 Ballot Cycle, and HL7 Version 3 Standard: Medicaid Information Technology Architecture (MITA) Development Framework, Release 1 (US Realm), from January 2009 Ballot cycle. PMO archived project. 2010July: updated project repository URL Sept. 2009: There are three separate teams (Business Process Team, Data Analytics Team, Modelers Team) working on tasks within this project umbrella. May be easier to track using 3-Year Plan activities. PMO to meet with FM rep(s) to discuss how best to track this in PI. |
Product Type | |
Project Document Repository | http://mita.wikispaces.com/ |
Backwards Compatibility | |
Stakeholders | |
Vendors | |
Providers | |
SDO/Profilers | |
Realms | - Choose One - |
HL7 Affiliate | |
Roadmap Reference | |
Start Date | Sep 24, 2007 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at pmo@HL7.org for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.