1 / 28

HITSP Project Orientation

HITSP Project Orientation Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSS Vice President, Informatics, HIMSS. Agenda. 1. Welcome 2. HITSP Charter and Goals 3. Relationship between HITSP, HISPC and CCHIT

barbara-orien
Download Presentation

HITSP Project Orientation

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. HITSP Project Orientation Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSSVice President, Informatics, HIMSS

  2. Agenda 1. Welcome 2. HITSP Charter and Goals 3. Relationship between HITSP, HISPC and CCHIT 4. What is the HITSP process/structure?5. TC Specific Work:     a) What is a Harmonized Use Case?     b) What is a HITSP Construct?     c) Familiarization with existing HITSP Constructs 6. TC Tools:     a) ANSI Member Library     b) ANSI Public Library     c) Standing Meetings and Numbers 7. Questions

  3. In 2005, HHS awarded contracts to seed a public-private effort to build a nationwide health information network

  4. The Certification Commission for Healthcare Information Technology (CCHIT) Healthcare Information Technology Standards Panel (HITSP) American Health Information Community The Health Information Security and Privacy Collaboration (HISPC) Nationwide Health Information Network Architecture Projects(NHIN) A public-private “Community” was then established to serve as the focal point for America’s health information concerns and drive opportunities for increasing interoperability HITSP includes 351 different member organizations and is administered by a Board of Directors 24 SDOs (7%) 248 Non-SDOs (71%) 30 Govt. bodies (9%) 13 Consumer groups (3%) 36 Project Team and Undeclared (10%) The Community is a federally-chartered commission and will provide input and recommendations to HHS on how to make health records digital and interoperable, and assure that the privacy and security of those records are protected, in a smooth, market-led way.

  5. The HITSP team is charged with completing eleven different tasks, with current efforts focused on the harmonization process Eleven Tasks are included in this contract: • Comprehensive Work Plan • Conduct a Project Start Up Meeting • Deliver Recommended Use-Cases • Participate in related meetings and activities, including the AHIC Meetings • Develop a Gap Analysis • Standards Selection, Evaluations and Testing • Define a Harmonization Approach • Develop Interoperability Specifications • Develop and Evaluate a Business Plan for the self-sustaining processes • Submit Monthly Reports – ongoing efforts • Assist with communications – ongoing efforts The Community HHS Secretary Mike Leavitt, Chair HHS ONCHIT1 PO, Dr. John Loonsk HITSP Dr. John Halamka, Chair Member populated Technical Committees Project Management Team Executive in Charge, F. Schrotter, ANSI Program Manager, L. Jones GSI Deputy PM, J Corley, ATI Project Manager, Julie Pooley, Booz Allen Harmonization Process Definition Technical Manager Michelle Deane, ANSI Harmonization Process Delivery Technical Manager Joyce Sensmeier, HIMSS

  6. HITSP formed Technical Committees to focus on AHIC breakthrough areas - Initial focus is on 4 use cases Current HITSP Focus • Biosurveillance -- Transmit essential ambulatory care and emergency department visit, utilization, and lab result data from electronically enabled health care delivery and public health systems in standardized and anonymized format to authorized public health agencies with less than one day lag time. • Consumer Empowerment -- Deploy to targeted populations a pre-populated, consumer-directed and secure electronic registration summary. Deploy a widely available pre-populated medication history linked to the registration summary. • Electronic Health Records -- Deploy standardized, widely available, secure solutions for accessing laboratory results and interpretations in a patient-centric manner for clinical care by authorized parties. • Emergency Response EHR – Describes the role that an emergency responder electronic health record, comprising at minimum demographics, medication, allergy and problem list information, can be used to support emergency and routine health care activities.

  7. HITSP Coordinating Committees and Leadership • Foundations Committee • Steve Wagner • Bob Dolin • HITSP Process Review Committee • Lynne Gilbertson • Erik Pupo • HITSP-CCHIT Joint Work Group • Jamie Ferguson, Kaiser Permanente • Harmonization Readiness Committee • Lynne Gilbertson • Business Plan Committee • Steve Lieber • International Landscape Committee • Bill Braithwaite • Governance Committee • Michael Aisenberg

  8. HITSP Technical Committees and Leadership • HITSP Technical Committee - Care Delivery • James Ferguson, Kaiser Permanente • Steve Hufnagel, DoD • Steve Wagner, Department of Veterans Affairs • HITSP Technical Committee - Consumer Empowerment • Elaine Blechman, PhD, University of Colorado, Boulder • Charles Parisot, EHR Vendor Association • Scott Robertson, Kaiser Permanente • HITSP Technical Committee- Population Health • Floyd Eisenberg, MD, MPH, Siemens Medical Solutions • Peter Elkin, MD, Mayo Clinic College of Medicine • Shaun Grannis, Department of Family Medicine, Indiana University School of Medicine • HITSP Technical Committee – Security and Privacy • Glen Marshall, HL7 • Walter Suarez, HIPAA/HIT • John Moehrke, GE Healthcare

  9. HITSP project team and staff supports each Technical Committee • HITSP Technical Committee- Care Delivery • Don Van Syckle, DVS Consulting • HITSP Technical Committee- Consumer Empowerment • John Donnelly, IntePro Solutions, Inc. • HITSP Technical Committee- Population Health • Lori Reed-Fourquet, e-HealthSign LLC • HITSP Cross-Technical Committee Coordination • Bob Yencha, Alschuler Associates • HITSP Security and Technical Committee Coordination • Johnathan Coleman CISM, CISSP, Security Risk Solutions, Inc. • HITSP Emergency Responder-EHR Coordination • Michael Glickman, Computer Network Architects, Inc.

  10. HITSP Technical Committees Terms of Reference • Perform high level Requirements Analysis and Design of HITSP Interoperability Specifications, transaction packages, transactions, components, constructs including requirements analysis, and minimum data set. • Identify and analyze gaps and duplications within the standards industry as they are related to each specific Use Case. • Provide a description of the gaps, including missing or incomplete standards. • Provide a description of the duplications, overlaps, or competition among standards for the relevant Use Case. • Review and scope statements of work for each new use case. • Provide a listing of all standards that satisfy the requirements imposed by the relevant use cases as well as readiness criteria that shall be used to evaluate the standard. • Select and evaluate recommended standards to meet the relevant Use Case. • Develop, review and evaluate ‘interoperability specifications’ for the selected standards. • Submit recommendations to HITSP for review, approval and resolution. • Ensure timely response and disposition of comments. • Ensure on-going process for addressing corrections/change requests and resolutions.

  11. Security and Privacy Technical Committee Terms of Reference/Charter • Harmonize HITSP standards for EHR-Lab reporting, Population Health and Consumer Empowerment with relevant Security and Privacy standards, including the HIPAA Security and Privacy Rules, and basic consents, where appropriate. • Assemble HITSP Security and Privacy Work Group (SPWG) with adequate representation from each TC. • Convene regular meetings of the SPWG to review current Interoperability Specifications and identify areas of Security and Privacy that were deferred. • Begin work on identifying security standards, approaches, and identifying unresolved issues (e.g. policy issues). Leverage activities of other Security and Privacy related workgroups. • In developing Security and Privacy related content, it will be important to maintain traceability on how existing and emerging HITSP constructs may be affected.

  12. Emergency Responder EHR Use Case • Under the leadership of the Office of the National Coordinator for Health Information Technology, an Emergency Responder EHR Use Case has been developed and prioritized for the attention of the Healthcare Information Technology Standards Panel (HITSP) and the other ONC initiatives. • The Use Case describes the role of an Emergency Responder Electronic Health Record, comprising at a minimum demographic, medication, allergy and problem list information, that can be used to support emergency and routine health care activities. • The Use Case will leverage the work in related activities from the HITSP Care Delivery Technical Committee and elsewhere. The HITSP process strives to involve a broad base of participants. • As we proceed into the second year of the standards harmonization process, this Use Case will be a core Work Program activity of the HITSP Care Delivery Technical Committee. From time to time the Technical Committee may assign tasks to workgroups under it’s direction.

  13. The actual harmonization process is a series of steps taken by industry stakeholders within the context of HITSP Harmonization Process Steps ReceiveRequest I Harmonization Request II RequirementsAnalysis III Identificationof CandidateStandards IV Gaps,Duplicationsand Overlaps Resolution V Standards Selection VI ConstructionofInteroperabilitySpecification VII InspectionTest VIIIInteroperabilitySpecificationReleaseandDissemination IXProgram Management BeginSupport

  14. Work Plan and Schedule Overview HITSP 2007 Timeline 10/09/07 HITSP Board 04/23/07 HITSP Board 07/09/07 HITSP Board 02/05/07 HITSP Board 09/07/07 HITSP Panel 02/12/07 HITSP Panel 03/19/07 HITSP Panel 07/16/07 HITSP Panel 10/15/07 HITSP Panel 05/11/07 HITSP Panel JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC 6/18 – 6/20 TC Face to Face San Diego CA 5/08 – 5/10 TC Face to Face Arlington VA 09/04 – 09/06 TC Face to Face Arlington VA 03/06 – 03/08 TC Face to Face Chicago IL Activity 1 – Version 2.0 of Existing EHR, CE, BIO ISs EHR, CE and BIO v 2.0 On-going Support Implementation Support and Testing (includes minor document updates) Activity 2 – Security and Privacy for All Use Cases Activity 3 – New Emergency Responder EHR Use Case S&P and EHR-ER v 1.0 04/13 – 05/16 05/17 – 06/14 Implementation Support and Testing (with annual updates as required) Public Input on S&P Public Comment Inspect Test and Public Comment Comment Resolution and Panel Approval Requirements, Design, Standards Selection IS Construct Development 02/15 – 05/16 07/20 – 08/16 08/17 – 10/15 05/17 – 07/19 Activity 4 –New Use Cases from AHIC Detail Schedule to be Established Upon Review of the Use Cases

  15. HITSP 2007 Schedule of Meetings 10/09/07 HITSP Board 04/23/07 HITSP Board 07/09/07 HITSP Board 02/05/07 HITSP Board 09/06/07 HITSP Panel 07/16/07 HITSP Panel 02/12/07 HITSP Panel 03/19/07 HITSP Panel 10/15/07 HITSP Panel 05/11/07 HITSP Panel JAN SEP FEB MAR APR MAY JUN JUL AUG OCT NOV DEC 6/18 – 6/20 TC Face to Face San Diego CA 5/08 – 5/10 TC Face to Face Arlington VA 09/04 – 09/06 TC Face to Face Arlington VA 03/06 – 03/08 TC Face to Face Chicago IL

  16. HITSP Definition of a Standard • A standard specifies a well-defined approach that supports a business process and: (1) has been agreed upon by a group of experts; (2) has been publicly vetted; (3) provides rules, guidelines, or characteristics; (4) helps to ensure that materials, products, processes, and services are fit for their intended purpose; (5) is available in an accessible format; and (6) is subject to an ongoing review and revision process.

  17. Tier 1 Standards Readiness Criteria • The standards required to support each major Use Case event were organized within an agreed upon standards taxonomy • The standards selected for inclusion in the pool were examined using ‘HITSP approved’ Tier 1 and Tier 2 Harmonization Readiness Criteria

  18. Tier 2 Standards Readiness Criteria • Suitability • The standard is named at a proper level of specificity and meets technical and business criteria of use case • Compatibility • The standard shares common context, information exchange structures, content or data elements, security and processes with other HITSP harmonized standards or adopted frameworks as appropriate • Preferred Standards Characteristics • Approved standards, widely used, readily available, technology neutral, supporting uniformity, demonstrating flexibility and international usage are preferred • Standards Development Organization and Process • Meet selected criteria including balance, transparency, developer due process, stewardship and others. • Total Costs and Ease of Implementation • Deferred to future work

  19. HITSP receives Use Cases and Harmonization Requests from external sources, such as AHIC and ONC. The Use Case or Request defines scenarios, business actors, and business and functional/interoperability requirements. HITSP decomposes the Use Case requirements into scenario(s) and then into transactions providing context: technical actors, actions and content. It may create or reuse a transaction or a grouping of transactions (transaction package) based on commonality at this level. Transactions are logical groupings of actions that are decomposed into components, which are groupings of base standards that work together, such as message and terminology. Each HITSP construct, i.e., transaction package, transaction or component, may constrain the construct or standard below it. Constraints follow a strict hierarchy and are only imposed by the next higher construct. Transaction packages, transactions and components all are potential candidates for reuse if a new set of requirements and context are successfully fulfilled by the existing construct. While reuse is a HITSP goal, it is established in the context of a Use Case and its functional/interoperability requirements. HITSP constructs are version controlled and, if reused, will be uniquely identified. HITSP FrameworkBasis for Interoperability Specification Template

  20. HITSPFramework

  21. Definitions and Rules

  22. Definitions and Rules (cont.)

  23. Document Naming Convention:[Document Type]_HITSP_[Document Number]_[Version]_[year]_[Short_Title]_[Date] Example: IS_HITSP_02_v1.2_2006_Biosurveillance_10202006.pdf Document Type: IS (Interoperability Specification) Document Number: 02 Version: 1.2 Year: 2006 Short Title: Biosurveillance Date: October 20th, 2006 Document Types: IS: Interoperability Specification ISTP: Transaction Package IST: Transaction ISC: Component Familiarization with existing HITSP Constructs  Collectively known as “Constructs”

  24. There are Three existing Interoperability Specifications: IS-01 v1.2 EHR-Lab-Result-Reporting IS-02 v1.2 Biosurveillance IS-03 v1.2 Consumer Empowerment There is also a high-level Executive Summary of the three main ISs Each IS has a number of HITSP Constructs which it calls upon to describe the implementation of lower level, specific interactions The Beginning of each IS contains a diagrammatic overview of the lower level constructs it calls upon and their relationship to the IS Familiarization with existing HITSP Constructs

  25. The ANSI Public Document Library is used for publicly posting completed works and related materials. It can be found on the “Document Library” links from the main HITSP site: www.hitsp.org HITSP Interoperability Specifications (ISs) and Executive Summary can also found at www.hitsp.org which links to them directly. The Use Cases are located in the Public Document Library under: Technical Committees / AHIC Harmonized Use Cases The Members Document Library is used for works in progress and can be found at: http://members.ansi.org/sites/ Login using: ANSI_Membership\{your ANSI assigned user ID} Password: {your ANSI assigned password} Technical Committees have standing meeting times with dedicated conference bridge lines supported by various web-based collaboration tools including: GoToMeeting: Up to 26 participants; “Meet Now” capability GoToWebinar: Up to 1001 participants; Survey, Poll and Q &A Capabilities Technical Committee Resources

  26. Standing Conference Calls all scheduled for the TCs and Work Groups as follows: For all standing meetings: Dial in: 1-877-352-0183 International : 602-462-1021 Consumer Empowerment: Every Monday 12:00pm to 1:00 pm EST Participant code: 482290 Care Delivery: Every Monday from 3:00 -5:00pm EST. Participant code: 694315 Population Health: Every Monday from 1:00 -3:00 pm EST. Participant code: 972454 Security and Privacy Work Group: 1st and 3rd Thursday of each month at 1-2pm EST Participant code: 911743 Technical Committee Resources

  27. For Technical Committee related questions please contact your TC facilitators or: Joyce Sensmeier MS, RN-BC, CPHIMS, FHIMSS Vice President, Informatics HIMSS 230 East Ohio, Suite 500 Chicago, IL 60611-3269 Phone: 312-915-9281 email: jsensmeier@himss.org Theresa Wisdom, MBA, RHIA Manager, Standards Harmonization HIMSS 230 East Ohio, Suite 500 Chicago, IL 60611-3269 Phone: 312-915-9513 email: twisdom@himss.org Jessica KantCoordinator, Standards HarmonizationHealthcare Information & Management Systems Society230 E. Ohio St., Suite 500Chicago, IL 60611Phone: 312-915-9283 Fax: 312-915-9511 email: jkant@himss.org For ANSI Document Library related questions please contact: Alison ZieglerProgram Administrator, Standards PanelsAmerican National Standards Institute25 West 43rd StreetNew York, NY 10036Phone: 212-642.4947 email: aziegler@ansi.org Troubleshooting

  28. Thank you for volunteering to participate in HITSP. We cannot succeed without you! Questions?

More Related