State of New Hampshire. Phase 3 Converging on Solutions discussion deck Business and Technical Operations Workgroup. July 20, 2010

Transcription

1 State of New Hampshire Health Information Exchange Planning and Implementation Project Phase 3 Converging on Solutions discussion deck Business and Technical Operations Workgroup July 20, 2010

2 Agenda Opening remarks, review of work to date, review of initial consensus areas Converging on Solutions Generating content for the strategic and operational plans Wrap up and next steps Appendix 2

3 HIEPI - MAeHC Project Schedule Segment 1 Timeline: June 1 October 31 Activity/Milestone Launch project, establish teams, determine roles and responsibilities, convene stakeholder kickoff meeting Create strawman plan and disseminate preparation packets Conduct environmental scan Week Jun Jul Aug Sep Summit 1 and follow up: Opening doors and exploring ideas Summit 2 and follow up: Considering alternatives and narrowing options Summit 3 and follow up: Converging on solutions Plan review, vetting, and finalization First draft of Plan Plan due to ONC Plan submission to ONC Respond to ONC questions - ONC approval anticipated We Are Here 3

4 Review Building blocks Increasing cost Increasing complexity Increasing value potential Shared services Community record Secure routing to public health and patients Secure routing among providers Does require some type of centralized storage of data Does not require central storage of clinical data July 20, 2010 NH HIEPI Steering Committee Meeting v0.1 4

5 Review - Strawman phasing Is the transaction legal under current NH law? Are the technology, business, or legal complexities manageable given a short lead time? Can it be developed and launched within the ONC HIE funding budget? Is there an immediate market need for the transaction? Is there a lack of a clear substitute in the market today? No If it s illegal today, do we expect that it could be made legal in 2011 (e.g., is the transaction otherwise required in the market or by law, e.g., public health)? Is there expected to be an important market need for the transaction? Can technology, business, or legal complexities be resolved in parallel with Phase 1 implementations? Is there a continued lack of a clear substitute in the market today? No Yes Yes Phase 1 Phase 2 If it s illegal today, do we expect that it could be made legal in 2011 or beyond? Is there expected to be an important market need for the transaction? Can technology, business, or legal complexities be resolved in parallel with Phase 1 and 2 implementations? Is there a continued lack of a clear substitute in the market today? Yes Phase 3

6 Review - Strawman phasing (pending further input and environmental scan data) Phase 1 A push network that allows secure, standardized, low-cost sending and receiving of clinical documents among providers for treatment purposes - Across hospital networks (discharge summaries, labs, etc) - Manual record location across provider organizations - Within hospital networks for those hospitals who opt for it - Outside of hospital networks for offices and clinics who are not part of hospital networks today A standing, multi-stakeholder governance process to guide decision-making going forward A development program to build Phase 2 capabilities Phase 2 Extend push network to include public health and other healthcare entities (e.g., long-term care, etc) A pull network to allow electronic queries of CCD-standardized patient information through a Record Locator Service Development program to build Phase 3 capabilities Business development to build shared services capabilities Phase 3 Extend push network to include patients, other entities Extend pull network to allow centrally orchestrated merging of records across clinical entities Advanced shared services capabilities

7 Review - Use case prioritization HIE Building Block What From whom To whom Legality Difficulty Demand for service Current market availability Secure routing to providers Consult note -- Summary of care record Specialist PCP Secure routing to providers Hospital admission notification Hospital Referring physician and/or PCP Secure routing to providers Hospital admission notification Hospital Referring Hospital Secure routing to providers Hospital discharge summary Hospital Referring physician and/or PCP Secure routing to providers Hospital discharge summary Hospital Hospital Secure routing to providers Hospital ED visit summary Hospital Referring physician and/or PCP Secure routing to providers Imaging reports Hospital PCP or specialist Secure routing to providers Key clinical information summary Hospital Hospital Secure routing to providers Key clinical information summary PCP or specialist Hospital Secure routing to providers Lab results Hospital PCP or specialist Secure routing to providers Referral -- Summary of care record PCP Specialist Secure routing to providers Referral -- Summary of care record PCP or specialist Hospital Secure routing to providers Request for key clinical information Hospital Hospital Secure routing to providers Request for key clinical information Hospital PCP or specialist Phasing HIE Building Block What From whom To whom Legality Difficulty Demand for service Current market availability Secure routing to providers Hospital discharge summary Hospital Other care settings Secure routing to providers Lab order PCP or specialist Hospital Secure routing to providers Lab results Public health lab Hospital Secure routing to providers Lab results Public health lab PCP or specialist Expanded secure routing Immunization record Hospital Public health Expanded secure routing Immunization record PCP or specialist Public health Expanded secure routing Laboratory ordering decision support Payers PCP or specialist and hospitals Expanded secure routing Reportable lab results Hospital Public health Expanded secure routing Syndromic surveillance data Hospital Public health Expanded secure routing Syndromic surveillance data PCP or specialist Public health Expanded secure routing Reportable conditions PCP or specialist Public health Expanded secure routing Reportable conditions Hospital Public health Community record Community record Multiple sources Hospital Community record Community record Multiple sources PCP or specialist Community record Medication history Other clinical sources Hospital Community record Medication history Other clinical sources PCP or specialist Phasing 7

