1. No category

MiHIN Use Case Definitions
Use Case Name
Submit/Receive Statewide ADT
Notifications
Submit Active Care Relationships
(ACR)
Submit Provider Information to
Statewide Directory
Request Basic Provider Information
from Statewide Directory
Definition
In the Statewide ADT Notification Service, a patient is admitted to a
hospital. The hospital sends an ADT ‘Admit’ message to HIN. HIN checks
the Active Care Relationship ServiceSM (ACRS) which contains
information on what providers are associated with this patient. HIN
checks the Health Provider Directory (HPD) to obtain the delivery
preference for each of those providers (i.e. a secure Direct email, an ADT
message via HL7, etc.). HIN notifies the providers, based on their
delivery preferences, that the patient has been admitted to the hospital.
Other scenarios include when a patient is discharged from the hospital
or is transferred to a different location (unit, bed) within the hospital or
to another facility outside of the hospital.
The Submit Active Care Relationship Service Use Case addresses
organizations submitting data to establish an active care relationship
between a particular patient and that organization. The uses of active
care relationships in there are for routing ADT messages,
provider/physician org/care organization/payer searches for care
providers with active care relationship with patient.
The Submit Data to Provider Directory Use Case will populate and
maintain up-to-date Health Professional information for the purpose of
building a reliable statewide Directory. The Participating Organization
will provide information about Health Professionals, including but not
limited to name, contact information, organization(s), title(s),
position(s), health plan network participation and other associated
information as appropriate. Authorized Health Professionals can use the
Directory to look up Electronic Service Information (ESI), such as Direct
Addresses, to facilitate secure exchange of health information.
The Health Provider Directory Basic Query Use Case is designed to
provide up-to-date Health Professional, electronic address and
electronic service information, such as Direct addresses, to authorized
Health Professionals to facilitate contact look-up and secure exchange of
health information for the purpose of meeting operational, treatment or
payment obligations as defined in the HIPAA privacy and security rules
(information can not be stored within the querying organization).
Request Advanced Provider
Information from Statewide
Directory
The Health Provider Directory Advanced Query Use Case provides a
means for those Participating Organizations who wish to have access to
additional data elements that go beyond those available through the
basic Directory portal or API methods and have a need to extract, store
and analyze Directory data (Information can be stored over time for
other purposes).
Health Provider Search Service
The Health Provider Search Service allows HISP vendors to query and
retrieve Direct Secure Messaging addresses from the Statewide Health
Provider Directory.
Single Sign-On (SSO)Service (under
FSOA)
In this Use Case, the state is collaborating with HIN to conduct a
technical, logistical, and legal pilot of an identity exchange hub (IEH). The
IEH pilot will permit Medicaid to expand MICAM single sign-on (SSO)
services portal to access various State systems, e.g., licensure, public
health, and Medicaid EHR Incentive Program registration and
meaningful use attestation systems. The IEH activity establishes a
federated identity management infrastructure. IEH will eventually be
expanded to allow providers to authenticate to each of the sub-state
HIEs, the various provider portals to the state’s major insurance
companies, and a selection of the state's largest health systems.
The Common Key Service Use Case provides a consistent and reliable
way to match patients across multiple organizations, applications and
services, ensuring patient safety and high data integrity when data is
shared.
Common Key Service (CKS)
Exchange Integrated Care Bridge
Record (ICBR)
In Progress
Exchange Advance Directives with
Peace of Mind Registry
The Statewide Consumer Directory - Advanced Directives (e.g.: living
will) Use Case would utilize the Consumer Directory model which will
provide point-of-care access to critical patient medical and directive
information to enable efficient, SAFE treatment which incorporates the
patient's wishes by tying identified documents to the MPI.
The Medication Reconciliation Use Case calls for a transition-of-care
medication review. Medication Reconciliation is a regimented,
documented review to avoid drug errors during patient transfers.
Submit/Receive Statewide
Medication Reconciliation
Submit Cancer Notifications
Submit Immunizations
This Use Case is responsible for Population-based cancer surveillance in
Michigan for cancer control activities aimed at reducing the morbidity
and mortality of cancer, the second leading cause of death in the United
States. Michigan has an existing Michigan Cancer Surveillance Program
(MCSP, a.k.a. Cancer Registry), and this project will enhance it to receive
reporting form EHRs. The solution will use a slightly modified Michigan
implementation of the CDC’s National Program of Cancer Registries
(NPCR) Implementation Guide for Ambulatory Healthcare Provider
Reporting to Central Cancer Registries
http://www.cdc.gov/cancer/npcr/meaningful_use.htm as called out in
Meaningful Use Stage 2. This calls for a HL7 Clinical Document
Architecture (CDA) document being submitted for any patient encounter
that includes activities related to cancer, including diagnosis, referral,
treatment, and follow-up. This project will also include receiving HL7
version 2.5.1-based results messages from laboratories related to cancer
pathology results. The solution will use a slightly modified Michigan
implementation of the North American Association of Central Cancer
Registries (NAACCR) Pathology Laboratory Electronic Reporting Version
4.0 (April 2011) Implementation Guidelines
http://www.naaccr.org/StandardsandRegistryOperations/VolumeV.aspx.
Both types of messages will be received by the Data Hub and routed to
the enhanced Cancer Registry.
The Submit Immunizations Use Case is intended for immunization
providers and their vendors to assist in connecting to the state's Care
Improvement Registry. The Care Improvement Registry is an
immunization registry that compiles complete immunization histories for
children and adults in the state. Electronic Health Record (EHR) systems
that comply with Stage 1 Meaningful Use requirements must be able to
submit immunization administration data to their state registry.
Request Immunization
History/Forecast
Submit Syndromic Surveillance Data
Convert Syndromics
Submit Reportable Labs
Submit Birth Defect Notifications
The Request Immunization History/Forecast (Query By Parameter) Use
Case enables a Participating Organization to query for and obtain the list
of immunizations for a resident (adult or child), including those
immunizations received to date as well as a list and schedule of
vaccinations the patient is forecasted to receive in the future. The
Participating Organization will send an Immunization History and
Forecast query to HIN, the query will pass to the state data hub and
query the Care Improvement Registry data base. The query results will
be delivered back to the Participating Organization via the same
systems.
The Submit Syndromics Use Case sets forth the requirements for
Participating Organization to use HIN to submit Syndromic Surveillance
data through the state data hub to the Syndromic Surveillance System.
The Syndromic Surveillance System provides real-time situational
awareness of potential public health threats and emergencies. The
system sends alerts to public health officials when unusual increases in
symptom presentations are detected, and epidemiologists can analyze
findings, investigate further, and contact local public health agencies and
providers.
The Convert Syndromics Use Case positions HIN to receive a standard
ADT registration message, strip it of unneeded data, convert the
information into a syndromic message and submit it to the Syndromic
Surveillance System.
The Submit Reportable Labs Use Case sets forth requirements for
Participating Organizations to submit Reportable Lab data through the
state's data hub to the Disease Surveillance System. The Disease
Surveillance System is the communicable disease reporting system for
the state that helps public health officials identify outbreaks of diseases
such as the flu and meningitis. In addition, it facilitates coordination
among public health agencies, provides secure analysis of communicable
disease surveillance information, and addresses needs of traditional
disease surveillance.
The Submit Birth Defect Notifications Use Case will enhance the existing
registry by automating information submission for any patient
encounter that includes activities related to birth defects, including
diagnosis, referral, treatment, and follow-up.
Submit Newborn Screening - CCHD
(Pulse Oximetry)
This Use Case is responsible for collecting the Newborn Screening for
Critical Congenital Heart Defects (CCHD), Pulse Oximetry, Bloodpsot, and
Hearing test data as specified by the Platform. The Platform will issue an
acknowledgment or rejection notice back to the participant Source
System if available.The newborn screening mandate in Michigan Public
Health code section 333.5431 requires hospitals to screen the newborn
babies for, among other things, critical congenital heart defects (CCHD)
and report the CCHD test results to MDCH. Congenital heart defects are
the most common of birth defects, affecting nine in 1,000 newborns.
The most severe type is called critical congenital heart disease, requires
surgery or catheter intervention in the first year of life. CCHD remains
one of the most significant causes of infant death in the United States. A
simple non-invasive test called pulse oximetry helps detect CCHD in
newborns. Failure to detect CCHD early puts the baby at risk for death or
other serious complications within the first few days or weeks of life,
often requiring emergency room care.
Submit Newborn Screening Hearing
Test Results
Submit State Lab Orders/Receive
State Lab Results
Exchange Continuity of Care
Documents (non VA/SSA)
This Use Case will allow for the use of HIE network and technology to
rapidly and more efficiently deliver result information to the appropriate
providers. It will expand on the business continuity of information
transference through leveraged enterprise information technology
architecture and will serve to streamline the validation push/pull
environment.
The eHealth Exchange participant requesting patient information of a
HIN QO Use Case occurs when an organization on the eHealth Exchange
discovers a patient within one or more of HIN QOs, and queries and
retrieves documents related to that patient.
Exchange Patient Records Statewide
The Cross-QO Query Use Case allows querying between an eHealth
Exchange participant and a HIN QO via the eHealth Exchange for patient
records.
Exchange Continuity of Care
Documents with VA
The purpose of this Use Case is to set forth the requirements for VA to
use HIN to provide a means for the Participating Organization to request
and provide patient continuity of care information through HIN.
The CMS Electronic Submission of Medical Documentation Use Case
applies to CMS’s Electronic Submission of Medical Documentation
(esMD) program. The purpose of this Use Case is to set forth the
requirements for CMS esMD to use HIN to provide a means for the
Participating Organization to provide patient medical information
through HIN.
The Submit Clinical Quality Measures Use Case streamlines the
electronic Clinical Quality Measure reporting process. A HIN will collect
relevant data and submit the information to the state where Meaningful
Use Credit will automatically be given for validated reports.
Additionally, the CQM information can be used for cross clinical
comparison of measures.
Respond to CMS Electronic
Submission of Medical
Documentation (eSMD) Request for
CCD
Submit Clinical Quality Measures
(CQMs)
Review Clinical Quality Measures
(CQMs)
Respond to SSA Disability
Determination Requests for CCD
Facilitate Transport and Completion
of Health Risk Assessments (HRAs)
Birth Registry
Chronic Disease Registry
Submit Death Notifications
The purpose of this Use Case is to set forth the requirements for SSA to
use HIN to provide a means for the Participating Organization to provide
patient disability eligibility information through HIN.
In Progress
The Birth Registry Use Case automates submission of birth reporting to
state registries through the HIN common gateway.
The Chronic Disease Registry Use Case leverages the HIN infrastructure
to deliver Chronic Disease information to state registries. This enables
an epidemiologic understanding of prevention, management, and
control of chronic diseases in the state by supporting the surveillance,
planning, targeting and evaluation needs of a variety of departmental
programs, as well as identifies new trends and associations in chronic
disease prevention and control.
The Death Registry Use Case aims to automate death reporting from the
county level to the state's Electronic Death Registration System (EDRS)
through a HIN. The electronic death registry is interoperable with the
state HIE core services, including the MPI and integration engine, to
automatically send death records to systems within the Medicaid
Enterprise, streamlining the process and enabling death records to be
incorporated into the MMIS to prevent payments within a week of
death.
Statewide Controlled Rx
Repository/Request Controlled
Substance History from MAPS
Exchange Patient Consent
PLACEHOLDER: Autism
Consumer Incentives to Digitally
Document Health
Send/Receive Messages to/from
MiHIN Using Direct Secure
Messaging
Allergy Registry
The Patient Look Up (Cross Community Access XCA) Use Case enables
providers to query a patient utilizing a HIN and a Master Person Index
(MPI) as an "Initiating Gateway." The MPI coordinates the various
patient identifiers across different provider systems.
The Allergy Registry Use Case specifies the collection of allergy
information about patients and its access through the HIN common
gateway with the purpose of improving care and reducing negative
reactions to medicines.
Automated Cancer Results Query
(triggered by ADT, etc.)
In Progress
Automated Immunization Query
(triggered by ADT, etc.)
Automated Lab Results Query
(triggered by ADT, etc.)
Automated Specialized Registry
Query (triggered by ADT, etc.)
Behavioral Health Data
In Progress
Blind Push to a Known Partner
In Progress
In Progress
The Behavioral Health Data Use Case provides a way to facilitate
behavioral health data which requires extended patient consent.
The Blind “Push” to a Known Partner Use Case involves sending
documents to destination partners specifically identified by the sender.
In this use case, the recipient systems need human intervention to
understand the content and purpose of the communication, as there is
no computer processable metadata, beyond the addressee and what
may be provided informally “on the cover page”. This use case is similar
to fax communication in use today within healthcare.
Certificate Registry
The Certificate Registry maintains Direct and other certificates to enable
discovery by query.
Clinical Information Collection for
Federal Funding
The Clinical Information Collection for Federal Funding Use Case is used
for federal programs such as the Everyone with Diabetes Counts Project
which require the submission of clinical results for funding.
The Consent Directives (e.g.: DNR) Use Case, would utilize the Consumer
Directory model which will provide point-of-care access to critical
patient medical and directive information to enable efficient, SAFE
treatment which incorporates the patient's wishes by tying identified
documents to the MPI.
The Continuity of Care Summary Push Use Case involves providers
automatically sending Continuity of Care Summaries through a HIN. The
HIN identifies relevant providers and sends the messages in their
delivery preference.
Consent Directives
Continuity of Care Summary Push
Customer Satisfaction Reporting
This Use Case automates submission of customer satisfaction reporting
through the HIN to the state or CMS.
Diagnostic Imaging
The Diagnostic Imaging Use Case utilizes the HIN infrastructure to
securely electronically exchange Diagnostic Imaging between providers.
Disaster Preparedness
The Disaster Preparedness Use Case leverages Direct for health records
access and as a communication pathway in emergency situations.
During disasters, patients become dislocated and the need to access
medical records from outside an entity's own system in a timely manner
increases, but security and privacy issues remain constant.
The Do Not Resuscitate Declaration Use Case would leverage the
Consumer Directory model to establish an IHE standards-based query
and retrieve mechanism for authorized providers to electronically access
the location of a Do Not Resuscitate Declaration document.
Do Not Resuscitate Declaration
Doctor's Notes
The Doctor's Notes Use Case creates a standard method for exchange of
machine readable Doctor's notes which would be searchable by
keyword, EP, etc. through the HIN common gateway.
Drug-Allergy Trigger System
The Drug-Allergy Trigger System Use Case utilizes the HIN common
gateway to create a system that will alert EPs when patient may
potentially have adverse effects to a recommended drug, a component
of a complete drug reconciliation.
The Drug-Behavior Trigger System Use Case utilizes the HIN common
gateway to create a system that will alert EPs when patient may
potentially have adverse effects to recommended drug due to their
physical condition, a component of a complete drug reconciliation.
Drug-Behavior Trigger System
Drug-Drug Trigger System
The Drug-Drug Trigger System Use Case utilizes the HIN common
gateway to create a system that will alert EPs when two recommended
drugs cannot be taken concurrently, a component of a complete drug
reconciliation.
Electronic Prescription
The Electronic Prescription Use Case provides patients with information
regarding nearby prescription dispensaries, refill directions, etc.
Family Health History
The Family Health History Use Case involves the establishment of
searchable relevant chronic diseases of first degree relatives through the
HIN common gateway.
The Filterability of Data Use Case mandates standardization of
information fields with structured, query based, and sortable data.
General Use Case requirement.
Filterability of Data
Fraud Reduction
Health Education
HEDIS Regulatory Compliance
High Utilization Monitoring
Home Health Devices Alert
The Fraud Reduction Use Case requires new authentication techniques
to ensure someone is who they say they are like using voice biometrics
to verify callers on a phone.
The Health Education Use Case automates the process of providing
Patient-specific education resources identified by CEHRT to patients.
The HEDIS Regulatory Compliance Use Case would utilize a HIN to
automate the reporting of care and performance measures. Healthcare
Effectiveness Data and Information Set (HEDIS) is a tool used by more
than 90 percent of America's health plans to measure performance on
important dimensions of care and service.
The High Utilization Monitoring Use Case establishes patterns or
parameters of acceptable and unacceptable behavior, tests individuals
against these models, or looks for new and unusual patterns, in order to
identify outliers that demonstrate suspicious system utilization. The
goal being to reduce the number of admissions, duplication of services,
shorten time in hospitals and reduce over utilization.
The Home Health Devices Alert Use Case leverages the HIN
infrastructure to alert relevant care providers of problems detected by
home health devices.
Home Health Providers
The Home Health Providers Use Case is used to allow Home Health
Providers to access health information from remote locations.
In Case of Emergency (ICE)
The In Case of Emergency (ICE) Use Case would utilize the Consumer
Directory model to keep track of emergency, and emergency contact
information about a patient tied to the MPI.
The Infant Mortality Registry Use Case, like the Death Notifications use
case, transmits relevant infant death reporting data to the state through
a HIN as a central and secure mode of transmission.
Infant Mortality Registry
Labeled Documents Delivered to
Known Partner
Labeled Documents Pushed to
Known Partners
The Labeled Documents Delivered to Known Partner with Linked Patient
Use Case builds on the second use case by further strengthening the
workflow surrounding the point-to-point exchange by including
metadata that matches patient IDs across systems, and by notifying the
sender if there is a failure in delivery.
The Labeled Documents Pushed to Known Partners Use Case improves
workflow, as it goes beyond replacing basic fax capabilities. This data
package includes sufficient labeling by the sender to allow the receiving
system to derive the purpose of the communication without opening the
sent documents.
Living Will
The Living Will Use Case would leverage the Consumer Directory model
to establish an IHE standards-based query and retrieve mechanism for
authorized providers to electronically access the location of a Living Will
document.
Location Intelligence
The Location Intelligence Use Case utilizes Location-Based Services to
offer patients additional services such as finding the nearest pharmacy,
tracking on-call doctors, and even “checking in” and monitoring the
progress of mobile healthcare workers.
The Medical Power of Attorney Use Case leverages the Consumer
Directory model to establish an IHE standards-based query and retrieve
mechanism for authorized providers to electronically access the location
of a patient's medical power of attorney information.
Medical Power of Attorney
MIHP Registry
In Progress
Mobile Communications
The Mobile Communications Use Case requires a unified self-service
architecture that can be applied to voice, mobile web apps, or
interactive text messaging.
In the National ADT Notification Service, a patient is admitted to a
hospital in a different state than their active relevant physicians. The
hospital sends an ADT ‘Admit’ message to a HIN. HIN checks the Active
Care Relationship ServiceSM (ACRS) which contains information on what
providers are associated with this patient. HIN checks the Health
Provider Directory (HPD) to obtain the delivery preference for each of
those providers (i.e. a secure Direct email, an ADT message via HL7,
etc.). HIN notifies the providers, based on their delivery preferences,
that the patient has been admitted to the hospital. Other scenarios
include when a patient is discharged from the hospital or is transferred
to a different location (unit, bed) within the hospital or to another
facility outside of the hospital.
National ADT Notification Service
National Notifiable Disease
Surveillance System (NNDSS)
The National Notifiable Disease Surveillance System Use Case utilizes the
HIN infrastructure and the eHealth Exchange to report notifiable
diseases from the state to federal agencies.
Notify Providers of Disease
Outbreaks
In Progress
Nurse Home Visit Interface
Operations Communications with
Payers
In Progress
The Operations Communications with Payers Use Case refers to those
messages that are not directly required for billing. ADTs are an example
of an operations communication that would be shared with a payer.
The Opt-In Preferences Use Case would leverage the Consumer
Directory model to establish an IHE standards-based query and retrieve
mechanism for authorized providers to electronically access the location
of documents containing opt-in preferences.
The Opt-Out Preferences Use Case would leverage the Consumer
Directory model to establish an IHE standards-based query and retrieve
mechanism for authorized providers to electronically access the location
of documents containing opt-out preferences.
Opt-In Preferences
Opt-Out Preferences
Organ Donor/Tissue Donation (e.g.
Gift of Life)
The Organ Donor/Tissue Donation (e.g. Gift of Life) Use Case would
leverage the Consumer Directory model by adding organ/anatomical
donor registry reference information to the consent and advanced
directives location service of the HIN tied to the MPI.
Patient Access to EHR
The Patient Access to EHR Use Case calls for a patient portal where
patients can view their medical documents across multiple systems with
a single sign on. CMS Stage 2 requires 5% by attestation.
Patient Privacy
The Patient Privacy Use Case requires use new authentication
techniques to ensure health information is not given to unauthorized
persons, like using voice biometrics to verify callers on a phone.
Patient Retrieval of Immunization
History / Forecast
The Patient retrieval of Immunization History / Forecast Use Case allows
a resident to acquire their list of immunizations including those
immunizations received to date as well as a list and schedule of
vaccinations the patient is forecasted to receive in the future.
Patient Smoking Status
The Patient Smoking Status Use Case indicates documentation of
smoking history of patients thirteen and older and its access to the
information through the HIN.
Patient-Provider Message Exchange
The Patient-Provider Message Exchange Use Case is used for health
messages to be sent from one party to another over a direct secure
server.
The Payment Communications with Payers Use Case involves billing
related messages and supporting documentation. In lieu of having an
existing method of transport for healthcare claim/billing files (837s or
HCFA1500 or UB-92 formatted) Direct can be a method of delivery. In
addition it can be used to send supporting documentation necessary for
the payment of the claims in a secure manner.
The PHR Update & Maintenance Use Case would enable a patient to
determine which PHRs are associated with themselves.
Payment Communications with
Payers
PHR Update & Maintenance
Population Reporting (Medicare
Advantage Reporting)
Population Research and Analysis
Prescription Fill Status- Push
Prescription Tracking
Proactive Outbound IVR and Text
Messaging
The Population Reporting (Medicare Advantage Reporting) Use Case
streamlines quality data reporting. It is designed to accelerate internal
quality initiatives and improves Medicare Advantage Stars ratings. Each
Medicare Advantage organization must have an effective procedure to
develop, compile, evaluate, and report information to CMS in the time
and manner that CMS requires. The technical specifications for the
reporting requirements provide a description of the measures, reporting
timeframes and deadlines, and specific data elements for each measure.
In Progress
The Prescription Fill Status- Push Use Case allows the forwarding of a
patient's prescription filling status from pharmacies to providers with
correct Patient-to-Provider attribution for the purpose of monitoring
what prescriptions a patient is actually filling.
The Prescription Tracking Use Case stipulates information collection of
not only prescriptions given, but fulfilled as well, accessible through the
HIN.
The Proactive Outbound IVR and Text Messaging Use Case involves
automating reminders, enrollment confirmations, bill collections,
surveys and other patient interactions.
Provider Access to CQM Reports
The Provider Access to CQM Reports Use Case gives providers the
benefit of viewing the results of their own CQM reports, possibly with
state average benchmarks.
Public Health Reporting to CDC
In Progress
Pull via Community Sharing Health
Information Exchange
The “Pull” via the Community Sharing Health Information Exchange Use
Case uses health information managed and shared within a
“community”. The shared records are tagged with metadata to be
queried and retrieved. No geographic restrictions are placed on the
boundary of such communities.
The Push Clinical Data to Patient Use Case automates transmission of
medical records to a patient's PHR through Direct. This helps supports
Meaningful Use Stage two requirement requirements. One of the most
critical features of patient participation in directed exchange is the
patient’s capacity to prevent the spread of bad information as it is
happening.
The Pushing ADTs to Payers Use Case will streamline notification to
payers when a patient is admitted to a hospital. Today, this process is
totally manual (phone or fax), non-standard, time intensive, and subject
to error.
Push Clinical Data to Patient
Pushing ADTs to Payers
Query for Digital Certificate
The Query for Digital Certificate Use Case enables Direct addresses and
other certificates to be discoverable by maintaining a certificate registry.
Readmission, Risk Stratification,
Program Graduation
The Readmission, Risk Stratification, Program Graduation Use Case
allows for the inclusion of risk stratification by a Doctor, readmission to
hospital in a certain period, and patient's ability to graduate program in
Clinical Quality Measures.
In Progress
Referrals (breakdown of use cases
TBD)
Reminder Notices System
Reportable Labs to Disease Registry
Reviewed Medication List
The Reminder Notices System Use Case establishes an automated
messaging system for appointment reminders such as mail, email, text,
and voicemail through the HIN.
In Progress
The Reviewed Medication List Use Case is a patient-based account of all
active medications established in annual and transfer-of-care medication
reviews. The list is analyzed for therapeutic duplication and sub-optimal
drug combinations, it is then stored on a central data repository.
STARS & HEDIS Values
State Level Readmission Rate
The STARS & HEDIS Values Use Case incorporates existing performance
scores from organizations to create a community rating. STAR ratings on
the plan and contract level are calculated by CMS for Medicare Parts C
and D using relevant information including HEDIS ratings. Healthcare
Effectiveness Data and Information Set (HEDIS) is a tool used by more
than 90 percent of America's health plans to measure performance on
important dimensions of care and service.
The State Level Readmission Rate Use Case utilizes the Statewide ADT
Notification Service "feed" and the Master Person Index to establish a
patient readmission rate for the entire state.
Statewide Trust Bundle
The Statewide Trust Bundle Use Case establishes a single point of trust
that must be established for secure electronic information transfer
through a Direct infrastructure.
STD Surveillance Network (SSuN)
(Submit)
The STD Surveillance Network (SSuN) (Submit) Use Case streamlines
reporting of STD cases to SSuN through the HIN common gateway to
improve the capacity of national, state, and local STD programs to
detect, monitor, and respond rapidly to trends in STDs through
enhanced collection, reporting, analysis, visualization, and interpretation
of clinical, behavioral, and geographic information obtained from a
geographically diverse sample of individuals diagnosed with STDs.
The Stroke Registry Use Case will take the pre-existing stroke registry
and augment submission and access through the HIN common gateway
to improve stroke patient outcomes and the status of stroke care
throughout the state.
Stroke Registry
Structured Lab Results
The Structured Lab Results Use Case allows for X-rays, CAT scans, MRIs,
and other lab results to be discoverable through a query utilizing the HIN
common gateway.
Track Meaningful Use Compliance
In Progress
Universal Audit Repository
A Universal Audit Repository (UAR) will be developed to fully audit and
track information access and disclosure of PHI at the organization and
individual level, in compliance with HIPAA regulations.
In progress
Vulnerability Monitoring
Submit an idea for a Use Case: http://mihin.org/about-mihin/resources/use-case-submission-form/
Links to Useful Documents
Use Case Factory Diagram
41 FY '15 APD UCs Comparison
Copyright 2015 Michigan Health Information Network Shared Services