We build HIPAA-ready software for healthcare.
Arena Health designs and builds web and mobile products for care providers and health-tech companies, connects them to EHRs and medical devices, and handles patient data the way HIPAA expects.
Please leave patient information out of your email.
- Where patient data lives
- EHRs, patient management systems, telehealth platforms and medical devices.
- What we build in between
- Apps, integrations and databases that keep that data encrypted, access-controlled and logged.
- Where it’s needed
- Clinicians, care teams, patients and the people who run the service.
What we build
Most projects combine several of these. Each one is shaped around the people who will use it and the data it carries.
Web and mobile apps
Products for patients, clinicians and operations staff on the web, iOS and Android, designed and built by one team.
EHR and patient-system integrations
Connections to electronic health records and patient management systems, so information is entered once and shows up where it’s needed.
Telehealth and remote monitoring
Remote visits and readings taken at home, built into your product rather than run as a separate tool beside it.
Medical device integration
Links between your software and the hardware it depends on, so a reading reaches the record without anyone retyping it.
Encrypted databases and secure cloud
Storage and hosting set up for protected health information: encrypted, backed up, and reachable only by the people and services that need it.
Anonymized analytics
Dashboards and reports built on de-identified data, so you can see how the service is running without opening anyone’s record.
Compliance documentation
The paperwork a healthcare product is expected to have in place, written alongside the software instead of reconstructed afterwards.
Need something that isn’t listed? Email us what you have in mind.
Our products
Alongside client work, we build our own software for medical education: simulators and classroom tools for the people who teach and learn care.
- Three languagesFull interface in English, Portuguese and Spanish
- Every screenRuns on desktop, tablet and smartphone
- Runs in your browser, nothing to installChrome 107+Edge 107+Safari 16+ · macOS, iPhone and iPadFirefox 104+An internet connection is required to load every application.
Train neonatal and pediatric ventilation without occupying a bed or risking a patient.iVent NeoPed
Ventilation simulator
An adult ICU ventilator in the browser, driven by real physiology.iVent Adult
Ventilation simulator
Clear calculations for neonatology and pediatrics, in one place.NeoPedCalc
Reference calculators
One stethoscope, the whole class listening.iMedCast
Shared digital stethoscope
Learn the ECG from the heart outward.3D Electrocardiogram
ECG simulator
One brain, seen on CT, MRI and ultrasound.NeuroSim 3D
Neuroimaging simulatorLive in January 2027
Many species, one imaging engine.NeuroSim VET
Veterinary neuroimaging simulatorLive in January 2027
Learn to scan before you touch a patient.POCUS Sim 3D
Ultrasound simulatorLive in January 2027
All of them are built for teaching and reference, and none of them keeps patient records. NeuroSim 3D, NeuroSim VET and POCUS Sim 3D go live in January 2027.
How our products are made
Built by physicians.Grounded in science.Reviewed by senior clinicians.
Our medical applications and simulators are programmed, supervised and guided directly by physicians, bringing together medicine, computer engineering, artificial intelligence and human physiology.
Evidence first
Every solution is designed with technical and scientific rigor, grounded in scientific publications, clinical studies, medical guidelines and peer-reviewed research from national and international journals.
Computational physiology engines
Our platforms run on physiology engines built from an extensive scientific literature. They reproduce the physiological and pathophysiological mechanisms of the human body, and its response to clinical interventions, dynamically and coherently.
Reviewed by senior clinicians
Our applications are tested, evaluated and supervised by senior healthcare professionals with broad clinical and academic experience, continually refining the accuracy of the simulations, the consistency of the physiological models and their value for teaching.
More than a picture of a clinical scene
We don’t build visual depictions of clinical situations. We build advanced simulation environments, driven by computational physiological models, scientific evidence and specialist medical knowledge.
Our commitment is to bring science, technology and clinical experience together in new ways to teach and train, helping healthcare professionals learn and keep improving.
Arena Health — technology built by physicians, grounded in scientific evidence and reviewed by senior healthcare professionals.
How a build handles patient data
HIPAA-ready means the safeguards are part of the design from the first sprint, not added in the month before launch. In the software we build, protected health information is:
Encrypted
In transit and at rest. Connections use TLS, and databases and their backups are encrypted, so an intercepted request or a copied disk doesn’t expose a record.
Access-controlled
Each role sees only the records and fields it needs to do its job. Authentication, session timeouts and permissions are designed with the product, not bolted on later.
Logged
The system records who viewed or changed a patient record, and when, so access can be reviewed and questions can be answered afterwards.
De-identified
Analytics and reporting run on data with the identifiers removed. Studying how a service performs doesn’t require knowing who the patients are.
Contained
Real patient data stays in the production systems built to hold it. It doesn’t go into development or test environments, application logs, error reports or email.
Documented
Data flows, access rules and third-party services are written down as the system is built. Your compliance paperwork is assembled from that record.
What an integration project looks like
Connecting to an EHR or a device is mostly a matter of finding out what the other system will let you do. The work tends to run in this order.
- 1
Map the data
Which systems, which records and fields, in which direction, and how often. It goes into a data-flow map before any code is written.
- 2
Find the interface
An HL7 v2 feed, a FHIR API, the vendor’s own API or a file export. We establish what each system really exposes and what its vendor will approve.
- 3
Arrange access
Sandbox credentials, vendor sign-off and the agreements that cover patient data. This step often sets the schedule, so it starts early.
- 4
Build against a sandbox
Development and testing run on synthetic records. Real patient data isn’t needed until the integration is ready for production.
- 5
Test with the people who’ll use it
Your team runs its real workflows end to end before anything goes live, and rollout happens in stages rather than all at once.
- 6
Hand over
You receive the documentation, monitoring for failed or delayed messages, and a clear account of how the integration is maintained.
Tell us what you’re building.
It starts with an email. We’ll read it and reply to arrange a call. Arena Health is part of Arena Code Software, so your message goes to the Arena Code inbox.
Please don’t include patient information in your email.
Useful to include
- What the product does and who uses it
- The systems it needs to connect to
- Where it stands today: an idea, in development, or live
- Any date you’re working toward
