CEND & Population Explorer
The CRISP Event Notification Delivery (CEND) Solution is an internally operated system designed to offer real-time alerts for patients’ hospital encounters seamlessly through the Population Explorer application. CEND ensures timely troubleshooting and ongoing enhancements due to its internal nature, enhancing our ability to deliver accurate notifications. After submitting a CEND panel, users are able to view notifications for their patients through Population Explorer.
Population Explorer an easy-to-use interface for clinicians or a patient’s care team to access their patients’ latest encounters and each patient’s six-month encounter history. Upon login to the CRISP-DC Portal this tool will be seamlessly integrated in your view as a separate widget.
The reports permit users to:
- Access and Review: Users can view and export latest encounters of patients on their panel.
- Filtering Capabilities: Efficiently filter data available in an encounter based on your specific inquiries.
- Intra-Portal Navigation: Click into other information available in HIE portal directly from the widget. This includes clinical information, referrals, and prescription drug monitoring, where available.
What is CEND?
The CRISP Event Notification Delivery (CEND) solution provides users with real-time alerts about patients’ hospital encounters by matching an organization’s patient roster (or “panel”) with up-to-date encounter ADT data. These alerts are delivered directly into the organization’s workflow, seamlessly integrating with the CRISP Portal via Population Explorer.
CEND represents a complete re-imagining of traditional push alerting. Leveraging our data lake infrastructure, CEND can create alerts tailored to each participant’s specific needs. Beyond ADT-based alerts, we deliver real-time alerts for a wide range of health factors, such as A1C levels, diabetes risk, hospitalizations, and social determinants of health.
What is Population Explorer?
Population Explorer offers a user-friendly interface for clinicians and care teams to review patients’ encounters, providing access to the latest encounters and six-month encounter history. Population Explorer is integrated directly in the DC Portal.
Resources
Available Filters
Below is a table of available filters in Population Explorer and their definitions.
| FILTER NAME | FILTER DEFINITION |
|---|---|
| ACO | An Accountable Care Organization (ACO) is a network of healthcare providers that collaboratively manage and coordinate care for a specific patient population, aiming to improve outcomes and reduce costs, often through shared savings programs. |
| Admit Date/Time | The date and time which a patient was first admitted for an event. |
| Admit Source | Source of the admission from the ADT |
| Care Manager | The name of the Care Manager for a patient in any given event. |
| Care Program | A care program is a structured healthcare initiative designed to provide coordinated, comprehensive services to improve patient outcomes for specific conditions or populations. |
| Date of Birth | The day, month, and year on which the patient for a given event was born. |
| Date of Death | The day, month, and year on which the patient expired according to MD Vital Statistics |
| Death Indicator | Flag to indicate if a patient is expired |
| Diagnosis Code | The code for any of the diagnosis the patient received (ex: COVID 19 code is U07.1) |
| Diagnosis Description | The name of any of the diagnoses the patient received. |
| Discharge Date/Time | The date and time which a patient was discharged for an event. |
| Discharge Disposition | Discharge disposition in an ADT message refers to the patient’s post-discharge status or the location they are sent to, such as home, rehab, or another care facility. |
| Discharge to Location | Specific location a patient is discharged to if available |
| Encounter Date | The date which a patient encounter occurred. |
| Encounter Type | The type of encounter for a given patient event (ex: Emergency, Inpatient, Observation, Outpatient). |
| Facility | The name of the facility at which a patient event occurred. |
| Facility Type | The type of facility at which a patient event occurred (ex: hospital). |
| Follow up Status | The status set by your organization for an individual patient event |
| Group | Related to patient groups created by your organization |
| Insurance From ADT | Refers to the patient’s coverage details, including the insurer and plan information used for billing and medical services during their care. |
| Insurance Type | Refers to the category of healthcare coverage or insurance plan the patient has, such as private, Medicare, Medicaid, or self-pay. |
| Location | User defined panel field |
| MRN | MRN (Medical Record Number) in an ADT message is a unique identifier assigned to a patient within a healthcare facility’s records, used to track their medical history and treatments. |
| National Provider Identifier (NPI) | The provider associated with a patient encounter, by NPI number |
| Panel MRN | MRN (Medical Record Number) provided from the user panel. |
| Notification Type | Different types of Intelligent alerts users can select by if configured. |
| Patient Class | Indicates the patient’s status or type of care being provided, such as inpatient, outpatient, emergency, or observation. |
| Patient Complaint | The issue a patient described experiencing upon admission for an event (ex: chest pains) |
| Patient Name | The name of the patient associated with a given event. |
| Practice | User defined panel field where the patient is assigned |
| Primary Care Provider | PCP input by the panel or filled in by CRISP data |
| Primary Diagnosis Code | Identifies the main medical condition or reason for the patient’s treatment, represented by a standardized code such as ICD-10 (ex: COVID 19 code is U07.1). |
| Provider | Refers to the healthcare professional or organization responsible for delivering care to the patient, including physicians, nurses, or clinics. |
| Risk Methodology | User defined Risk Methodology submitted on the panel. |
| Risk Methodology 2 | User defined Risk Methodology submitted on the panel. |
| Risk Score 1 | User defined Risk score submitted on the panel. |
| Risk Score 2 | User defined Risk score submitted on the panel. |