1 / 9

MHS Information Model Update 13 March 2008 Skyline 3, Conference Room 2

MHS Information Model Update 13 March 2008 Skyline 3, Conference Room 2 Information Model Team. Purpose of IM effort. Semantic interoperability between all systems within the MHS as well as new COTS packages

idania
Download Presentation

MHS Information Model Update 13 March 2008 Skyline 3, Conference Room 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MHS Information Model Update 13 March 2008 Skyline 3, Conference Room 2 Information Model Team

  2. Purpose of IM effort • Semantic interoperability between all systems within the MHS as well as new COTS packages • Mapping to service partners, federal partners, and industry standards to ensure continued alignment with their systems • Provide complete data elements to add detail to other IRD artifacts (i.e. BPMN)

  3. COTS FAM-D MHS Information Model Map Map MHS Core Information Model Legacy Map Map RIM specific data Map Map VHIM HEMS Overall approach • Core Information Model will be determined from: HL7 RIM, HEMS, FAM-D, and VHIM • Complete MHS Information model will be canonical for all IMs below to ensure interoperability

  4. Project Timeline

  5. Project Timeline • Future High level Tasks

  6. Deliverables Tied to tasks within the project plan

  7. Questions

  8. Backup Slides - Criteria • Applicability to Current Systems • Alignment with CDR, time to map between architecture • Alignment with AHLTA • Applicability to New Development (COTS) • Time to map Information Model to COTS products • Time to map Information Model to meet standards (HL7, CCHIT, etc) • Applicability to DoD/VA Integration • Time to map to VA model (or new Joint Information Model?) • Alignment with DoD Strategic Goals / DoD Business Users • Easily understandable • Condition of data (structured? Is it in a standard format?) • Provides value to technical users to understand business issues • Helps business users understand technical issues • Helps clarify and strengthen contract language • Supports new architectural development process • Detail Level • Difficulty to Complete Model/Completeness of the Model • Ability to Support the Medical Mission • Ability to Put in Public Domain • Condition of Supporting Documentation • Support Availability

  9. Backup Slides - Tasks

More Related