8 Review - Use case prioritization (continued) HIE Building Block What From whom To whom Legality Difficulty Demand for service Current market availability Secure routing to providers erx PCP or specialist Pharmacy Secure routing to providers Images Hospital PCP or specialist Secure routing to providers Images Imaging center PCP or specialist Secure routing to providers Imaging order PCP or specialist Imaging center Secure routing to providers Imaging reports Imaging center PCP or specialist Secure routing to providers Lab order PCP or specialist National lab Secure routing to providers Lab results National lab PCP or specialist Secure routing to providers Medication history Pharmacy Hospital Secure routing to providers Medication history Pharmacy PCP or specialist Expanded secure routing Claims submission & eligibility checking Hospital Health plan Expanded secure routing Claims submission & eligibility checking PCP or specialist Health plan Expanded secure routing Discharge instructions Hospital Patient Expanded secure routing General medical summary PCP or specialist Patient Expanded secure routing Post-visit summary PCP or specialist Patient Expanded secure routing Public health alerts Public health Hospital Expanded secure routing Public health alerts Public health PCP or specialist Expanded secure routing Quality measures Hospital CMS and/or NH Medicaid Expanded secure routing Quality measures PCP or specialist CMS and/or NH Medicaid Expanded secure routing Radiation exposure report Hospital Radiation exposure registry Expanded secure routing Radiation exposure report Imaging center Radiation exposure registry Community record Public health case investigation Hospital Public health Community record Public health case investigation PCP or specialist Public health Phasing 8

9 Initial consensus areas from each workgroup Governance Workgroup Consensus Areas Considering Public Instrumentality as organizational form modeled after NH Healthy Kids (independent 501(c)3 with explicit link to State government) Inclusive stakeholder governance body to undertake governance functions of policy setting, financial oversight and control, and operational oversight Equal governance representation (as opposed to differential representation based on financial contribution) Representation by stakeholder group (as opposed to individual) Finance Workgroup Consensus Areas Federal grant to be treated as one-time startup investment with no expectation for ongoing operational revenue Project to proceed incrementally, seeking to generate value at each step Entity to be treated as a going concern with a diverse Federal match and ongoing revenue model that includes state funding and membership contributions from all stakeholders 9

10 Initial consensus areas from each workgroup (continued) Business and Technical Operations Workgroup Consensus Areas Identified and vetted use cases that describe health information transactions (including stakeholders involved and information exchanged) Mapped use cases to building blocks to facilitate discussions and decisions of all other workgroups Prioritized use cases based on legality, Legality, Difficulty (Technical, Business/Governance, Legal complexity), Demand (Stakeholder interest; federal/state requirements), and Current market availability Began initial discussions regarding operations of HIE Legal and Policy Workgroup Consensus Areas Currently defining Consent, Audit, Authorization, Authentication, Access, and Contracts considerations for phase 1 health information transactions (transactions that are within current NH State and Federal law) Identifying areas where the HIE could improve privacy and security of health information exchange over current practice Identifying areas where public health reporting is both required by NH law and prohibited from the HIE 10

11 Initial consensus areas from each workgroup (continued) Public Health Workgroup Consensus Areas Recognition that exchange of public health information using the HIE is currently prohibited by NH State law Identification of information that could be gathered via the HIE in the future that is of high value to public health including elements required by the ONC (Immunization information, Biosurveillance, Reportable Conditions) Consensus on approach that provides minimal exposure of personal health information (PHI) (For example, public health may receive the number of H1N1 diagnoses for a given region and may go through an exception process to identify the provider and patient for follow-up action) Identifying areas where the HIE could improve privacy and security of public health information reporting over current practice as well as efficiency and cost of information gathering 11

