A soldier transfers from Fort Bragg to a VA clinic in San Antonio. His knee underwent ACL reconstruction eighteen months ago, and his physical therapist was tracking him through a careful return-to-duty progression. But when he pulls up his medical record at the VA, his entire course of rehabilitation, functional milestones, load-tolerance tests, movement screens, sits locked in a legacy VistA record that MHS GENESIS never fully absorbed.
This handoff failure isn't an edge case. It's the daily reality in federal physical therapy clinics where active-duty records, VA records, and emerging modernized systems are still learning to talk to one another. The electronic health record platforms that govern how federal physical therapists document care have undergone seismic shifts over the past decade, and understanding which system controls your clinic, and what standards it enforces, directly shapes how treatment stays mission-ready and how records survive across duty station transfers.
At the Federal Physical Therapy Section, we support clinicians who practice in military treatment facilities, Veterans Affairs clinics, Public Health Service units, and other federal healthcare systems. The organization brings together physical therapists and assistants from across these agencies to advance clinical excellence and advocacy in federal practice. When EHR systems don't talk cleanly, the cost shows up in patient care delays, repeated assessments, and lost context that should follow every service member and veteran through their continuum of care.
The shift from paper charts to federal EHR platforms
The Department of Defense rolled out MHS GENESIS, built on Cerner Millennium and Oracle Health architecture, beginning with initial site deployments in 2017. This modernized system replaced legacy platforms like AHLTA and CHCS across military treatment facilities, though the transition continues today at select bases. The VA, meanwhile, is migrating from decades of VistA and CPRS, the institutional backbone of VA record-keeping, toward a new Oracle Health EHR. That deployment paused after early rollout friction, then restarted at select VA medical centers with a measured, phased approach.
Federal PT clinics sit inside this transition zone. One clinic documents functional outcomes, treatment plans, and return-to-duty status inside MHS GENESIS. Thirty miles away, a VA facility's therapists are still working in VistA/CPRS. A Public Health Service clinic layers additional documentation requirements on top of whichever platform its agency has assigned. The result: clinicians in the same professional field are navigating three or four entirely different record architectures, each with its own template logic, coding standards, and interoperability assumptions.
We've written before about the federal scope of practice for physical therapists, and that scope extends directly into the documentation systems that capture it. When your clinic's EHR platform changes, your documentation workflow changes with it. Providers who understand the transition can help shape which outcomes data gets captured, and which functional gains risk being lost in the migration.
"Approximately 88 percent of office-based U.S. physicians have adopted an electronic health record system, a benchmark federal clinics are expected to meet or exceed."
How MHS GENESIS and VA systems document physical therapy care
Inside MHS GENESIS, encounter notes capture standardized functional outcome measures. Rather than free-text narratives, therapists enter the Defense and Veterans Pain Rating Scale, functional movement screens, and range-of-motion improvements into structured template fields. This standardization matters because downstream users, commanders, medical review boards, disability raters, pull return-to-duty and limited-duty determinations directly from these fields. Free-text notes don't populate those pulls. Structured data does.
A service member injured in theater gets evacuated to a military treatment facility, completes three weeks of PT, and receives a graded return-to-duty plan. When he transfers to a second base, the new physical therapist needs to pick up that grading return-to-duty plan directly from the record. When he leaves active duty and enters the VA system, his transition depends on that same record moving cleanly into VA's platform.
Interoperability between MHS GENESIS and the VA's modernized system runs through the Joint Health Information Exchange, an engineering layer designed to let a service member's PT history follow him through separation. But differences in system architecture, Cerner Millennium versus legacy VistA, mean data mapping and terminology crosswalks remain an active problem, not a solved one. How military and VA documentation systems differ goes deeper into these operational gaps.
Research supported by the National Institutes of Health has found that standardized data exchange formats such as HL7 FHIR reduce redundant documentation and repeat testing when patients move between military treatment facilities and VA care. The protocol exists. The full implementation across all facilities is still catching up.
What is ONC in healthcare?
The Office of the National Coordinator for Health Information Technology, housed within HHS, sets the certification criteria that EHR vendors, including Cerner and Oracle Health, must meet to sell into federal contracts. ONC's Health IT Certification Program is what verifies MHS GENESIS and VA's Oracle Health platform meet interoperability, security, and data-export standards.
The 21st Century Cures Act's information-blocking rule, enforced through ONC, requires federal clinics to make patient records, including PT notes, available electronically without unreasonable delay. For federal PT clinicians, ONC rules translate into daily requirements: patient portal access, structured data fields, timely note completion, and the ability to send records to other providers and to patients themselves on demand.
ONC doesn't dictate how you write a note. It dictates that the systems you work in must let that note move. The distinction matters.
What are examples of health information technology in federal PT clinics?
Core systems include MHS GENESIS for active-duty and select VA sites, legacy VistA and CPRS at remaining VA facilities, and the largely phased-out Composite Health Care System (CHCS). Patient-facing portals such as TRICARE Online and My HealtheVet let patients view PT appointment notes, home exercise programs, and progress summaries directly. Functional coding tools built into these systems reference standardized disability and functioning classifications so outcomes can be compared across facilities and agencies. The telehealth modules for remote PT follow-ups embedded in MHS GENESIS support remote consultations for service members and veterans stationed away from a treatment facility.
Here are the main EHR platforms, portals, and coding tools that federal PT clinics rely on:
- MHS GENESIS, built on Cerner Millennium and Oracle Health architecture
- VistA and CPRS, the VA's legacy system still operational at many VA medical centers
- TRICARE Online and My HealtheVet, patient-facing portals for appointment viewing and record access
- Functional coding frameworks that reference the International Classification of Functioning, Disability and Health (ICF)
- Telehealth modules for remote PT consultations and follow-up assessments
- Joint Health Information Exchange (JHIE) for cross-system data sharing between DoD and VA
Standards like the International Classification of Functioning, Disability and Health, developed by the World Health Organization, provide the framework that many federal functional outcome coding tools reference. When a PT enters a functional status code into any federal system, that code maps to ICF language so outcomes can be tracked across agencies and over decades of a service member's career.
What are the benefits and challenges of electronic health records?
Start with the benefits. A service member's PT records follow him across duty station transfers, so a new clinic isn't starting from zero on an existing rehab plan. Structured functional outcome data lets federal PT teams track non-pharmacologic management of pain in a way that supports reduced reliance on opioids, directly aligned with federal pain-management priorities. That structured data also feeds disability prevention and long-term cost control at scale: when outcomes data is consistent across facilities, leadership can identify gaps in care and redirect resources.
The challenges cut deeper. Interoperability gaps remain between federal systems and civilian EHR platforms, from athenahealth-run practices to hospital systems like Sutter Health, Atrium Health, and IU Health. When a veteran transitions to civilian care or a TRICARE beneficiary moves between employers, the full federal PT record often doesn't move with them. A civilian therapist sees fragments. Structured documentation requirements also add charting time per encounter, a tradeoff federal clinics manage through templated notes and dedicated documentation blocks, but it remains labor that doesn't translate to patient contact.
Peer-reviewed research indexed on PubMed links EHR adoption to reductions in duplicate imaging and lab testing across care transitions, alongside documented increases in clinician after-hours documentation time. It's a net win on efficiency, but the win is uneven, gains land at the system level, and burdens land on individual clinicians.
We have explored patient safety standards in federal PT clinics in detail before. EHR systems that enforce those safety standards are essential. But the safety benefit only accrues if the documentation culture inside your clinic embraces the structure the system provides.
What healthcare IT jobs support federal physical therapy practice?
Federal health IT roles directly touching PT documentation include clinical informaticists, EHR super-users and trainers at military treatment facilities, and interoperability coordinators managing DoD-VA data exchange. Positions are posted under federal HIT job series, such as GS-2210 IT Specialist and GS-0601 health system administrator tracks, alongside clinical PT billets. Public Health Service and state health department partnerships also recruit health IT staff to support federally funded clinic systems, widening the career pathway beyond DoD and VA alone.
When you see friction in your clinic, a referral that doesn't move, an outcome measure that vanishes during a transfer, a template that doesn't match your patient population, you're seeing a place where cross-agency communication between clinical and IT teams either succeeded or broke down. These positions exist to make that communication work.
"Health workforce research projects sustained growth in demand for clinical informaticists and health IT specialists across federal healthcare systems, with demand projected to remain strong over the next decade."
Documentation practices that keep federal PT records audit-ready
Audit-ready documentation isn't bureaucracy for its own sake. It's the foundation that supports readiness grading, disability determinations, and care continuity. Here's what works:
- Use the facility's standardized template fields for functional outcome measures rather than free-text notes. Free text doesn't populate return-to-duty or disability-rating pulls correctly, and your careful assessment gets locked away from the users who need it.
- Close out encounter notes within your facility's required completion window, commonly 24 to 72 hours depending on service branch policy. This aligns your documentation with medical board and readiness reporting timelines.
- Cross-check ICD-10 and CPT coding against the specific injury and duty-limitation categories used in return-to-duty grading, not just generic diagnostic codes. The specificity matters downstream.
- Route any cross-agency referral, DoD to VA, VA to civilian specialist, through your system's built-in interoperability or referral module rather than printed summaries. A digital referral keeps the full record intact; paper gets filtered and lost.
- When your system rolls out a new template or a new functional coding framework, attend the training and test it against your most common patient scenarios before go-live. Template design choices embed assumptions about what care looks like, and those assumptions need to match your clinical reality.
- Document the clinical reasoning behind graded return-to-duty and limited-duty determinations in structured fields so commanders and medical review boards can see your decision logic, not just your conclusion.
Building interoperable records for a mission-ready force
The soldier in San Antonio who lost his knee rehab notes, the veteran who can't see his own functional progress in a civilian clinic, the military treatment facility that repeats imaging because the prior workup didn't transfer cleanly, these aren't system failures in isolation. They're symptoms of a documentation ecosystem still in transition. Accurate EHR documentation directly supports readiness, disability prevention, and long-term cost control, not just administrative compliance.
As MHS GENESIS and VA's Oracle Health rollout continue to converge, federal PT clinicians who master today's documentation standards are positioned to shape tomorrow's interoperable record system. The clinicians doing the work in the field right now have insight into what structured data fields actually capture reality, where templates break down, and how records need to move to keep patients advancing. That voice matters in IT design, even if the channel for it remains informal.
Members are welcome to bring documentation questions, cross-agency friction points, and record-transfer frustrations directly to the organization. Shared standards keep pace with the systems in the field only when the field speaks up.