Battlefield Medical Record (Tactical EHR)

The Battlefield Medical Record lets a medic capture injuries, interventions and vital signs at the point of injury on a rugged handheld, by voice or touch, without a network connection. The record travels with the casualty through each role of care, and syncs to the theater and garrison health record systems your program designates when a connection is available. Speech recognition proposes entries; the medic confirms every one.

The problem it solves

Point-of-injury care is often documented on paper casualty cards, tape or a marker on the casualty, or not at all, because the medic's hands and attention belong to the patient. Cards are lost or illegible, receiving teams re-ask what was given and when, and much of the care never reaches the casualty's long-term health record or the trauma registry. Electronic tools built for clinics assume a network, a keyboard and time, none of which a medic has.

Who it’s for

• Combat medics, corpsmen and pararescue personnel providing point-of-injury care
• Battalion aid station and forward surgical teams receiving casualties
• Medical commanders and planners responsible for casualty care documentation
• Military health system program offices and informatics teams
• Trauma system staff who review care for performance improvement

1. Capture at the point of injuryThe medic records the casualty, injuries, interventions and vital signs by speaking or with a few large touch targets, on a device that works without any network.
2. Hand offWhen the casualty moves, the record moves with them, device to device, so the receiving team sees what has been done.
3. Sync when connectedRecords are held encrypted on the device and forwarded when a connection the program permits becomes available.
4. Continue the recordSynced records are delivered to the health record and registry systems your program designates, so point-of-injury care becomes part of the casualty's history.

Voice capture

Speech recognition on the device turns spoken entries into structured fields, with each entry shown for the medic to confirm.

Works without a network

All capture, handoff and viewing work on the device alone; sync happens only when an authorized connection is available.

TCCC card structure

Fields follow the DD Form 1380 TCCC Card, so the record matches what medics are trained to document.

Body diagram

Injuries and tourniquet locations marked on a front and back diagram with large touch targets usable with gloves.

Automatic times

Each intervention is time-stamped when recorded, and tourniquet time is shown prominently once applied.

Device-to-device handoff

The record transfers to the receiving team's device over a short-range link, with the handoff recorded on both.

Printed and on-casualty summary

Where the receiving team has no device, a summary can be printed or written from the screen to travel with the casualty.

Unidentified casualties

Records can start without identity and be reconciled later, so identification does not hold up documenting care.

Conflict-safe sync

When two devices hold different versions of a record, both are kept and flagged for review rather than one overwriting the other.

Amendments, not edits

After handoff, corrections are added as amendments with who made them and when; the original entry remains visible.

Mass casualty view

A team lead sees all casualties on their devices with triage category, key interventions and evacuation status.

Training mode

A separate mode for exercises and training uses fictional casualties and never syncs to health record systems.

Medic

Records care for casualties they treat and hands records off with the casualty

Receiving clinician

Accepts handed-off records and continues documenting care

Medical team lead

Sees all casualties in their team and coordinates evacuation

Medical records staff

Reconciles identities and sends records to designated health record systems

Trauma registry abstractor

Reviews point-of-injury records for the registry and performance improvement

System administrator

Manages devices, users and configuration without access to casualty records

Designated health record systems

Reconciled records are sent to the theater and garrison health record systems your program designates, through interfaces it approves, using HL7 FHIR where the receiving system supports it.

Trauma registry

Point-of-injury data exported in the format your trauma registry process uses, for abstractors to review.

Unit rosters

Roster data loaded to devices before an operation so a medic can select a casualty rather than type identity details.

Patient monitors

Vital signs from field monitors that offer a supported interface can be captured into the record.

Unit sync node

A small server at an aid station or command post collects records from devices and forwards them when a wider connection is available.

Identity and access

In garrison and at fixed facilities, staff sign in through your identity provider with CAC or PIV.

Device management

Devices are provisioned, updated and locked through your mobile device management system.

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.

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.

Program discovery

We work with your program office and medical leaders on the roles of care, devices, designated receiving systems and constraints of the environments the product will be used in.

Device and network configuration

The application is configured for your devices, short-range handoff methods, sync nodes and the networks your program permits.

Vocabulary and forms

Field structure, medication lists and spoken vocabulary are set to your formulary and documentation standards, and reviewed by your clinicians.

Interfaces

Interfaces to designated health record and registry systems are built and tested with their owners, under the approvals your program requires.

Exercises

Medics use training mode in exercises under realistic noise, light and glove conditions, and findings are fed back before operational use.

Authorization support and fielding

We provide the control mapping and evidence for your Risk Management Framework assessment, then field devices and train medics, receiving teams and records staff.

• 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.

• Have medics record a training scenario wearing gloves and under noise, and review how many voice entries needed correction
• Test a device-to-device handoff and a printed summary handoff
• Run devices offline for an exercise period and check that every record syncs afterward
• Create a sync conflict deliberately and see how it is presented for review
• Walk through identity reconciliation and release with your medical records staff
• Review the control mapping against your authorization requirements