1 / 11

CRISP Update

CRISP is a non-profit Health Information Exchange serving Maryland and the District of Columbia. We enable the healthcare community to securely share data to facilitate care, improve outcomes, and reduce costs.

stovar
Download Presentation

CRISP Update

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. CRISP Update January 2017

  2. Vision – Mission – Guiding Principles CRISP is a non-profit health information exchange, or HIE, serving Maryland and the District of Columbia. • Our Vision • To advance health and wellness by deploying health information technology solutions adopted through cooperation and collaboration. • Our Mission • We will enable and support the healthcare community of Maryland and our region to appropriately and securely share data in order to facilitate care, reduce costs, and improve health outcomes. Our Guiding Principles Begin with a manageable scope and remain incremental. Create opportunities to cooperate even while participating healthcare organizations still compete in other ways. Affirm that competition and market-mechanisms spur innovation and improvement. Promote and enable consumers’ control over their own health information. Use best practices and standards. Serve our region’s entire healthcare community.

  3. 1 2 3

  4. CRISP Key Performance Indicators

  5. 1 2 3

  6. Work plan with Maryland Hospitals Care Coordination Infrastructure Goals Care Coordination Workgroup Recommendations FY17 Update Factor Requirements Each hospital will be able to: Flag Patient Relationships 1. Share Care Planning Data 2. Health Risk Assessment Use of In-Context Alerts 3. Use of CRISP Reports 4. Now called a “Patient Care Overview”

  7. FY17: Focus on Care Coordination • CRISP will support Maryland hospitals this year, with an aim of helping them all do these four things, to collectively improve care coordination: • Flag Patient Care Management Relationships: Notify CRISP for each patient who is enrolled/dis-enrolled in a care management program, including contact information for the patient, care coordinator, and primary care provider. • Share Care Planning Data: Whenever care management information appropriate for sharing is created or updated for a participating patient, send a copy of the information to CRISP. • Use In-Context Alerts: Create an “alert mechanism” in your hospital EHR so your clinicians know when a person who is in care management has shown up, with easy access to the full data. • Use CRISP Reports: Incorporate CRISP reports and compiled data into the work of the population health team. (For patient identification and performance measurement.) • This approach should align with broader interventions and programs in place to support the high need / complex patients

  8. What is a Care Alert? A rapid, brief communication tool for colleagues encountering our most vulnerable patients, intended to enhance patient safety and save time. • Primary audience is clinicians, especially in acute settings • High value, action-oriented “need to know” information • May be free text or an element of structured data • Informs decision of whether to admit, and how to treat, patient • Intended to be presented within workflow, in context of the patient’s chart • May offer click-through to longitudinal care plan and/or other rich information within CRISP

  9. In-Context Integration • Cerner hospitals in Maryland and DC have implemented API calls from Mpages. • These API calls can query a range of different data types from CRISP to meet specific workflows.

  10. Data Router and Non-Hospital Connectivity • Key Functions include: • Consent management • Data normalization • Data routing • Patient-provider relationships determination and management Data Router - A service designed to move encounter data and clinical records from ambulatory practices to the care management systems which can ingest them and use them for care coordination

  11. Contact • David Horrocks • Office: 443-285-0161 • david.horrocks@crisphealth.org

More Related