12 Initial consensus areas from each workgroup (continued) Technical Infrastructure Workgroup Consensus Areas Incremental approach Begin with legal transactions that are feasible and affordable and that can help NH s eligible providers and hospitals achieve meaningful use Build upon foundation as allowed by NH law and in line with financial model Initial consensus areas for phase 1 foundation to be confirmed this week Hospital and other healthcare systems as brokers for transactions Statewide HIE Narrowly Facilitates Exchange (Lean infrastructure) Use NHIN Direct as Protocol for Central Exchange Allow local and global addressing of endpoints Protected Health Information not exposed to central HIE Trust relationships are brokered by HIE and/or local networks Transport Layer Security is used as a baseline of transaction encryption - other encryption can be layered on Transactions are unsolicited and unidirectional No Consent Representation required for transaction (consent management responsibility federated to brokers and not enforced by HIE) Acknowledgement of successful transactions sent to initiator Local transactions happen according to local architectural and policy frameworks 12

13 Emerging approach is to create Hub of Hubs tying together existing institutions (emerging Phase 1 consensus) Phase 1 NHIN Hospital Hospital Large practices Security NH Statewide Network Backbone Node addressing Hospital Provider addressing Audit Other provider aggregators? Secure routing across hubs Secure routing within hubs where not currently available Secure routing with entities outside of hospital hubs Secure routing with NHIN 13

14 Emerging approach is to create Hub of Hubs tying together existing institutions (Phase 2 strawman still to be vetted with WGs) Phase 2 NHIN Hospital Hospital Public health Security EMPI Large practices NH Statewide Network Backbone Node addressing Record Locator Service Hospital Provider addressing Other providers Audit Other provider aggregators? Secure routing across hubs Secure routing within hubs where not currently available Secure routing with entities outside of hospital hubs Secure routing with NHIN Secure routing to public health Secure routing to other clinical entities Record locator service for patient information queries SNFs VNA Long-term care 14

15 Emerging approach is to create Hub of Hubs tying together existing institutions (Phase 3 strawman still to be vetted with WGs) Phase 3 NHIN Security EMPI Large practices Hospital Hospital NH Statewide Network Backbone Node addressing Record Locator Service Hospital Provider addressing Data aggregation services Other providers Audit Other valueadded services Public health Other provider aggregators? Secure routing across hubs Secure routing within hubs where not currently available Secure routing with entities outside of hospital hubs Secure routing with NHIN Secure routing to public health Secure routing to other clinical entities Record locator service for patient information queries Centrally orchestrated merging of records across clinical entities Quality registries Other... SNFs VNA Long-term care 15

16 Agenda Opening remarks, review of work to date, review of initial consensus areas Converging on Solutions Generating content for the strategic and operational plans Wrap up and next steps Appendix 16

17 Converging on Solutions Address all elements of strawman strategic and operational plans for which workgroup is responsible Create bulleted statements for each key part of the plans Try to come to workgroup consensus on all key decisions note where consensus is not reached and a plan forward July 20, 2010 NH HIEPI Steering Committee Meeting v0.1 17

18 SP-8.4 HIE Business and Technical Operations Topic Guidance from ONC Implementation To address how the state plans will develop HIE capacity, the Strategic Plan must include a strategy that specifies how the state intends to meet meaningful use HIE requirements established by the Secretary, leverage existing state and regional HIE capacity and leverage statewide shared services and directories. The implementation strategy described in the Strategic Plan shall describe the incremental approach for HIE services to reach all geographies and providers across the state. The implementation strategy shall identify if and when the state HIE infrastructure will participate in the NHIN. Additional Guidance What capabilities will be needed to manage the projected business and infrastructure of the organization? For Phase 1? For Phase 2? For Phase 3?

19 OP-3.4 HIE Business and Technical Summary Topic Guidance from ONC Current HIE Capacities The Operational Plan must describe how the state will leverage current HIE capacities, if applicable, such as current operational health information organizations (HIOs), including those providing services to areas in multiple states. State-Level Shared Services and Repositories The Operational Plan must address whether the state will leverage state-level shared services and repositories including how HIOs and other data exchange mechanisms can leverage existing services and data repositories, both public or private. Shared services for states to consider include (but are not limited to): Security Service, Patient Locator Service, Data/Document Locator Service, and Terminology Service. These technical services may be developed over time and according to standards and certification criteria adopted by HHS in effort to develop capacity for nationwide HIE. Standard operating procedures for HIE (encouraged but not required) The Operational Plan should include an explanation of how standard operating procedures and processes for HIE services will be developed and implemented.

