Defense & intelligence · Moraph software

Battlefield Medical Record (Tactical EHR)

Record casualty care at the point of injury, by voice, and keep it with the patient

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

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.

  • Paper casualty cards are lost, damaged or unreadable at handoff
  • Medics cannot stop treating to type into a device
  • Receiving teams lack a reliable record of what was given and when
  • Point-of-injury care rarely reaches the long-term health record or trauma registry

Who uses it

  • 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

Requirements it supports

DD Form 1380, Tactical Combat Casualty Care (TCCC) CardDoD Instruction 6040.45, DoD Health Record Life Cycle ManagementDoD Manual 6025.18, Implementation of the HIPAA Privacy Rule in DoD Health Care ProgramsHIPAA 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.

See how it works

A short walkthrough

Illustrative screens with fictional sample data. They show the workflow, not any client’s data or configuration, and the layout of the product itself differs. A live demonstration uses the product with sample data.

  1. Step 1

    Recording care by voice

    The medic speaks as they work, and each proposed entry appears for a single tap to confirm or correct.

    Casualty C-0417 · Unidentified, roster match pending

    Mechanism
    Blast (fictional training scenario)
    Injury
    Left lower leg, severe bleeding
    Tourniquet
    Left thigh · 10:42
    Tourniquet time
    38 minutes
    Pulse
    112
    Respirations
    22

    Proposed from speech, awaiting confirmation

    • Medication: analgesic per your formulary, 10:51
    • Second tourniquet considered, not applied
    • Casualty alert and responsive
    The medic speaks as they work, and each proposed entry appears for a single tap to confirm or correct.

  2. Step 2

    The mass casualty view

    The team lead sees every casualty the team is treating, with what matters for evacuation.

    CasualtyTriageKey interventionMedicEvacuation
    C-0417UrgentTourniquet 38 minMedic 2Requested
    C-0418UrgentAirway adjunctMedic 1Requested
    C-0419PriorityDressing, splintMedic 3Pending
    C-0420RoutineDressingMedic 3Not required
    The team lead sees every casualty the team is treating, with what matters for evacuation.

  3. Step 3

    Handing off the casualty

    The record moves with the casualty, and each handoff is recorded on both devices.

    Casualty C-0417 · Chain of care

    1. Record started at point of injuryMedic 2
    2. Tourniquet applied and time capturedMedic 2
    3. Handed off to evacuation teamMedic 2
    4. Vital signs added in transitEvacuation medic
    5. Handed off to aid station and acceptedReceiving clinician
    6. Assessment and disposition recordedReceiving clinician
    The record moves with the casualty, and each handoff is recorded on both devices.

  4. Step 4

    Sync status

    When a permitted connection is available, records forward from devices through the unit sync node.

    DeviceMedicRecords heldLast syncStatus
    Device 07Medic 12TodaySynced
    Device 11Medic 21TodaySynced
    Device 14Medic 332 days agoNot synced
    Device 02Evacuation medic1Today1 conflict
    When a permitted connection is available, records forward from devices through the unit sync node.

  5. Step 5

    Reconciling identity

    Medical records staff match point-of-injury records to the casualty's confirmed identity before sending them on.

    Record C-0417 · Identity reconciliation

    Started as
    Unidentified casualty
    Roster match proposed
    Service member 50213 (fictional)
    Matched on
    Unit, roster number, time and location
    Conflicting version
    1 from Device 02
    Receiving systems
    Designated health record, trauma registry

    Before release

    • Resolve the vital signs conflict with the evacuation medic
    • Second records reviewer to confirm the identity match
    • Release to designated systems
    Medical records staff match point-of-injury records to the casualty's confirmed identity before sending them on.

  6. Step 6

    Documentation completeness

    Medical leaders see which parts of the casualty card are most often missed, to focus training.

    FieldUnit AUnit BUnit C
    Mechanism of injury96%91%98%
    Tourniquet time100%94%100%
    Medications with time88%71%90%
    Vital signs, two or more sets64%58%79%
    Medical leaders see which parts of the casualty card are most often missed, to focus training.

Workflows

