Recording bedside physiological data for ICU research
A bedside monitor displays each value until the next one replaces it on the screen. Kymolog stores each reading the devices send, codes it and links it to the patient's encounter, so a study can use the full series.
Linked to the encounter · LOINC · UCUM · research store on premises or hosted
ICU data linked to the encounter
At 10:20, the pulse oximeter at ICU bed 7 reports an oxygen saturation (SpO₂) of 94 %. The Kymolog™ edge agent codes it with LOINC 59408-5 and the UCUM unit %, names the device and stamps the time. Kymolog then checks which patient occupied bed 7 at 10:20, attaches that patient and links the reading to the ICU encounter.
Heart rate from the monitor and body temperature from the thermometer take the same path. Twelve hours at one bed arrive as three coded series on one encounter: SpO₂ and heart rate every five minutes, temperature every hour. Continuous physiological monitoring is kept as research data at each device's own reporting interval.
Figure 2 as a table
| Series | Code and unit | Device, interval |
|---|---|---|
| SpO₂ | LOINC 59408-5, % | Device/ox-12, every 5 min |
| heart rate | LOINC 8867-4, /min | Device/mon-07, every 5 min |
| body temperature | LOINC 8310-5, Cel | Device/tm-03, hourly |
| marked reading | SpO₂ 94 % at 10:20 | bed 7 at 10:20: p-041, Encounter/e-2207 |
A study dataset with one row per reading
Kymolog turns the coded series into study rows without anyone retyping a value. Each row says when the reading was taken, whose it is and which stay, what was measured, which device took it and which Observation it came from (Fig. 3). Each reading is a FHIR R4 Observation, and FHIR (Fast Healthcare Interoperability Resources) gives every one of those columns a named field.
Rows also carry their review status. A reading a clinician rejected in the review queue stays marked as rejected, so a study can exclude it deliberately. Kymolog keeps each device's own health readings too, such as its battery and its signal, so a gap in a series has the device's own record beside it.
Figure 3 as a table
| Column | At 10:20:00 | Observation field |
|---|---|---|
| time | 10:20:00 | effectiveDateTime |
| subject | p-041 | subject |
| encounter | e-2207 | encounter |
| LOINC | 59408-5 | code |
| value, unit | 94 % | valueQuantity (UCUM) |
| device | ox-12 | device |
| Observation, status | 9b3f, final | the record itself |
Critical care research on your own beds
Public ICU datasets come from other hospitals and other years. With Kymolog on a unit, ICU research can draw on readings from your own beds, coded the same way from the first day. The edge agent reads bedside monitors, pulse oximeters, blood pressure cuffs, thermometers, electrocardiogram (ECG) monitors and continuous glucose monitors (CGMs), and any other device class by configuration.
An ECG monitor's corrected QT interval arrives as LOINC 8636-3 in ms, comparable from one patient to the next. Physiological data collection needs no build per study: a protocol picks the units, device classes and dates it needs. With the research store on premises, the identified series stays under your hospital's own access rules, and each study draws only the fields its approval covers. If we host the research store in our cloud, it only receives de-identified readings.
The EHR side of the same study
Diagnoses, medications and lab results for the same patients live in the EHR. Clinical Extract, which we also build, pulls that EHR data for research. Kymolog covers the device readings, and the two datasets join on the patient and the encounter.
Hospitals that want to share de-identified device data beyond their own researchers can join the data network, a separate add-on service we run.
Discuss a research dataset for your ICU
Name the unit and the device classes on its beds. The demo shows one bed's readings as coded series, then as study rows that each point back to their device. We reply within one business day with times to talk.