1 / 19

GCPR - Modeling Discussion September 1999 HL7 Meeting Atlanta, Georgia

GCPR - Modeling Discussion September 1999 HL7 Meeting Atlanta, Georgia. Discussion Group. Dr. Mike Lincoln - VA Dr. Tim Mayhew - IHS Dr. Terry Clark - VA Dr. Steve Brown - VA Mr. Steve Wagner - VA Mr. Marco Johnson - DoD Ms. Nancy Orvis - DoD Mr. Ken Rubin - VA/EDS

jalila
Download Presentation

GCPR - Modeling Discussion September 1999 HL7 Meeting Atlanta, Georgia

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. GCPR - Modeling DiscussionSeptember 1999 HL7 MeetingAtlanta, Georgia

  2. Discussion Group • Dr. Mike Lincoln - VA • Dr. Tim Mayhew - IHS • Dr. Terry Clark - VA • Dr. Steve Brown - VA • Mr. Steve Wagner - VA • Mr. Marco Johnson - DoD • Ms. Nancy Orvis - DoD • Mr. Ken Rubin - VA/EDS • Mr. John Leslie - Litton/PRC • Capt Jim McCain - IHS

  3. WHAT IS THE GCPR FRAMEWORK?

  4. GCPR Utility Service Concept Data elements 1, 2, 3, 5, 6, 7 Materiau rudiments une, deaux, trois Requisition de rancard Request for Information Entropie Anforderung Datei funf, sechs, sieben

  5. High-level Architecture Model

  6. Data Management Model

  7. Security Component • Ensure client/population information is available to authorized users only • Guiding legislation • Federal Privacy Act • Health Insurance Portability and Accountability Act, 1996

  8. Common InformationModel/Data Representation • Identify and model common data elements • Maximize use of established data standards • Facilitate collaborative development of additional standards by academic, industry and government agencies

  9. Phase I - Development • Develop and maintain Reference Information Model (RIM) for clinical information domains. • (ongoing activity) • Develop heritage/legacy system interfaces • (agency unique activity, ongoing). • Establish security standards and authorities. • Design and develop the technical environment. • Proof-of-Concept Testing. • Prototype Demonstration.

  10. Phase I -Government Tasks/Responsibilities • Model Selection • Select baseline information models • Document adopted terminology models • Model Development • Identify trigger/events and data elements by domain expert focus groups • Produce electronic format of model for hand-off • Model Maintenance • Ongoing maintenance of information and terminology models • Heritage/Legacy System Interfaces • Establish Common Security Standards • Identify and document common policies and methods. • Ensure compliance with key regulations/laws.

  11. Draft for Discussion Only Framework Version 1 • Model • (5 Partitions) • Person (MPI) • Laboratory • Patient Record • Architecture • Security • Continuity of Care • Model • (6 Partitions) • Problem Lists • Medication Profiles • Allergies • Imaging Results • Immunizations • Vital Signs Deploy V1 ……………… Build & Alpha V1 Refine & Beta V1 Phase III Framework Version 2 Model (4 Likely Partitions) Outpatient Encounter Notes Narrative Summaries Physical Exams Consult Tracking Build & Alpha V2 Refine & Beta V2 Deploy V2 … EXPECTED GCPR FRAMEWORK TIMELINE Nov ‘00 - Mar ‘01 Apr ‘01 ………………………………… Nov ‘99 - Mar ‘00 Apr ‘00 - Oct ‘00 5 Months 7 Months 6 Months Phase I Phase II Apr ‘01 - Aug ‘01 Sep ‘01... Nov ‘00 - Mar ‘01 May ‘00 - Oct ‘00 5 Months 5 Months 6 Months

  12. GCPR Modeling Discussion

  13. GCPR GRM • GRM Goals • Brief History • Role of HL7 • Role of other Standards Models • Where we are

  14. GCPR GRM -- The Present • Status of the GRM • Gaps in the model • Identified collaboration opportunities with HL7

  15. GRM -- The Future • GRM = Domain Model + Computational • Cornerstone Deliverables • GRM Product Description Document • GRM Modeling Approach Document • GRM Utilization Guide(s) • HL7 “Rules of Engagement” Approach

  16. GRM and HL7: Open Questions 1) When should we engage HL7? 2) How should we engage HL7? 3) What should be done informally vs formally? 4) Whom should be engaged? 5) When does the Govt SIG become involved?

  17. GRM and HL7: Current CONOPS • Refine and extend the model • Security Example (RIM) • Language Example (RTM) • Forward and backward harmonization • Propose extensions but continue working (e.g., cannot risk HL7 interdependency with project timelines) • Role of GRM Team and HL7

  18. Symbiotic Outcomes (for GCPR) • Ability to leverage significant existing work (Utilization of RIM 3.0) • Field-test HL7 Clinical Templates • Tap into existing expertise and knowledgebase (for HL7) • Refine and contribute to areas of the RIM 3.0 model (i.e. security) • Gained experience in applying the model both to large provider environment and via current technology • Terminology refinement and detail definition • Creation of HL7 Clinical Templates • Greater involvement in SIGS and Technical Committees Others?

  19. Next Steps...

More Related