20 Phase 1 Operational Requirements Program/project management Organizational certification/compliance monitoring Rollout planning/management Coordination with other programs Vendor procurement strategies/vendor management (if needed) Certificate authority and management Micro data center operations: Directories Maintenance and upgrade planning and management 20

21 Additional Phase 2 & 3 Operations Requirements Phase 2 Limited MPI/RLS Rollout and Maintenance Patient Authentication Phase 3 Full MPI/RLS Rollout and Maintenance Clinical Viewer Infrastructure Provider Authentication Clinical Repository Infrastructure For orchestration, aggregation 21

22 Agenda Opening remarks, review of work to date, review of initial consensus areas Converging on Solutions Generating content for the strategic and operational plans Wrap up and next steps Appendix 22

23 Looking ahead to the review and finalization of the plan Segment 1 Timeline: June 1 October 31 Activity/Deadline Week August MAeHC to review draft plan for compliance and prepare plan for release to Stakeholders and Steering committee Stakeholders, Core Team, and Steering committee members to review draft plan and submit comments via comment tracking spreadsheet MAeHC to aggregate comments, assign comment ownership to Core Team and Workgroups, and disseminate Workgroups to review all comments, determine action, and recommend revisions MAeHC team to incorporate recommended revisions SOP Version 1 Comments due back by Aug 12 SOP Version 2 Steering Committee and Core team to gain necessary approvals on final plan As necessary, final revisions will be made to plan Final State-approved plan to be submitted to ONC SOP Version 3 23

24 Comment tracking spreadsheet E.g., Recommend that we consider E.g., Core Team E.g., Accept revision E.g., Revision incorporated 24

25 Wrap up and next steps Next Summit: #3 Converging on Solutions July 26, 9:00-1:00 Brown 232 Feedback review session to be scheduled for between Aug 16 and 18 Meeting summary to be distributed to all workgroups 25

26 Agenda Opening remarks, review of work to date, review of initial consensus areas Converging on Solutions Generating content for the strategic and operational plans Wrap up and next steps Appendix 26

27 SP-2 HIE Development and Adoption Summary Topic Guidance from ONC The Strategic plan must address vision, goals, objectives and strategies associated with HIE capacity development and use among all health care providers in the state, to include meeting HIE meaningful use criteria to be established by the Secretary through the rulemaking process. The Strategic Plan must also address continuous improvement in realizing appropriate and secure HIE across health care providers for care coordination and improvements to quality and efficiency of health care. Strategic Plans should also address HIE between health care providers, public health, and those offering services for patient engagement and data access.

28 SP-3 HIT Adoption Summary Topic Guidance from ONC Although it is beyond the scope of this program to fund HIT adoption initiatives described in a State Strategic Plan, it does not preclude other HITECH ACT programs or state funded initiatives to advance HIT adoption in a state. While many states have already addressed HIT adoption in their existing Health IT State Plans, it is not a requirement. However, the inclusion of Health IT adoption in the Strategic Plan is valuable and provides for a more comprehensive approach for planning how to achieve connectivity across the state.

29 SP-7 Coordination with Public Health Programs Topic Guidance from NH DHHS The Coordination with Public Health Programs Summary must include a summary of how appropriately-protected, de-identified Data derived from an HIE can improve the practice of New Hampshire's public health programs, including: Chronic/Communicable Disease and Injury Surveillance and Control Health Statistics and Data management Disease/Injury Prevention The NH PHIN Initiative, and The public health programs listed under SP-5 above, namely: the HIV Care Grant Program, the MCH State Systems Development Initiative, State Office of Rural Health Policy, and the NH Primary Care Agency. This summary must include how EMR Data can flow from an HIE to the State s public health agencies in full compliance with privacy laws and with PHIN standards for the secure transport of health Data across the Internet. More generally, SP - 7 must describe how the interests of public health agencies can be incorporated into the meaningful use of EMR by the State s health care providers.

30 OP-3.4 HIE Business and Technical Summary (continued) Additional Guidance How should the Phase 1 business be launched and managed? Prior to launch of separate public instrumentality organization (assuming that this can be created by the legislature in July 2011)? After launch of the public instrumentality? With special consideration given to seamless transition of the business and any infrastructure from State operational management and ownership to the new public instrumentality