1 / 11

Cautionary Language Concerning Forward-Looking Statements

Safe Harbor Statement. Cautionary Language Concerning Forward-Looking Statements

ling
Download Presentation

Cautionary Language Concerning Forward-Looking Statements

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. Safe Harbor Statement • Cautionary Language Concerning Forward-Looking Statements • This presentation contains descriptions of products, services, features and functionalities that AT&T envisions for the future.  AT&T reserves the right to modify, delay or withdraw  any such product, service, feature or functionality.    This document is not an offer, commitment, representation or warranty by AT&T and is subject to change. Last Updated: 5/12/10

  2. Agenda - AT&T in Healthcare - Connecting the Healthcare Ecosystem - Core Components of HIE - What’s Important? - Considerations

  3. Healthcare is Important to AT&T

  4. National Healthcare “Ecosystem” In Need of an Overhaul Patients/Consumers/MDs @ Home Community Clinics/Physician Offices Hospitals/Health Systems Urgent Care Centers Healthcare institutions operate largely as “islands” with separate systems and processes VendorSuppliers Long Term Care Facilities Pharmaceuticals State/Federal Agencies & Payors

  5. AT&T Healthcare Community Online (HCO)

  6. Core Components of HIE • Record Locator Service (RLS)(MPI) • A “centralized” service that manages the location of various episodes of care for quick retrieval and access to a single patient medical record across many sources. • Master Patient (Person) Index (MPI) • Establish a “centralized” MPI for participants (providers, payers, etc.) to support broad-based data exchange and quality reporting, ensuring a patient is identified only once across the HIE initiative. • Data Exchange Services • A “centralized” engine to allow messaging of data to the system of choice for the participants across the HIE initiative. This will expedite data routing and transformation between all legacy systems and external sources/end-points. • Portal Services • A collaborative framework for displaying aggregated information in a “centralized” patient-centric dashboard, as well as accessing applications across HIE initiatives. • Identity Services • Establishes the privacy and consent management process that satisfies the requirements and needs of a HIE initiative, while having a “centralized” approach to managing digital identities of users across the initiative. • AppCloud® • An “application marketplace” of 3rd party clinical and administrative applications and services integrated to the “HCO Platform” for delivery to healthcare communities and initiatives.

  7. Collaboration, Aggregation

  8. 2 Hospital Hospital Patient Patient Practitioner Practitioner Hospital Patient Practitioner Data Center Data Center LAN/WAN/WLAN Hardware Radiology EMR EMR Software Software “B” Laboratory Laboratory Laboratory Pharmacy Pharmacy Pharmacy Radiology Radiology Radiology Data Center Pharmacy LAN/WAN/WLAN Hospital Hospital Patient Practitioner Patient Practitioner EMR Software “A” Data Center Data Center Hardware LAN/WAN/WLAN Laboratory EMR EMR Software “C” Software Laboratory Laboratory Laboratory Pharmacy Pharmacy Pharmacy Radiology Radiology Radiology The HIE SystemIntegrates internal and external data sources and legacy applications HCO Portal AT&T Network Government Data Labs

  9. What’s Important to a Physician User? 9

  10. HIE Considerations • HIE Technology is easy. • Acheiving agreement and trust is the challenge. • Reasons organizations may not want to share data: • How do I Know that the HIE meets HIPAA requirements? • Am I opening myself up to liability? • How do I know that the HIE will honor my data-sharing agreements? • Am I giving someone else a competitive advantage? • What else is my data being used for? • What about legal discovery and non-repudiation of data? Security and privacy, when implemented properly, provide a framework for trust.

  11. Interoperability and management of patient records Retrieval of clinical data across continuum of care Broader data exchange and access to applications Comprehensive view of patient information Clinical and administrative process automation Connect. Share. Collaborate.

More Related