Anesthesiology EHR

What should an anesthesiology EHR capture?

An anesthesiology EHR should capture the pre-anesthesia evaluation, a time-stamped intraoperative record fed by physiologic monitors and the anesthesia machine, and the post-anesthesia evaluation, plus the start and stop times, staffing ratios and procedure codes that anesthesia billing needs. Hospitals must keep all three clinical documents under the Medicare Conditions of Participation.

An anesthesia record is unusual among clinical documents because it is written during the procedure, not after it. Drug doses, airway events, fluid totals and vital signs are logged as they happen, and the clinician often has seconds to enter them.

That makes the design problem closer to a cockpit than a chart. Fast entry, automatic capture and clear time stamps matter more than free-text flexibility.

Which documents do hospital rules require?

Hospitals that take Medicare must document three things for every patient who receives anesthesia, each with its own timing rule. The software should know those windows and warn before they close.

• Pre-anesthesia evaluation: completed and documented by a qualified practitioner within 48 hours before surgery or a procedure requiring anesthesia services (42 CFR 482.52(b)(1)).
• Intraoperative anesthesia record: required for each patient (42 CFR 482.52(b)(2)).
• Post-anesthesia evaluation: completed and documented no later than 48 hours after surgery or the procedure (42 CFR 482.52(b)(3)).
• Monitoring standard: the American Society of Anesthesiologists Standards for Basic Anesthetic Monitoring, last amended 15 October 2025, state that the patient's oxygenation, ventilation, circulation and temperature shall be continually evaluated during all anesthetics.

Those rules shape the data model directly. The pre-anesthesia evaluation needs a signed time that can be compared with the procedure start. The intraoperative record needs a value or a documented reason for each of the four monitored areas. The post-anesthesia evaluation needs a task that follows the patient out of recovery, sometimes to an inpatient unit where a different clinician completes it.

The evaluation itself usually records the airway assessment, anesthesia history, allergies, the planned technique and the ASA physical status. Storing physical status as a coded field pays off later, because anesthesia claims can carry the physical status modifiers P1 to P6.

A common failure point is the case that slips a day. If surgery moves, a pre-anesthesia evaluation signed three days earlier no longer meets the 48-hour window, and the system should flag it on the day of surgery rather than leave it for a chart audit.

Ambulatory surgery centers follow a different rule set. Under the ASC Conditions for Coverage at 42 CFR 416.42, a physician or anesthetist must examine the patient immediately before surgery to evaluate the risk of anesthesia, and must evaluate each patient for proper anesthesia recovery before discharge. A system used in both settings needs both rule sets.

How do monitors and anesthesia machines feed the record?

Monitors and machines usually feed the record through a device gateway that converts their output into standard messages. The IHE Device Enterprise Communication (DEC) profile, from IHE's patient care device work now held in its Devices domain, defines that message as an HL7 v2 ORU^R01 using ISO/IEEE 11073-10101 nomenclature for each observation.

• Patient association: the gateway must know which patient is in which room on which device, usually by binding the device to the case at room entry and releasing it at room exit.
• Sampling interval: the record stores values at a configured interval, while the monitor itself may sample far more often, so the case record states what interval was used.
• Validation: values arrive as unvalidated data. Artifacts from a moved probe or a flushed arterial line must be marked by the clinician before they become part of the signed record.
• Clock agreement: the monitor, the gateway and the record must share a time source, or drug doses and vital signs drift apart on the timeline.
• Downtime: when the gateway stops, the clinician needs a manual entry mode that shows clearly which values were typed and which were captured.

Anesthesia machines and infusion pumps add settings and events, not only measurements. A ventilator mode change or an infusion rate change is clinically important, so the integration should capture events as well as periodic values.

The recovery unit needs the same feed. Recovery scores, pain scores and discharge readiness are charted on a tighter schedule than ward care, and the device binding has to follow the patient from the operating room to the recovery bay without a gap.

What billing data does anesthesia time create?

Anesthesia billing combines a base unit value for the procedure with time units derived from documented minutes. Medicare's Claims Processing Manual multiplies base and time units by a locality-specific anesthesia conversion factor, so accurate start and stop times are money as well as documentation.

