When a patient’s health changes after preoperative assessment, the team should document the update, identify whether urgent help is needed, and route relevant information to the appropriate clinical reviewer. The responsible clinicians then determine whether the procedure can proceed, needs further assessment, or should be postponed. Staff should communicate and record the resulting plan.
Preoperative assessment reflects the information available when it was completed. A new illness, medication change, emergency department visit, or change in home support can require the team to revisit that information.
For ambulatory surgery centers (ASCs) and other procedural settings, the challenge is not simply collecting another answer. It is making sure the update reaches someone who can evaluate it before outdated information drives the next step.
A completed questionnaire, a reviewed assessment, and current readiness for surgery are different stages. A reliable workflow keeps those distinctions visible.
Why Post-Assessment Changes Are Common
The interval between assessment and surgery creates opportunities for information to change. Patients may receive treatment elsewhere, develop symptoms, or discover that their transportation arrangements no longer work.
The update may concern clinical risk, practical readiness, or both.
Common categories include:
- Acute illness: A new cough, fever, gastrointestinal illness, or reported infection.
- Medication changes: A new prescription, changed dose, discontinued medicine, or previously unreported supplement.
- Cardiovascular or respiratory symptoms: New concerns that need assessment rather than an assumption that the earlier review still applies.
- Support and access issues: A caregiver becoming unavailable, transportation falling through, or difficulty following preparation instructions.
- New clinical information: Test results, specialist recommendations, or discharge records received after the initial assessment.
Do not expect patients to decide which changes matter for anesthesia. Ask specific questions and provide a clear reporting route.
The operational objective is to make updates easier to identify and review, rather than discovering them only when the patient arrives.
Build Detection Into the Preoperative Timeline
Detection should combine planned contact with a way for patients to report changes whenever they occur.
Schedule a pre-procedure check-in. A focused call, text, or portal message can ask about new symptoms, medication changes, emergency visits, and preparation concerns. A check one to three days before surgery is one possible workflow, not a universal requirement or a replacement for earlier reporting.
Set the timing through the facility’s clinical process and allow for different patient and procedure needs.
Make updating easy. Give patients a clearly identified contact route and explain when it is monitored. Include after-hours instructions. Patients should not have to guess whether to contact the surgeon’s office, the center, or another department.
Prompt staff at handoffs. Include a brief change check at relevant touchpoints. Registration and scheduling staff can identify that something has changed without being expected to interpret its medical significance.
Use available system information carefully. Where external records or alerts are available, assign responsibility for reviewing them. Do not assume that every outside encounter will appear automatically or that an alert has already been assessed.
A scheduled check-in should be a reminder, not an instruction to wait. Patients need to know they can report a change before that contact occurs.
Update Records Without Creating Chart Chaos
A useful update should show what changed, when it changed, who reported it, and what action remains outstanding.
Adding a note is not enough if the working case status still suggests that all review is complete.
Use a consistent update standard:
- Record the change in a designated location. Make it accessible to the team rather than leaving it only in a voicemail or separate worksheet.
- Capture the timing and source. Distinguish patient-reported information from findings documented by an outside clinician.
- Connect supporting records. Include relevant medication information, discharge summaries, test results, or specialist notes when available.
- Identify the review status. Show whether the update is awaiting assessment, requires further information, or has been reviewed.
- Record the decision and communication. Identify the responsible reviewer, outstanding actions, and instructions provided to the patient.
Preserve the original assessment through timestamped updates or version history rather than silently replacing it. The current view should make the latest information and unresolved questions obvious.
This approach also reflects the American Society of Anesthesiologists’ emphasis on accurate documentation and avoiding unnecessary duplication of information already available in the medical record.
“Update received” should not be used as a substitute for “clinically reviewed.”
Define Escalation Protocols Before You Need Them
An escalation protocol should distinguish a possible medical emergency from a clinical review request or a scheduling problem.
Those situations should not enter the same queue with the same response expectations.
Possible emergency symptoms require immediate attention. Chest pain and serious breathing difficulty can be signs of a medical emergency. Instructions should direct patients with emergency symptoms to call 911 or seek emergency care, rather than wait for a portal reply or routine preoperative callback.
For non-emergency updates, the facility’s protocol should answer five practical questions:
- Which changes require clinical review? Define the symptoms, medication updates, outside encounters, and unresolved preparation issues that staff must route for assessment.
- What can nursing address under approved guidance? Identify the limits of standing instructions and when uncertainty requires escalation.
- Who makes the relevant decision? Clarify responsibilities for surgical planning, anesthesia assessment, and scheduling.
- How quickly should someone respond? Set expectations according to urgency and proximity to the procedure, including a backup contact.
- How is the outcome confirmed? Record the decision and identify everyone who needs updated instructions.
The American Society of Anesthesiologists’ preanesthesia standards assign the anesthesiologist responsibility for assessing medical status and developing the anesthesia plan. An administrative “cleared” status should not replace that assessment.
Keep the protocol where staff work. A clear policy is useful only when the person receiving an update can find the next step and reach the responsible reviewer.
Clinical Scenarios and Sensible Responses
The following examples illustrate information collection and escalation, not treatment instructions or automatic cancellation rules.
A new illness does not necessarily mean surgery must be canceled. The responsible clinicians need to assess the circumstances, including the procedure and the patient’s condition.
New respiratory symptoms two days before elective anesthesia.
Record when symptoms began, what the patient reports, and whether they have already sought care. Route the update for appropriate clinical review rather than telling the patient that a cough is either harmless or an automatic cancellation.
Document the resulting instructions and any further information needed.
A patient started a new blood thinner after the original assessment.
Collect the medication name, dose, reason for prescribing, and any instructions already provided. Record the last dose when relevant and known.
Send the information to the responsible clinicians for a coordinated plan. Intake staff should not independently advise stopping, restarting, or changing medication. A complete medication history is important because medicines and supplements can affect anesthesia planning.
A patient reports elevated blood pressure readings during the preoperative call.
Record the reported readings, their timing, associated symptoms, and recent treatment changes for clinical review.
Do not assume anxiety explains the readings or ask administrative staff to determine whether the patient is fit for surgery. The reviewer should assess what follow-up is appropriate.
A patient reports an emergency department visit for abdominal pain after assessment.
Request available discharge information, test results, and follow-up instructions. Identify questions that remain unresolved and route them before the planned procedure.
Ask the clinical reviewer whether the new findings affect preparation, the anesthesia plan, or the procedure itself.
Across these examples, the workflow is consistent: collect relevant information, identify the reviewer, document the response, and communicate the next step.
Coordinate Across Offices, Vendors, and Families
A clinical decision can create several operational tasks.
When a procedure is postponed or its arrangements change, identify who will notify the patient, the surgeon’s office, scheduling staff, and any relevant support teams. Coordinate equipment or vendor arrangements where necessary.
Use a consistent communication structure:
What has changed? Explain the current plan in plain language.
What should the patient do next? Provide the instructions approved by the responsible clinical team.
Who is handling outstanding work? Identify responsibility for records, appointments, or further review.
When should the patient expect another update? Set an appropriate expectation and provide a contact route.
Confirm that the patient received the message rather than treating “sent” as the end of the task.
Use Technology to Support the Protocol, Not Replace Judgment
Digital intake and automated communication can provide ways to request updates and organize information. Their value depends on the review process behind them.
When assessing a workflow, ask:
Can a patient report a change after submitting the original questionnaire? Who receives it? Can the reviewer see the original assessment alongside the update? How are unresolved actions kept visible?
Do not assume that submitting a form automatically updates every clinical system or triggers immediate staff attention. Confirm what the configured workflow actually does.
One Mnet Health supports pre-admission, patient intake, and patient engagement for healthcare providers, including ASCs and hospitals. These services are relevant to organizing the information and communication surrounding preoperative review.
The center still needs to define clinical criteria, review responsibilities, and escalation arrangements.
Technology can help deliver an update to the right place. Qualified clinicians determine what that update means for care.
Train, Drill, and Measure
Test the process with short scenarios involving registration, nursing, scheduling, and anesthesia staff.
For example, walk through what happens when a patient reports a new medication after hours and the primary reviewer is unavailable.
Check whether staff can identify the correct contact, record the update, and determine who owns the next action.
Measure whether the workflow is functioning as intended:
- Documented check-ins: Which cases have the required pre-procedure health update?
- Time to review: How much time passes between a reported change and clinical assessment?
- Outstanding actions: Which cases still need records, clarification, or patient contact?
- Late discoveries: Which relevant changes were first identified on the procedure day?
- Communication problems: Where did patients receive delayed or conflicting instructions?
These measures build on the original workflow’s emphasis on documented checks, response timing, cancellations, and patient feedback.
Review postponements in context. An appropriate clinical decision to delay a procedure should not be treated as a process failure simply because it changes the schedule.
Ask instead whether the information was available earlier, whether it reached the correct reviewer, and whether the patient understood the resulting plan.
Frequently Asked Questions
How close to surgery should we re-check patient health status?
Set the timing through the facility’s clinical process. A focused check one to three days before surgery can be one planned touchpoint, alongside day-of review. Patients should report changes when they happen rather than wait for a scheduled contact. Earlier or additional review may be appropriate.
Who should patients call if they get sick after clearance?
Provide a clearly named contact route in written and digital instructions, including after-hours guidance. Explain who monitors messages and when to expect a response. For possible medical emergencies, patients should call 911 or seek emergency care rather than wait for the preoperative team to reply.
Should every medication change trigger anesthesia review?
Every reported medication change should be documented and routed according to a clinically approved protocol. Not every update needs the same level of review, but administrative staff should not decide its significance independently. Uncertainty and changes outside standing guidance should reach the appropriate clinician.
What if the surgeon and anesthesia disagree about proceeding?
Use the facility’s established clinical escalation process. Clarify the concern, identify the responsible clinical leaders, and document the agreed plan. Scheduling pressure should not resolve a clinical disagreement, and administrative staff should not be asked to choose which medical opinion to follow.
How do we update digital intake without losing the original assessment?
Use timestamped addenda or version history, identify the source of the new information, and distinguish reported changes from reviewed findings. Keep the current status and outstanding actions visible. Where information crosses systems, confirm the handoff rather than assuming every record updated automatically.
Protect Patients With a Clear Change Playbook
The goal is not to predict every change before surgery. It is to provide a reliable response when new information appears.
That response should make four things clear: what changed, who is reviewing it, what decision was made, and what the patient should do next.
Start by examining the gap between initial assessment and procedure day. Identify where updates can be missed, where responsibility is unclear, and where patients receive incomplete instructions.
Then connect patient reporting, documentation, clinical review, and communication into one defined workflow.
Contact One Mnet Health to discuss how Medical Passport improves the preoperative intake process by transforming patient health data into actionable insights and intelligence that support timely clinical review before surgery.