The principal workflows

  1. Capture at the point of injury

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

    • Medic starts a casualty record from a roster entry or as an unidentified casualty
    • Injuries marked on a body diagram by touch or by voice
    • Interventions such as tourniquets and medications spoken as they are given, with times captured
    • Speech recognition proposes structured entries; the medic confirms or corrects each
    • Vital signs entered by voice or from connected monitors where the unit uses them

  2. Hand off

    When the casualty moves, the record moves with them, device to device, so the receiving team sees what has been done.

    • Medic marks the casualty ready for evacuation
    • Record transferred to the receiving device over a short-range link, or by a printed summary where no device is present
    • Receiving team sees injuries, interventions and times at a glance
    • Receiving team accepts the handoff, and the record shows who held the casualty when
    • Care continues to be added in the same record

  3. Sync when connected

    Records are held encrypted on the device and forwarded when a connection the program permits becomes available.

    • Device detects an authorized network or a unit sync node
    • Completed and updated records are queued and forwarded
    • Conflicts between two devices' versions are kept, not overwritten, for review
    • Synced records are released from the device according to your retention setting
    • Sync status shown on each record

  4. Continue the record

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

    • Records matched to the casualty's identity by medical records staff
    • Unidentified casualty records reconciled when identity is confirmed
    • Records sent to designated health record systems through approved interfaces
    • Trauma registry abstractors receive point-of-injury data for their review
    • Corrections recorded as amendments, with the original kept

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Medic

Combat medic, corpsman, pararescueman, medical technician

Provides point-of-injury care and documents it as it happens, without stopping care to type.

Sees

  • Records they started or that were handed to them
  • The casualty's injuries, interventions, times and vital signs
  • Sync status of records on their device

Does

  • Starts casualty records, including for unidentified casualties
  • Records injuries, interventions, medications and vital signs by voice or touch
  • Confirms or corrects each entry proposed by speech recognition
  • Hands the record off to the receiving team
  • Prints or writes out a summary when no receiving device is available

Cannot

  • See records of casualties they have not treated or received
  • Delete an entry after handoff; they can add an amendment
  • Send records to health record systems directly
Approvals
None; their entries stand as the clinical record, and later corrections are amendments.
Notified about
Tourniquet time reminders on their casualties, handoff confirmations, and records that have not yet synced.

Receiving clinician

Physician, physician assistant, nurse, medic at an aid station or forward surgical team

Takes over care with a clear picture of what has been done and continues the same record.

Sees

  • Records handed off to their device or synced to their facility
  • The full history of care and handoffs for each casualty
  • Amendments and who made them

Does

  • Accepts handoffs and confirms receipt
  • Adds assessments, interventions and medications
  • Records disposition and evacuation
  • Hands the record on at the next transfer
  • Adds amendments when earlier information proves wrong

Cannot

  • Remove or overwrite another clinician's entries
  • See records for casualties not in their care unless their role grants it
  • Reconcile identities; that belongs to medical records staff
Approvals
None; entries are attributed to them.
Notified about
Incoming handoffs and casualties marked for evacuation to their facility.

Medical team lead

Senior medic, platoon or company medical lead, aid station officer in charge

Coordinates care and evacuation for multiple casualties and keeps track of who is where.

Sees

  • All casualties recorded by their team's devices within range or synced
  • Triage category, key interventions and tourniquet times
  • Evacuation status and handoffs

Does

  • Reviews the mass casualty view and assigns casualties to medics
  • Sets evacuation priority
  • Confirms handoffs to evacuation teams
  • Reviews unsynced records after an event

Cannot

  • Change entries made by a medic, other than by amendment
  • Change device configuration or users
  • Send records to health record systems
Approvals
None in the record; evacuation decisions follow your procedures.
Notified about
New casualties recorded by the team, tourniquet time reminders and records not yet synced.

Medical records staff

Medical records technician, patient administration, health information management staff

Makes sure point-of-injury records reach the right patient's long-term record.

Sees

  • Synced records awaiting identity reconciliation or delivery
  • Conflicting versions flagged by sync
  • Delivery status to each designated system

Does

  • Matches records to the casualty's confirmed identity
  • Reconciles unidentified casualty records
  • Resolves sync conflicts with the clinicians involved
  • Releases records to designated health record systems
  • Answers requests for copies under your release procedures

Cannot

  • Change clinical entries; they can only route them for amendment
  • Merge two casualties without a second reviewer
  • Release records outside the designated systems and approved requests
Approvals
Identity merges and splits require a second medical records reviewer.
Notified about
Records awaiting reconciliation, delivery failures and sync conflicts.

Trauma registry abstractor