• Base units: CMS communicates the base unit for each anesthesia code to its contractors in the HCPCS file released each year.
• Time units: for Medicare, reported anesthesia minutes are divided by 15 and rounded to one decimal place.
• Start and stop: anesthesia time starts when the anesthesia practitioner begins to prepare the patient in the operating room or an equivalent area, and ends when the practitioner is no longer in personal attendance.
• Interruptions: blocks of time around an interruption can be added together as long as the practitioner is furnishing continuous anesthesia care within those blocks.
• Modifiers: claims show who did the work and under what supervision, for example AA for an anesthesiologist personally performing, QK for medical direction of two to four concurrent cases, QX and QZ for a CRNA with and without medical direction.

The record should compute anesthesia minutes from explicit start and stop events, store any interruption blocks, and pass both to the billing system. Typing a total into a box hides the evidence an auditor would ask for.

Some codes break the pattern. The Claims Processing Manual says contractors do not recognize time units for CPT 01995 or 01996, so the billing export should report those codes without computed time rather than send minutes the claim cannot use.

Medical direction records

Medical direction is billed only when the anesthesiologist documents specific steps for each case. Under 42 CFR 415.110, the physician performs the pre-anesthetic examination, prescribes the plan, personally participates in the most demanding parts including induction and emergence, ensures qualified staff perform the rest, monitors at frequent intervals, remains physically present and available for emergencies, and provides indicated post-anesthesia care.

The same section limits medical direction to no more than four concurrent anesthesia procedures, and requires the physician alone to document in the record that each step was met. Those two rules map to software in a straightforward way.

• Concurrency counter: track every case each anesthesiologist directs across rooms, and warn before a fifth case would start.
• Attestation points: prompt the directing physician to attest presence at induction and emergence at the moment they happen, with a time stamp.
• Hand-offs: record each change of directing physician or CRNA with a time, because the claim and the modifier depend on who was responsible when.

Build, buy or extend: how should a group choose?

The choice depends on where anesthesia is delivered and which system already holds the surgical record. A hospital department, an ambulatory surgery center and an office-based anesthesia group have different starting points.

• Extend the hospital EHR: fits departments inside a health system whose enterprise EHR offers an anesthesia module. The work is configuration, device gateway setup and billing interfaces.
• Buy a standalone AIMS: fits groups covering several facilities on different EHRs. The integration load is high, with ADT, orders, results and documents flowing to each facility.
• Build a focused system: fits office-based or mobile anesthesia groups whose cases, devices and billing rules are narrower than a hospital's. Scope it to the three required documents, time capture and billing export.
• Billing-only integration: fits groups whose facilities already capture the clinical record. Build a feed of times, staff and codes from each facility to the group's billing system.

Whatever the choice, test it in a simulated case with real devices before go-live. A device gateway that has never seen the facility's monitor models is the riskiest part of the plan.

Where anesthesia record projects fail

• Device binding left to memory: values from the previous patient's monitor land in the next patient's record.
• Unvalidated values signed: monitor artifacts become part of the legal record because nothing forced a review.
• Totals instead of events: anesthesia time is typed as a number, and the start and stop evidence is lost.
• Concurrency tracked on paper: the fifth concurrent case is discovered at billing, not before it starts.
• Post-anesthesia evaluations orphaned: patients transfer before the evaluation, and no task follows them.

How Agnotic can help

Anesthesia software lives at the meeting point of devices, clinical documentation and professional billing. Agnotic Technologies builds those connections for the client: device gateway integrations using IHE DEC and HL7 v2, intraoperative record modules, anesthesia time and concurrency tracking, and billing feeds to the group's revenue cycle system.

For groups working across facilities, Agnotic builds the ADT, order and document interfaces that let one anesthesia record serve several hospital EHRs.

Sources

• 42 CFR 482.52: Condition of participation, anesthesia services
• 42 CFR 415.110: Conditions for payment, medically directed anesthesia services
• ASA: Standards for Basic Anesthetic Monitoring
• CMS Medicare Claims Processing Manual, Chapter 12: Physicians and Nonphysician Practitioners (anesthesia, section 50)
• IHE Devices Technical Framework, Volume 2: Transactions (PCD-01)
• 42 CFR 416.42: ASC condition for coverage, surgical services
• CMS NCCI Policy Manual for Medicare, Chapter 2: Anesthesia Services