Device data in the chart, through the interface you already run.
We do not ask your interface team to adopt a new engine or a new standard. Formcloud speaks the ones you have, and we bring the mapping work with us.
- HL7 v2
- 2.5.1: ADT in; ORU, MDM out
- FHIR
- R4: Observation, Device, DeviceMetric, Patient, Encounter, DiagnosticReport
- Launch
- SMART on FHIR, in-context views
- Typical go-live
- 8 to 12 weeks from kickoff
Interfaces
What each interface carries and which direction it runs.
| Interface | Direction | Carries | Typical use |
|---|---|---|---|
| HL7 v2 ADT | In | Admissions, transfers, discharges | Associating a device with a patient and an encounter |
| HL7 v2 ORU | Out | Observations and results | Vital signs and rhythm summaries into flowsheets |
| HL7 v2 MDM | Out | Documents | Corta episode reports as PDF with structured header |
| FHIR R4 Observation | Out | Individual measurements | Trends, remote monitoring programs, research stores |
| FHIR R4 Device | Out | Device identity and status | Device association and asset views |
| FHIR R4 DiagnosticReport | Out | Interpreted episodes | Cardiology review and sign-off |
| SMART on FHIR | Launch | In-context Formcloud views | Strip review from inside the chart |
How an integration project runs
Four phases. Most of the time goes into the second one.
Discovery
Your interface team, our integration engineer, and a clinical owner agree what data goes where and who will look at it.
Mapping
Device measurements are mapped to your codes and flowsheet rows. Mappings are versioned files you can review, not a black box.
Testing
We replay recorded device data through your test environment until the flowsheet matches what a clinician expects to see.
Go-live and watch
A supervised first week with daily review, then a monthly check on unmapped or rejected messages.
Standard code systems
Measurements are coded on the way out, so your team is not inventing codes for a heart rate.
| Data | Code system |
|---|---|
| Vital signs | LOINC, using the standard vital signs profile |
| Device types | IEEE 11073 nomenclature with SNOMED CT where your record expects it |
| Units | UCUM |
| Rhythm findings | SNOMED CT, with the original device label preserved |
| Custom codes | Supported, and listed in the mapping file |
Ask for the integration guide
It covers message samples, mapping templates, and the test scripts we use. Your account team can send it, or find it in the developer docs.