Company Overview - University of California, Berkeley · Introducing Cal INDEX • California Integrated Data Exchange • Announced August 5, 2014 • Nonprofit, mutual benefit corporation

Company Overview

Company Overview | 01.14.2015 | ©2015 Cal INDEX. CONFIDENTIAL & PROPRIETARY 1

Introducing Cal INDEX

•  California Integrated Data Exchange •  Announced August 5, 2014 •  Nonprofit, mutual benefit corporation •  Next generation HIE (4.0)

•  Mission •  Statewide HIE •  Longitudinal Patient Record (LPR) •  Medical research (future)

•  Goals •  Trusted, secure source of health data •  Improve patient care and safety •  Complete the “System of Care”


Completing the System of Care

Providers

Payers

Consumers

•  Data as a Service (DaaS) –  Acquire, curate and manage data

into a common data model (LPR) –  Manage the hard stuff:

integration, access, attribution, logging

–  Access: portal, API, download

•  Converged payer and provider data increases value

•  Supports emerging care and risk models

•  Future – Complimentary data sources will drive incremental value (e.g., registries)


Does California and Federal privacy laws such as HIPAA and CMIA prevent me from contributing or sharing data with Cal INDEX without patient consent?

A.  True B.  False

Company Overview| 01.16.15 | ©2015 Cal INDEX. CONFIDENTIAL & PROPRIETARY 4

Cal INDEX Services

•  Health Information Exchange (HIE) –  Ingest, curate, manage patient data

•  Longitudinal Patient Record (LPR) –  Repository model

•  Payer and provider data –  Rich combined data –  Standard data model

•  Data access –  Direct access via clinical portal –  System access via secure APIs –  Bulk [download] data access

•  Privacy and Security –  Notice of Privacy Practices –  Role based security –  Data attribution –  Logging and audits –  Opt out model


Cal INDEX AWS VPC

OPT-‐OUT/BackIN JSP/JBOSS/Hibernate/Spring/MySQL

ORION AWS VPC

ORION HIE

NextGate EMPI

CareCom Terminology

CDR/Data PlaJorm

ETL Service API

Server

Clinical Portal Server

IntegraLon Server

HIE/LPR

ETL UI

ParLcipant Portal

ParLcipant Downloads

ParLcipant REST API

PaLent Opt Out/In

ParLcipants

Cal INDEX Development Timeline

•  1H2015 –  Complete initial deployment of company and

platform –  Begin payer and provider implementations –  Establish product and privacy workgroups

•  2H2015 –  Grow payer and provider participation –  Deliver additional product features –  Define consumer access model

•  2016 –  Initiate consumer access –  Expand data sets available via LPR –  Continue evolving product features/value


Use case: Stroke (EMS) •  Jane Doe, 72, female, at lunch with friends when she loses consciousness. 9-1-1 is

called and EMS responders arrive; the friends are able to provide little information to the paramedics and patient has regained consciousness. BP is slightly elevated 165/100 and though conscious, patient is confused and has slurred speech

•  EMS provider is a Cal INDEX participant. Once patient identity is established, they can view data from the LPR to help assess the patient

•  Paramedics find the following in the LPR: –  Patient history of hypertension being controlled by medication –  6 months prior patient had ER visit with diagnosis of TIA –  Patient does not have any history of seizures, diabetes or documented recent trauma

•  Using the LPR in conjunction with a physical assessment, they make the decision to by-pass Hospital #1 (nearest) and transport patient to Hospital #2 (a stroke center of excellence)


Use case: Stroke (ED) •  [continued from the EMS slide] Paramedics notify Hospital #2 and their Rapid

Response Team is alerted

•  Patient has never been to Hospital #2 but because they are a Cal Index participant, the response team is able to review the LPR and ascertain the following:

–  Emergency Contact Information: Husband; mobile phone –  Patient had prior ER visit with diagnosis of TIA; LPR does not show subsequent episodes.

–  Indication of medication per Rx history (both prescribed and filled) •  Patient is not on Coumadin/blood thinners

–  No Hx of Diabetes –  No history of aneurysm –  Normal A1C and platelet count from PCP visits 2 months prior –  No surgery or any noted accident or trauma within the last three months

•  Outcome: –  Response Team orders prompt laboratory and CT imaging –  Stroke diagnosis is confirmed and receiving informed consent from husband, tPA is

administered within 2 hours of initial onset –  Jane Doe suffers minimal permanent impairment


Use case: Diabetes (PCP) •  Jack Doe is a newly diagnosed 42 year old, type 2 diabetic, with cholesterol elevated at

280 and high triglyceride level

•  Dr. Smith has prescribed an oral hypoglycemic to control his blood sugar along with a statin for the cholesterol; patient receives his initial 30 day supply

•  Patient returns to the office after 83 days for a follow up appointment (having canceled two). His A1c remains elevated < 9.0 and his cholesterol is still at 280; patient states he has been compliant with the treatment protocol

•  Dr. Smith considers changing medications but before he does, reviews the LPR which includes Rx history (provided by the participating health plans). Reviewing the refill history, Dr. Smith ascertains that Jack has only refilled his prescriptions once since the initial visit (vs twice if he were adherent)

•  This information (not available via EMR alone) allows Dr. Smith to understand that Jack’s continued elevated A1c and cholesterol level might be related to a medication adherence issue – that he can now discuss with the patient


Contact

@calindex www.calindex.org

[email protected]


David Watson – CEO [email protected]

Documents

Company Overview - University of California, Berkeley · Introducing Cal INDEX • California Integrated Data Exchange • Announced August 5, 2014 • Nonprofit, mutual benefit corporation