Trauma nurse coordinator, registry abstractor, performance improvement staff

Uses point-of-injury data for the trauma registry and to improve casualty care.

Sees

  • Reconciled records within the scope granted
  • Interventions, times and outcomes recorded across roles of care

Does

  • Reviews records for registry abstraction
  • Exports registry data in the agreed format
  • Notes documentation gaps for training feedback

Cannot

  • Change any clinical entry
  • See records outside the scope granted
  • Release records outside the registry process
Approvals
Their scope is approved by the medical records lead or privacy officer.
Notified about
Newly reconciled records within their scope.

Privacy officer

HIPAA privacy officer, Privacy Act officer

Oversees who can see casualty records and how they are released.

Sees

  • Access and release logs
  • Role assignments and scopes
  • Requests for copies and their outcomes

Does

  • Reviews access logs and investigates unusual access
  • Approves scopes for registry and research access
  • Approves release procedures and exceptions

Cannot

  • Change clinical entries
  • Edit or delete the access log
Approvals
Approves non-routine releases and registry or review access scopes.
Notified about
Access outside a person's normal pattern and releases awaiting approval.

System administrator

Medical logistics or communications technician, health IT administrator

Keeps devices, users and configuration ready, without access to casualty information.

Sees

  • Devices, their software versions and last sync
  • Users, roles and units
  • Configuration such as retention and sync settings

Does

  • Provisions and retires devices
  • Assigns users to roles and units
  • Applies approved software updates
  • Remotely locks or clears a lost device when it next connects

Cannot

  • Open casualty records
  • Grant themselves a clinical role
  • Change retention or release settings without the privacy officer's approval
Approvals
Changes to retention, sync and release settings are approved by the privacy officer.
Notified about
Devices not synced for a period you set, devices reported lost and updates available.

Permissions at a glance

ActionMedicReceivingTeam leadRecords staffRegistryPrivacyAdmin
Start a casualty recordFullFullFullNo accessNo accessNo accessNo access
Record care and vital signsOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo accessNo access
Hand off a recordOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo accessNo access
Add an amendmentOwn work onlyOwn work onlyOwn work onlyNo accessNo accessNo accessNo access
View team casualtiesOwn work onlyOwn work onlyFullNo accessNo accessNo accessNo access
Reconcile identityNo accessNo accessNo accessFullNo accessView onlyNo access
Merge or split casualty recordsNo accessNo accessNo accessApprovesNo accessView onlyNo access
Send to health record systemsNo accessNo accessNo accessFullNo accessView onlyNo access
Export registry dataNo accessNo accessNo accessNo accessFullApprovesNo access
View access and release logsNo accessNo accessNo accessView onlyNo accessFullView only
Manage devices and usersNo accessNo accessNo accessNo accessNo accessView onlyFull
Change retention and release settingsNo accessNo accessNo accessNo accessNo accessApprovesFull
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Clinicians see the casualties they treat or receive; wider access, such as for registry review, is granted by scope and recorded.
  • Nothing in a clinical record is deleted after handoff. Corrections are amendments that show who made them and when, beside the original.
  • Administrators manage devices and users but cannot open casualty records, and changes to retention or release settings need the privacy officer's approval.
  • Roles and units are configured with your program during implementation and can follow your identity system's groups when devices are in garrison.

Features

What it does

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 care is never delayed for identification.

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.

Integrations

How it connects to your systems

Connects toHowWhat flows
Designated health record systemsReconciled 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.Out: casualty encounters, injuries, interventions, medications and vital signs.
Trauma registryPoint-of-injury data exported in the format your trauma registry process uses, for abstractors to review.Out: registry data set for reconciled records.
Unit rostersRoster data loaded to devices before an operation so a medic can select a casualty rather than type identity details.In: roster entries limited to the fields your program approves.
Patient monitorsVital signs from field monitors that offer a supported interface can be captured into the record.In: vital sign readings with time.
Unit sync nodeA small server at an aid station or command post collects records from devices and forwards them when a wider connection is available.In and out: records and handoffs between devices and designated systems.
Identity and accessIn garrison and at fixed facilities, staff sign in through your identity provider with CAC or PIV.In: user identity and group membership for role assignment.
Device managementDevices are provisioned, updated and locked through your mobile device management system.In: device enrollment and policy; out: device status.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

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.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Casualties by event

For medical team leads and medical planners

