One graph
Cardiology, PT, dental, and hospice write FHIR resources to the same patient — consent-aware, not copy-paste.
Halo · FHIR-native EHR
The chart that orbits the patient, not the department.
Incumbent EHRs were filing cabinets. FHIR arrived later as an export port. Halo is the inverse: HL7 FHIR R4 is the kernel — US Core in the United States, and the same graph for practices in Canada. Every Tuxil specialty writes to one record. A cardiology encounter becomes the rehab plan. Hospice inherits goals of care instead of a PDF. We implement Halo in all fifty U.S. states and across Canada.
Book a Halo walkthroughWhy Halo is different
| Typical stack | Halo |
|---|---|
| FHIR as an afterthought export | FHIR R4 / US Core as the system of record |
| A new install per specialty | One patient graph across Tuxil’s specialty map |
| Transitions as faxes and PDFs | Weight, rehab, and hospice as native pathways |
| Patient portal as a dumbed-down extract | Patients read the same resources clinicians write |
| Quality reporting as a warehouse project | Bulk FHIR and SMART apps on the same kernel |
Written for this map
Halo is not a generic hospital install stripped down. It is cut for the specialties Tuxil Health already serves — so a dental finding can surface for the internist, and weight-management labs travel into rehab without a new chart.
- Physiotherapy
- Optometry
- Dentistry
- Cardiology
- Family medicine
- Dermatology
- Orthopedics
- Otolaryngology
- Pathology
- Psychiatry
- Weight management
- Rehabilitation
- Hospice
Native FHIR
US Core is the kernel. SMART on FHIR apps plug in. Bulk export is a feature, not a warehouse project.
Practice-scale
Halo is built for independent and multi-specialty groups in all fifty U.S. states and Canada — weeks of implementation, not a decade.
Care programs stay on Tuxil Health: consulting, affiliation, weight management, rehabilitation, and hospice. Halo is the record those programs share.