Multi-Facility Integration (MFI)
Download
Report
Transcript Multi-Facility Integration (MFI)
Multi-Facility Integration
(MFI)
Data & Site Support
[email protected]
7/16/2015
Multi-Facility Integraqtion (MFI)
1
THE VISION
• 100% of Alaska Native health community
beneficiaries are properly identified and included
in user population and usage figures.
• 100% of all patient information (demographics,
eligibility, diagnoses, images, x-rays, needs, etc.)
legally allowed are available when and where
needed.
7/16/2015
Multi-Facility Integraqtion (MFI)
2
MFI Overview
• Module of Resource and Patient Management System
(RPMS)
• Used to share encounter data wherever it is allowed and
needed
• Maintains a centralized database consisting of the most
current registration demographics as well as all patient
encounters for that person
• Provides historical data when a patient presents at a
new location
• Centralized database available to statewide health
planners and to all ANMC facilities who have RPMS
access.
7/16/2015
Multi-Facility Integraqtion (MFI)
3
RPMS Overview
• Originated when Indian Health Service (IHS)
took copy of Veterans Administration (VA)
VISTA Patient Management System
• Written in MUMPS Computer language
(specifically created by hospitals for storing
patient data)
7/16/2015
Multi-Facility Integraqtion (MFI)
4
Why Share Data?
• Health Care
– More complete the HC history the better the HC
– Providers are more efficient if they know the full
patient history
– In Alaska there is the potential to be seen at more
than 250 different HC facilities.
– Many patients have records at up to six different
locations
7/16/2015
Multi-Facility Integraqtion (MFI)
5
Why Share Data? (Continued)
• Financial
– Compact/Contract funds for Alaska Natives is
calculated on number of active users
– If patients are not documented as having an
encounter in the last three years they do not show up
on active user counts
– If some patients/encounters are missing from the
state-wide database those patients are not
documented in any planning/research and therefore
under-represented
7/16/2015
Multi-Facility Integraqtion (MFI)
6
The MFI System Components
SITES
SHARING DATA
ENCOUNTER DATA
DEMOGRAPHIC DATA
INTERFACES
7/16/2015
Multi-Facility Integraqtion (MFI)
7
MFI Sites
97 MFI Sites (on 31 computers)
–
–
–
–
–
–
21 State PHN Computers
ANMC,
YKHC, PHN, Aniak
CAIHC, McGrath
Maniilaq, PHN, 10 villages
Metlakatla
–
–
–
–
–
–
–
Barrow, PHN, 7 villages
Ketchikan IC
Fort Yukon, PHN
Kodiak ANA, 6 villages
Small BBAHC, PHN, 28 villages
EAT
North Star, 7 Chugachmiut
villages
900,000 encounters/year sent to an average
of four sites each encounter
7/16/2015
Multi-Facility Integraqtion (MFI)
8
How MFI Shares Data #1
Network Mail
Demographics
&
Encounter Data
Facility A
(Parent Site)
7/16/2015
Integration Site
(MFI)
Network Mail
Encounters
Only
Message Processed
Then Encounter Data
Is Rerouted to other
sites Patient has visited
Facility B
(Satellite Site)
Multi-Facility Integraqtion (MFI)
9
How MFI Shares Data #2
Network Mail
Encounters Only
Integration Site
(MFI)
Network Mail
Message Processed
Then Encounter Data
Is Rerouted to other
sites Patient has visited
Facility A
(Parent Site)
7/16/2015
Demographics
&
Encounter Data
Facility B
(Satellite Site)
Multi-Facility Integraqtion (MFI)
10
MFI Encounter Data
• Normally limited to encounters that occurred
since a particular site joined MFI
• Historic encounters added (From 1/1/1990
onwards) to MFI database
• Encounter data captured is the basic
information stored in the RPMS Patient Care
Component (PCC)
7/16/2015
Multi-Facility Integraqtion (MFI)
11
MFI Demographic Data
• Not passed between sites, only sent to the MFI
(Integration) site.
• Where data from two or more sites needs to be
merged, newest data is selected (i.e. latest
address, emergency contact, etc.)
• Exception to above are Blood Quantum's where
ANMC data is selected if it exists
7/16/2015
Multi-Facility Integraqtion (MFI)
12
MFI Data Transferred #1
• Patient Visit Data
– Direct Outpatient
– Inpatient Encounters
– Clinic Visits
• Measurement Panels
• Hospitalization Stays
– In-Hospital
– Outpatient/Field
Visits
7/16/2015
• Contract Health Care
• Reproductive History
• Health Maintenance
Reminders
• Flowcharts
• Prenatal Data
• Supplements
• Scheduled Encounters
Multi-Facility Integraqtion (MFI)
13
MFI Data Transferred #2
• Eye Care
• Provider Details
• Purpose/Problem of
Visit
• Operative Procedures
– Inpatient, Outpatient
or Field visit
– Either direct care,
tribal program or
CHS
7/16/2015
•
•
•
•
•
Lab Tests
Immunizations
Exam
Medications
Activity Time &
Diagnostic Procedure
Results
• Dental
Multi-Facility Integraqtion (MFI)
14
MFI Data Transferred #3
• Specific Immunization Data Transferred
Contains immunizations specific to a particular
visit for a particular patient.
1. Immunization
2. Patient Name
3. Visit
4. Series
5. Reaction
6. Contrindicated
7/16/2015
Multi-Facility Integraqtion (MFI)
15
MFI Integration Site
• A centralized area containing the latest
demographic data for a patient
• Holds all Current AND Historical Encounter
data for a patient from any site visited
• Available for access by Health Care Providers,
Tribal Health Facilities, State Public Health
Nurses, etc. (Requires a completed MFI access
application form with supervisor approval faxed
to 729-3666).
7/16/2015
Multi-Facility Integraqtion (MFI)
16
Merging MFI Demographics #1
• Who’s responsible
– MFI (Integration Site); The MFI Database
Specialists
– Individual Sites perform own merges. NOTE: the
MFI Team are more than ready to provide help and
guidance when requested in merging records. The
overall goal is to fulfill the ANTHC Mission
Statement of providing the highest quality health
services.
7/16/2015
Multi-Facility Integraqtion (MFI)
17
Merging MFI Demographics #2
• Possible Reasons for not being able to merge
– Data input error (Transposed letters/numbers, etc.)
– Incomplete demographic data from site (unable to
confirm an exact match)
– Incorrect naming conventions (I.e. using nicknames)
7/16/2015
Multi-Facility Integraqtion (MFI)
18
Avoiding Duplicate Patients
Duplicate patient demographic data occurs if
thorough scanning of a patient during patient
registration is not performed during the
interview process. The following can help when
scanning;
• NAME: Enter as LAST NAME, FIRST (3-4
characters) – e.g. MCDONALD,RON
• DATE OF BIRTH: MM/DD/YYYY
• SOCIAL SECURITY NUMBER
7/16/2015
Multi-Facility Integraqtion (MFI)
19
MFI INTERFACES
• All sites connected via ATHSWAN- Alaska
Tribal Health System, Wide Area Network
• Only 1-to-1 interface required because we all use
RPMS
• Transmissions use VA “Filegrams”
• Will convert to HL7 by 2006
7/16/2015
Multi-Facility Integraqtion (MFI)
20
QUESTION TIME
• Any Questions?
• The MFI Team:
– Naomi Bahnke
– Tami Dietrich
– Betsy Dirks
7/16/2015
Database Specialist x2627
Database Specialist x2628
Database Specialist x2629
Multi-Facility Integraqtion (MFI)
21