Security, data and compliance in Battlefield Medical Record (Tactical EHR)

How Battlefield Medical Record (Tactical EHR) protects data and supports your compliance obligations.

Security controls

Encryption on the device

Records are encrypted on each device and in transit, and a lost device can be locked and cleared when it next connects.

Role-based access

Each person sees the casualties their role and unit allow; administrators manage devices without seeing casualty records.

Full audit trail

Every entry, view, handoff, amendment and release is logged with the person and time, and cannot be edited.

Encryption and keys

Data held by Moraph is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Cleared US-person support

Support tickets for defense clients are handled only by Moraph staff who are US citizens with active clearances.

US-only hosting

When hosted by Moraph, data stays in the United States region. Deployments in your own environment run under your authority.

Requirements it supports

• DD Form 1380, Tactical Combat Casualty Care (TCCC) Card
• DoD Instruction 6040.45, DoD Health Record Life Cycle Management
• DoD Manual 6025.18, Implementation of the HIPAA Privacy Rule in DoD Health Care Programs
• HIPAA Security Rule (45 CFR Part 164, Subpart C)
• Privacy Act of 1974 (5 U.S.C. 552a)
• DoD Instruction 8510.01, Risk Management Framework for DoD Systems

The product supports these requirements; meeting them remains your organization's responsibility.

Where it runs

• On tactical devices: The application runs on rugged handhelds your program approves, working fully offline.
• Unit sync node: A small server at an aid station, ship or command post collects and forwards records within the unit's network.
• Your environment: The central service installed in your own environment, including networks operated under your authority, with Moraph providing software and support as you allow.
• Moraph cloud (US): Hosted by Moraph in the United States region for unclassified use such as training, garrison sync and program evaluation, under a business associate agreement where PHI is involved.

Limitations

• It does not make treatment decisions or direct care. It records what clinicians do; protocols and clinical judgment remain with your medical personnel.
• Speech recognition can mishear in noise or under stress. Every proposed entry must be confirmed by the medic, and touch entry is always available.
• Records reach long-term health record systems only when a permitted connection is available and the receiving system's interface accepts them.
• It is not a full hospital health record. Once a casualty reaches a facility with its own health record system, care is documented there.
• Moraph does not claim accreditation or an authorization to operate for the product. Moraph maps controls and supports your own assessment and authorization.
• Operation on classified networks takes place in your environment, under your authority and accreditation. The Moraph-hosted service handles unclassified information only.
• Device hardware, radios and networks are supplied by your program; the product depends on what they make available.
• Interfaces to other systems depend on the owners of those systems approving and supporting them.