Casualties recorded for an event or period, with triage category, key interventions, evacuation and current location in the chain of care.

Break down by
Event, Unit, Triage category, Role of care
Delivered as
On device for the team; live view at sync node or garrison
Used for
Tracking casualties through evacuation and after an event.

Unsynced records

For medical team leads and system administrators

Records still held only on devices, with the device, the medic and how long since the last sync.

Break down by
Unit, Device, Age
Delivered as
On sync node; live view in garrison
Used for
Making sure every record reaches the health record before devices are reassigned.

Reconciliation queue

For medical records staff

Synced records awaiting identity confirmation, unidentified casualties and sync conflicts.

Break down by
Status, Unit, Age, Issue type
Delivered as
Live view; CSV export
Used for
Working through records so none is left unmatched.

Delivery status

For medical records staff and health IT

Records sent to each designated system, accepted, rejected or pending, with the reason for any rejection.

Break down by
Receiving system, Status, Date
Delivered as
Live view; CSV export
Used for
Finding and fixing records that did not reach the long-term record.

Clinical quality

Documentation completeness

For medical leaders and trainers

How often key TCCC fields such as tourniquet time, medications and vital signs were recorded, by unit.

Break down by
Unit, Field, Period, Role of care
Delivered as
Live view; PDF and CSV export
Used for
Targeting training on documentation.

Interventions and times

For trauma system and performance improvement staff

Interventions recorded, their times relative to injury and handoff, across roles of care.

Break down by
Intervention type, Unit, Role of care, Period
Delivered as
Live view; CSV export
Used for
Reviewing care for performance improvement.

Voice entry corrections

For medical leaders and the program office

How often medics corrected entries proposed by speech recognition, by field and conditions recorded.

Break down by
Field, Device model, Unit, Period
Delivered as
Live view; CSV export
Used for
Improving vocabulary and training where speech recognition is least reliable.

Privacy and audit

Access log

For privacy officer and auditors

Who viewed, changed, exported or released which records, and when.

Break down by
User, Record, Action, Date range
Delivered as
On request; CSV and PDF export
Used for
Investigating unusual access and answering audit requests.

Releases and disclosures

For privacy officer

Records released outside routine delivery, the requester, the basis and the approver.

Break down by
Requester type, Basis, Approver, Date
Delivered as
Live view; PDF and CSV export
Used for
Accounting for disclosures as privacy rules require.

Devices

Device readiness

For system administrators and medical logistics

Devices by unit with software version, battery and storage status at last check-in, and last sync.

Break down by
Unit, Device model, Software version, Last sync
Delivered as
Live view in garrison; CSV export
Used for
Making sure devices are ready before an operation or exercise.

Exports, access and evidence

  • Team-level views work on the device and at the sync node without a network; program-wide reports are available once records have synced.
  • Every report respects the viewer's role and scope, so a team lead sees their team and registry staff see the records within their granted scope.
  • Reports can be exported to CSV, and quality and audit reports to PDF, with each export recorded in the audit trail.
  • Training-mode records are kept apart and never appear in clinical, registry or quality reports.
  • Data can be delivered to your program's analytics environment for reporting alongside other health data, through interfaces your program approves.

Deployment

Where and how 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.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

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.

Limitations

What it does not do

Worth knowing before you evaluate it.

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

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

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

Questions

Frequently asked questions

Does it need a network to work?

No. Capture, handoff and viewing all work on the device alone. Records sync only when a connection your program permits is available.

What if speech recognition gets something wrong?

Every proposed entry is shown for the medic to confirm or correct, and touch entry is always available. Nothing is recorded from speech without confirmation.

How does the record reach the casualty's long-term health record?

Synced records are matched to the casualty's identity by medical records staff and sent to the health record and registry systems your program designates, through interfaces those systems' owners approve.

Is it authorized for use on our networks?

Authorization is your program's decision. Moraph does not claim accreditation for the product; we provide control mapping and evidence to support your Risk Management Framework assessment.

Can we use it in exercises?

Yes. Training mode uses fictional casualties, keeps those records apart and never sends them to health record systems.

Which devices does it run on?

Rugged handhelds your program approves. Supported devices and operating systems are confirmed during program discovery.

Next steps

Evaluate Battlefield Medical Record (Tactical EHR)

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Battlefield Medical Record (Tactical EHR) guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Battlefield Medical Record (Tactical EHR) support guide.

Related products