1
Joint Patient Assessment and
Tracking System
Overview Fact Sheet
When a State requests Federal support to move patients, the US
Department of Health and Human Services, as the lead Federal
agency, will implement the patient movement system, which is
comprised of five functions: patient evacuation (to include
patient reception and management), medical regulating, en-route
medical care, patient tracking that is integrated with tracking of
general population evacuees, and re-entry.
The Joint Patient Assessment and Tracking System (JPATS) is a
“Web App” that is part of the National Disaster Medical System
(NDMS) Disaster Medical Information Suite (DMIS) that is
designed to track every patient moved by the federal government from start to finish. It can run
on any web browser and is simple to use in the field.
Patient
Patient
Movement
Movement
Patient
Patient
Evacuation
Evacuation
Medical
Medical
Regulating
Regulating
En
En
-
-
route
route
Medical Care
Medical Care
Patient
Patient
Tracking
Tracking
Patient
Patient
Re
Re
-
-
entry
entry
Patient
Patient
Movement
Movement
Patient
Patient
Evacuation
Evacuation
Medical
Medical
Regulating
Regulating
En
En
-
-
route
route
Medical Care
Medical Care
Patient
Patient
Tracking
Tracking
Patient
Patient
Re
Re
-
-
entry
entry
Are States allowed to use JPATS?
Yes! States and local health departments are encouraged to consider using JPATS for their
patient tracking application needs. HHS offers JPATS to State and local health departments
without any licensing fee. Entities can use JPATS for their own isolated incidents, for State-to-
State responses and for larger events when the Federal government responds. If an entity
implements JPATS, their use is independent of Federal activation.
What is required to use JPATS?
JPATS can be run on laptop and desktop computers and handheld mobile devices. The JPATS
web application works with all commercial-off-the-shelf (COTS) Web Browsers (e.g., IE,
Chrome, Firefox) on current Microsoft and Apple operating systems (Windows 7 & OS 10). It is
also companionable with most handheld devices running iOS and Android. JPATS is compatible
with most universal handheld barcode scanner devices and apps.
What is required to support the JPATS Web Application?
JPATS runs in a Linux environment (Apache Tomcat) and can use either an Oracle or MySQL
data base to support the application. MySQL is an open source database available free of charge.
2
What does it cost to implement JPATS?
There is no licensing fee charged by ASPR to utilize JPATS. There are software and hardware
cost considerations, but the costs to implement JPATS are too variable to generically answer.
JPATS Technical Support with ASPR will work with interested parties in determining the
specific requirements. Cost considerations include hardware (i.e., network servers, handheld
barcode scanners, computers and other mobile devices to run the program), application support
(i.e., database platform, operating system, network server, hosting environment), and staff time
(i.e., IT staff to maintain the system, program staff to maintain the overall patient tracking
program, training time for all end users).
What support does ASPR provide?
ASPR JPATS Technical Support will provide an initial overview, a second more technical
discussion with the Information Technology staff and will provide access to numerous training
tools, including online training, videos, and hands on module training. ASPR will also provide
JPATS training materials, such as the JPATS Quick Guide for field reference.
What is the process to implement JPATS?
The JPATS implementation process includes:
An initial meeting with ASPR JPATS Technical Support to discuss JPATS capabilities
and to determine requirements.
Following the initial meeting, ASPR will provide login information for the JPATS
training application to allow interested parties to sample and experience JPATS. The
training also contains a training program on features and use.
A second meeting is scheduled with program and information technology staff to discuss
the detailed technical requirements and to develop an implementation plan.
If the decision is made to pursue JPATS, ASPR will provide assistance in deploying the
system and will provide the FTP code necessary to implement.
How do I find out more information on JPATS?
Please review the attached PowerPoint presentation. More information is available from ASPR.
Interested States or local health departments should contact their ASPR Regional Emergency
Coordinator to set up the initial meeting with JPATS staff described above.
Title
ESF #8 Patient Movement
HHS/ASPR/OEM
Overview
•
•
•
•
•
•
•
•
•
JPATS Background
JPATS History
DMIS Overview
JPATS and TRAC2ES
Functionality
Current Status
Data Sharing
─ DMIS System Of Record Notice (SORN)
State Questions
Summary
1
Joint Patient Assessment and
Tracking System (JPATS)
JPATS Background
•
•
•
Developed MOU with DoD in 2007 to get a civilian version
of their patient tracking system Joint Patient Tracking
Application (JPTA)
─
─
This was to address the presidential directives on patient
tracking.
Started making changes to JPATS in 2009
Web based application: Runs on any Browser
─ Visible outside of the HHS Network
Easy to use in the Field
─
─
Minimum training requirements
No specific IT Hardware required
2
JPATS History & Highlights
•
•
•
•
─
─
•
─
Needed a way to track Grandma when moved in the Federal
Patient Movement system, from start to finish
“FEDEX” capability
Not HIPAA constrained, but can link to Electronic Medical
Record (EMR)
JPATS is a “Web App” that is part of the NDMS Disaster
Medical Information Suite (DMIS)
JPATS: Joint Patient Assessment & Tracking System
EMR: Electronic Medical Record
Deployable EHR
HIR: Health Information Repository
DMIS Applications
5
JPATS is easy, the process is
complicated!
JPATS Functionality
6
•
•
Step by step registration
process
Design leverages touch
screen functionality, bar
code scanning, and
patient photographs for
identification
Current JPATS Status
•
─
•
─
•
─
•
•
Version 5.5 deployed and available for States;
Look and feel of typical browser based web application
MOA with DoD and VA on JPATS use
Trained DoD and VA FCCs
Delivery Platforms and apps;
Web application is browser agnostic
Works on COTS Operating Systems (i.e., Windows, Apple)
and Handheld devises operating system(i.e., iOS, Android)
ESF #8 Patient Tracking
Data Sharing
•
•
─
─
─
─
•
─
─
─
─
DMIS System of Record Notice (SORN) 2013-3118 (27 DEC 2013)
Outlines:
the Purpose of the Data collected,
Authority to collect Data
Individuals Covered
Routine Uses of the Data and Categories of Users
Allows ASPR to share data with ESF-8 Partners within;
the Federal Government (e.g., DoD);
State,
City
and local ESF-8 Partners.
Common State Questions
•
─
─
•
─
─
─
•
•
Operating System
States using variety of DB
JPATS runs on Oracle…have MySQL version
Cost of purchasing OS and associated software
Operating System: Linux (RedHat, Apache Tom Cat)
Data Base (dB): Oracle & MySQL
Deployable Versions:
OVF for Virtual Machine (VM) deployment
Local infrastructure and support concerns
10
Summary
•
•
─
•
─
JPATS is the ESF #8 Federal patient tracking system
Is JPATS available for State to deploy their own Version
Yes
Do we have the legal authority to move data from one
authority to another?
Yes
11
12
