Blog

    Pulmonology EHR

    By GauravNovember 4, 202610 mins read
    On this page

    A pulmonology EHR is the record a lung practice uses to order, capture and interpret breathing tests, run its sleep medicine program and keep equipment paperwork ready for payers. Its hardest data does not come from a keyboard. It comes from spirometers, body boxes, sleep recorders and CPAP modems.

    This guide walks through the pulmonary function lab feed, the sleep study and PAP adherence loop, home oxygen qualification, and the build decisions that separate a lung clinic system from a general ambulatory chart.

    What does a pulmonology EHR need to do?

    Building or connecting a pulmonology EHR?

    Agnotic builds pulmonary practice software for the client: PFT device interfaces, sleep study workflows, PAP adherence imports and EHR integration.

    A pulmonology EHR records the lung clinic's visits and also files structured results from pulmonary function equipment, sleep studies and positive airway pressure devices. It must store FEV1, FVC and DLCO as discrete values with the reference equation used, track CPAP adherence windows, and keep the blood gas or oximetry evidence that home oxygen coverage depends on.

    General ambulatory records handle the visit note, the problem list and prescribing well enough. The gaps appear around the pulmonary function lab, the sleep lab and the equipment supplier, which is where a lung practice spends much of its operational effort.

    Those three areas share one trait. The clinical evidence is produced by a machine, interpreted by a physician and then reused by a payer. A record that keeps only a scanned PDF of the result breaks that chain at the first step.

    Which pulmonary function results belong in discrete fields?

    Every value a clinician trends or a payer checks belongs in a discrete field, not only in the PDF report. For spirometry that means FEV1, FVC and the FEV1/FVC ratio, before and after a bronchodilator when one was given, along with the predicted value, the lower limit of normal and the z-score.

    • Spirometry: FEV1, FVC, FEV1/FVC and peak flow, stored per test session with the technician who ran it and a flag for acceptable effort.
    • Lung volumes: total lung capacity, residual volume and functional residual capacity, with the method used, because plethysmography and gas dilution or washout are coded differently.
    • Diffusing capacity: DLCO, plus the hemoglobin value if the lab corrects for it.
    • Exercise testing: walk distance, lowest oxygen saturation and any supplemental oxygen used during the test.
    • Interpretation: the reading physician, the date signed and the impression, kept apart from the machine values so neither overwrites the other.

    The reference equation set matters as much as the numbers. An official American Thoracic Society statement published in 2023 recommends replacing race and ethnicity specific reference equations with a race-neutral average equation such as GLI Global. A record that stores only percent predicted, without naming the equation, cannot be re-read when the lab switches sets.

    Coding follows the same structure. The CMS National Correct Coding Initiative policy manual describes 94010 for spirometry and 94060 for spirometry before and after a bronchodilator, and says only one unit is reported even when several efforts are needed to finish the test. Separate codes cover lung volumes (94726 or 94727, depending on method), diffusing capacity (94729) and pulmonary stress testing (94618).

    How do PFT and sleep systems connect to the chart?

    Most pulmonary function and sleep scoring systems connect through one of three routes, and the lab vendor should confirm in writing which ones its installed version supports. The route decides how much of the result becomes usable data.

    • 1. HL7 v2 results: the test software sends an ORU^R01 message with each measured value in its own OBX segment, ideally coded with LOINC, and the signed report attached or referenced. This is the route that keeps values discrete.
    • 2. File export: the software writes a PDF plus an XML or CSV file to a shared folder, and an interface engine picks it up, parses it and builds the message. It works, but the parser breaks whenever the vendor changes the export layout.
    • 3. Document only: a PDF lands in the chart as an uploaded document. Nothing in it can be trended or checked automatically.

    Orders deserve the same care. When the EHR sends an order message to the lab system, the accession number travels with it and comes back on the result. Without that link, a busy lab ends up matching reports to patients by name and date, which is where wrong-patient filing starts.

    Sleep studies add a second person to the result. The scoring technologist marks events and the sleep physician signs the report, so the record should hold both identities, the study type, the recording date and the apnea-hypopnea index or respiratory disturbance index as discrete values.

    Sleep medicine: from study order to PAP adherence

    The sleep workflow runs from a test order to a therapy decision to proof that the patient is using the device. Medicare coverage rules define each step, so the software can enforce them instead of leaving them to a paper checklist.

    • Test types: CMS National Coverage Determination 240.4.1 covers attended polysomnography in a sleep lab (Type I) and unattended home sleep tests on Type II, III and IV devices, each with minimum channel requirements.
    • Diagnosis threshold: NCD 240.4 covers an initial 12-week CPAP trial for adults with an AHI or RDI of at least 15 events per hour, or 5 to 14 events per hour with documented symptoms or conditions such as excessive daytime sleepiness, hypertension, ischemic heart disease or a history of stroke.
    • Short recordings: when the AHI or RDI comes from less than 2 hours of recorded sleep, NCD 240.4 requires at least the number of events a 2-hour recording would need.
    • Adherence: the DME MAC local coverage determination for positive airway pressure devices (L33718) defines adherence as use for 4 or more hours per night on 70 percent of nights during a consecutive 30-day period in the first three months of use.

    Those rules translate directly into data. The record needs the AHI linked to its source study, a trial start date, nightly usage imported from the device data the supplier shares, and a task that fires before the trial ends so the clinician can document a re-evaluation and the patient's benefit.

    PAP usage data usually reaches the practice through the device maker's cloud portal or a report from the equipment supplier. Both companies may hold ePHI, so the question of which of them is the practice's business associate under 45 CFR 164.502(e) should be settled before any automated import is switched on.

    What does home oxygen qualification require from the record?

    Home oxygen coverage rests on a qualifying test, so the record must hold that test as structured evidence tied to the order. The DME MAC local coverage determination for oxygen and oxygen equipment (L33797) sets the thresholds.

    • Group I at rest: an arterial PO2 at or below 55 mm Hg or an oxygen saturation at or below 88 percent, measured at rest and awake while breathing room air.
    • Exercise and sleep: separate qualifying rules apply to testing during exercise and during sleep, so each test record must say which condition applied.
    • Who tests: qualification testing is done in person by the treating practitioner or another medical professional qualified to perform oximetry, with overnight oximetry handled as its own case.

    In data terms, each oxygen test is an observation with a method (arterial blood gas or pulse oximetry), a condition (rest, exercise or sleep), the oxygen status at the time (room air or a stated flow) and the person who performed it. The order to the supplier should reference that observation, so an auditor can follow the claim back to a single test.

    A common failure point is storing oximetry as a number typed into a progress note. The value is there, but nothing shows the patient was on room air, and the supplier has to call the office to ask.

    Where pulmonology builds go wrong

    • Percent predicted without the equation: values cannot be re-read when the lab moves to race-neutral equations, and trend lines jump on the switch date.
    • Pre and post bronchodilator merged: one row per test hides the response that helps separate reversible from fixed obstruction.
    • PFT reports as images only: spirometry trends, COPD registries and payer audits all need discrete FEV1 and FVC.
    • No accession number on orders: results get matched to patients by name and date, and wrong-patient filing follows.
    • PAP trial dates held only by the supplier: the practice cannot see the adherence window closing until a claim is denied.
    • Oximetry without context: a saturation value with no rest, exercise or sleep condition and no oxygen status fails the qualification check.

    Teams that avoid these problems usually agree the data model for each test before they pick an interface method, then hold the lab vendor to that model during interface testing.

    Should a lung practice buy, configure or build?

    The answer depends on how much of the practice's work runs through its own labs. A practice that sends patients elsewhere for testing can often configure a general ambulatory EHR. One with an in-house PFT and sleep lab needs specialty workflows somewhere in its stack.

    • Configure a general EHR: fits clinic-only practices. Add pulmonary flowsheets, an inbound result interface and oxygen order templates.
    • Buy a specialty system: fits practices with their own PFT and sleep labs. Check that its result interface sends discrete values, not only PDFs.
    • Build modules around the EHR: fits groups with unusual workflows, such as a sleep program run across several sites or a device-data hub feeding more than one record. The EHR stays the system of record and the modules write back through its supported interfaces.

    Certification is a separate question. A practice that reports to Medicare quality programs generally needs certified EHR technology, and the API that 45 CFR 170.315(g)(10) certifies only reads patient and population data. Writing device data back into a certified EHR needs the vendor's own write APIs or an HL7 v2 interface.

    How Agnotic can help

    For a lung practice, most of the engineering sits between the test equipment and the chart. Agnotic Technologies builds that layer for the client: HL7 v2 result interfaces from PFT and sleep systems, parsers for file-based exports, PAP adherence imports, oxygen qualification records and the order links that keep each result on the right patient.

    Agnotic works inside the practice's chosen EHR and its supported interfaces, so the record stays the system of record while the specialty results finally arrive as data.

    Plan a pulmonology EHR integration with Agnotic

    See EHR integration services, or read more lung, device and interface guides in the EHR integration hub.

    Related reading on Agnotic

    Continue with HL7 orders and results, EHR integrations, and other specialty record guides.

    Sources

    Frequently Asked Questions

    Yes, for a clinic-only practice that sends testing elsewhere. Practices with their own PFT or sleep lab usually need specialty flowsheets, a discrete result interface and oxygen documentation added or bought.

    Talk to an engineer about your project

    We build PFT and sleep result interfaces, PAP adherence imports and oxygen qualification records for lung practices on their existing EHR.