|
1
|
|
|
2
|
|
|
3
|
|
|
4
|
|
|
5
|
|
|
6
|
- Grants
- Cleveland Clinic
- Community Health Information Collaborative
- HealthBridge
- HealthLINC (Bloomington Hospital)
- HealthLink RHIO (Wright State University)
- Kaiser Permanente
- Initial Contracts
- Carespark
- Delaware HIN
- Indiana University
- Long Beach Network for Health
- Lovelace Clinic Foundation
- MedVirginia
- NCHICA
- New York eHealth Collaborative
- West Virginia HIN
|
|
7
|
|
|
8
|
|
|
9
|
|
|
10
|
- Collaboration you can be proud of!
|
|
11
|
- CONNECT is an FHA initiative that enables Federal agencies to
participate in the Nationwide Health Information Network by:
- Participating in decisions about the NHIN
- Connecting their existing electronic health information systems to the
NHIN, in order to exchange data with Federal and non-Federal partners
- Implementing “accepted interoperability standards” of the Secretary,
Health and Human Services in their operational health information
exchanges
- Utilizing operational NHIN core services to meet OMB HI Scorecard
reporting requirements
- CONNECT provides a Federal NHIN Gateway software product to connect
agencies to the NHIN
- Built using SOA on an industry standard Java platform
- Configurable to support the needs of any agency
|
|
12
|
- FHA’s CONNECT Initiative provides three related tools to enable
organizations to connect to the NHIN:
- The Gateway, which implements the core services defined by the NHIN
- Enterprise Service Components, which provide robust tools for indexing
patient identities, maintaining patient health documents, implementing
business rules for authorizing the release of medical information and
more
- The Software Development Kit (SDK), which enables developers to
customize the Gateway and add or replace enterprise service components
|
|
13
|
- CONNECT Gateway early access release to Federal Partners – June 2008
- CONNECT Successfully Passed NHIN Test Event – August 2008
- CONNECT Gateway Release 1 – September 2008
- Implementation of seven service interfaces specified via the NHIN Trial
Implementations Cooperative Technical and Security Work Group consensus
process. These services include
Subject Discovery, Document Query, Document Retrieve, Audit Log Query,
Consumer Preferences Profile,
Authorization Framework and Messaging Platform.
- AHIC – NHIN Demonstration – September 2008
- SSA, DOD, VA
- Demonstrated implementation of two use cases: Wounded Warrior
Continuity of Care, and Medical Evidence for Disability Benefits
- CONNECT Successfully Passed NHIN Test Event – November 2008
- NHIN Public Forum Demonstrations December 2008
- SSA, DOD, VA, IHS, NCI, CDC
- Demonstrated implementation of the original seven along with two
additional service interfaces.
These services are Health Information Event Monitoring and NHIE
Service Registry.
|
|
14
|
- Adoption
- Move from testing into production usage by agencies
- Expand the set of agencies utilizing the NHIN from 6 to 14
- Work with industry to ensure that the Gateway code is available for use
and enhancement by vendors, open source communities and others
- Host a CONNECT User Conference to share technical knowledge and
facilitate enhancements to the code base
- Development
- Implement new NHIN services that will be defined
- Enhance the Gateway with enterprise-class components that includes
robust components for master patient indexing, document registries and
repositories, policy engine for authorizing release of medical
information and more
- Create tools and reference implementations that can be used by all NHIN
participants for testing purposes
- Operations and Maintenance
- Provide support services to the growing list of Federal agencies that
want to deploy the Gateway and integrate it with their existing
electronic health information systems
- Includes support at tier 1 (knowledgebase and initial phone
consultation) and tiers 2/3 (escalation with expert technical
assistance)
|
|
15
|
- Open Source: Federal agencies were committed to a platform that was open
and readily modifiable
- Extensibility: The Gateway needed to support both current and future
evolutions of the NHIN, and enable agencies to add functionality to
address their unique missions and support their unique electronic health
information systems
- Portability: The Gateway must be deployable using a wide variety of
operating system and database platforms
- Reliability: Agencies needed a
solution that could perform high-volume, mission-critical information
processing
- Substitutability: The Gateway needs to provide robust, enterprise-class
components while enabling agencies to replace them with their own
implementations if necessary
|
|
16
|
- Create an adapter architecture that enabled agencies and others to
connect their existing HI systems to the Gateway
- Embrace Web Services internally as well as externally to provide maximum
flexibility and extensibility, using an enterprise service bus (OpenESB)
- Utilize Java as the underlying platform to provide cross-platform
portability
- Adopt existing solutions where possible for critical enterprise service
components, such as a master patient index and authorization policy
engine
|
|
17
|
|
|
18
|
- The Gateway is organized into a common core services, and an
agency-specific adapter
- Components can be modified or replaced as needed to address
agency-specific requirements
- FHA provides a Software Development Kit (SDK) for adapter development
- Availability: March 2009
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
- FSS Objective
- To analyze and develop practical guidance and a strategic roadmap that
enables the adoption of secure, scalable health information exchanges
among the
Federal Government and private sector healthcare organizations.
|
|
23
|
|
|
24
|
- Current activities include:
- Use case analysis
- Conducting gap analysis
- Aligning with other security efforts
- February 2009: FISMA applicability guidance for HIE
- February 2009: Inviting private sector participation
- April 2009: Federal Security Strategy Roadmap
|
|
25
|
- Consequences (including higher costs) when security & privacy
standards are not implemented in a consistent manner:
- To Providers
- To Patients
- To Industry
- To Payers
- The FSS is creating a security roadmap that defines how the Federal
Government will securely conduct Health Information Exchanges
|
|
26
|
|
|
27
|
|
|
28
|
|
|
29
|
- FHISE will provide:
- A starting point for agencies beginning to implement health IT solutions
- A valuable resource for agencies mid implementation if they encounter
questions or challenges
- A resource for agencies as they ensure their solutions comply with
federal regulations
|
|
30
|
|
|
31
|
|
|
32
|
- Examples of business questions which can be answered through information
queries/reporting include:
- Business and Interoperability
Questions:
- How well does my initiative align with the National Health IT agenda?
- What other agencies’ initiatives carry out similar business functions
as my initiative?
- What IERs are available for reuse in my applications?
- Which technical or business actors appear across ISs?
- Investment Questions:
- What health info sharing investments in other agencies have similar
goals to mine?
- What are the info exchange systems supported by those investments?
- Can I reuse those information exchanges for my initiative?
- Service Questions:
- Which NHIN Core Services support my information exchange requirements?
- Who else is using those core services?
|
|
33
|
- 80 % Complete, 20% by end of January
- National Information Products
- ONC Strategic Plan
- NHIN Core Services
- HI Survey
- Interoperability Specifications 01-07
- CCHIT (Inpatient, Ambulatory EHR)
- Business Priorities
- Continuity of Care (Wounded Warrior)
- Application for Disability Benefits (Int Dis Model)
- Biosurveillance (PAHPA/HSPD-21)
- Long Term Care Transfer Across Settings (CARE)
|
|
34
|
- Community-based: FHA community inputs/maintains content
- Driven by health community and NHIN priorities
- Added NIPs, BPAs, NHIN Core Services to meet needs of new partners or
new government requirements
- ‘Best fit’ technology solution driven by requirements
- Intuitive user interface
- Broad selection of available queries designed to meet needs of each
stakeholder group
|
|
35
|
|
|
36
|
|
|
37
|
|
Notes
