New Hampshire - Hospital Regulatory & Mandatory Reporting Guide
New Hampshire — Hospital Regulatory & Mandatory Reporting Guide
New Hampshire is a meaningful hospital reporting jurisdiction because it does not treat catastrophic preventable harm as merely an internal quality matter. Instead, it operates a formal adverse health event reporting system for hospitals and ambulatory surgical centers, requires reporting of National Quality Forum serious reportable events, requires a root cause analysis, requires a corrective action plan, and directs the commissioner to analyze submissions for patterns of systemic failure and publish annual reports by facility. In litigation terms, that means a serious New Hampshire hospital case is rarely just a bedside chronology problem. It is often an NQF event-classification problem, a 15-working-day reporting problem, a root-cause-analysis sufficiency problem, a corrective-action credibility problem, an infection-control and HAI surveillance problem, and in many infection-sensitive matters, an immediate communicable-disease reporting problem at the same time.
That structure matters because New Hampshire’s framework is layered rather than singular. The hospital adverse-event statutes require reporting of specified serious events and follow-up systems analysis. The hospital licensure rules independently require every licensee to report adverse events, maintain infection-control processes, comply with communicable-disease obligations, and run quality assurance and performance improvement systems that specifically review adverse events. Separate healthcare-associated infection rules require hospitals to identify, track, and report specified infections and process measures, often through NHSN-aligned methodology. Separate communicable-disease rules require immediate reporting when a physician, healthcare provider, or—in the absence of a provider—the person in charge of an institution such as a hospital encounters a reportable disease or suspect case.
As a result, strong New Hampshire hospital cases are rarely framed as narrow negligence disputes. They are framed as institutional recognition, reporting, infection-control, surveillance, and systems-integrity cases. Counsel should not ask only what happened to the patient. They should ask whether the hospital recognized the occurrence as reportable, reported it within the statutory timeframe, completed a disciplined causal analysis, implemented a real corrective plan, tracked infection and process measures consistently, complied with immediate communicable-disease duties where applicable, and kept the chart, internal analysis, and regulator-facing narrative aligned.
New Hampshire is also strategically important because the commissioner’s role is expressly systemic rather than purely clerical. The statutory scheme requires the commissioner to analyze adverse event reports, corrective action plans, and root cause analyses to identify patterns of systemic failure and successful correction methods, and to publish annual facility-level reporting summaries. That gives serious New Hampshire hospital cases a strong institutional-liability dimension, particularly where the hospital later attempts to characterize the event as isolated, unavoidable, or purely clinician-specific.
Quick Authority Snapshot
Primary State Regulatory Authority
New Hampshire Department of Health and Human Services, through the commissioner and Health Facilities Administration structures, oversees hospital adverse-event reporting, hospital licensure compliance, healthcare-associated infection reporting, and communicable-disease reporting.
Core Hospital Reporting Framework
New Hampshire’s core adverse-event structure is built through RSA 151:38 and RSA 151:39 and implemented in hospital licensure rules including He-P 802.15. Hospitals must report covered adverse events, complete a root cause analysis, and submit corrective-action information to the state.
Primary Event Model
New Hampshire uses the adverse event / serious reportable event model, centered on National Quality Forum serious reportable events rather than a sentinel-event registry model. The system is still highly consequential because it requires external reporting, systems analysis, and corrective action.
Key Timelines
Covered adverse events must be reported as soon as reasonably and practically possible, but no later than 15 working days after discovery. If the root cause analysis and corrective plan are not complete at that time, the findings and corrective-action materials must otherwise be filed within 60 days of the event.
Hospital Operations Overlay
He-P 802 hospital licensure rules require hospitals to report adverse events, maintain infection-control programs, comply with communicable-disease obligations, and incorporate adverse events into quality assurance and performance improvement review.
Public Health / HAI Overlay
New Hampshire separately requires hospitals to identify, track, and report specified healthcare-associated infections and process measures under RSA 151:33 and He-P 309, while communicable-disease rules require immediate reporting of reportable disease and suspect cases under He-P 301.03.
Attorney Takeaway
In New Hampshire, case value often turns on whether the hospital recognized the event as reportable, filed the initial report on time, completed a disciplined root cause analysis, implemented a credible corrective action plan, tracked infection and process metrics accurately, made required public-health reports promptly, and maintained one stable institutional narrative across all of those layers.
Statutory & Regulatory Architecture
RSA 151:38 — Hospitals and Ambulatory Surgical Centers Required to Report Adverse Events
RSA 151:38 is the center of New Hampshire’s adverse-event reporting framework. It requires hospitals and ambulatory surgical centers to report covered adverse healthcare events to the commissioner as soon as reasonably and practically possible, but no later than 15 working days after discovery. The report identifies the facility but excludes identifying information for individual professionals, employees, and patients. This matters because New Hampshire treats certain major preventable harms as formal state-reportable quality and safety events, not merely internal incident-review matters.
National Quality Forum Event Incorporation
New Hampshire does not build its list from a static state-only event schedule. Instead, RSA 151:38 expressly incorporates serious reportable events and specifications published and periodically amended by the National Quality Forum. That is strategically important because event classification in New Hampshire is tied to a recognized national patient-safety framework. In litigation, that means the first battle is often whether the occurrence fit NQF serious reportable event logic and whether the hospital recognized that status when it should have.
Additional Bloodborne Pathogen Exposure Category
New Hampshire expands beyond the NQF framework by expressly requiring reporting of patient exposure to a non-aerosolized bloodborne pathogen caused by a healthcare worker’s intentional unsafe act. The statute and rule define this in terms of intentional or reckless behavior, objective unreasonableness, and absence of extenuating circumstances. This is important because it creates a separate state-reportable pathway for severe intentional or recklessly unsafe infectious exposure conduct even if the event is argued not to fit a classic NQF category.
Fifteen-Working-Day Initial Report
The 15-working-day reporting deadline is one of the most important timing levers in New Hampshire litigation. It creates an objective benchmark for institutional recognition. The question is not merely when the patient was injured. The more important question is when the hospital knew enough to treat the occurrence as a reportable adverse event and whether the state-facing reporting clock began to run materially earlier than the facility later claims.
RSA 151:38, II — Mandatory Root Cause Analysis and Corrective Action
New Hampshire does not stop at event notice. After an adverse healthcare event, the facility must conduct a root cause analysis and implement a corrective action plan to carry out the findings of that analysis, or report reasons for not taking corrective action. This is major institutional-liability architecture because the state expects the hospital to engage in causal systems learning rather than mere retrospective explanation.
Sixty-Day Findings / Corrective Action Deadline
If the root cause analysis and corrective plan are complete at the time of the initial report, they are included then. Otherwise, the findings of the root cause analysis and the corrective action plan must be filed with the commissioner within 60 days of the event. That means New Hampshire creates not one timeline, but two: an early event-recognition/reporting timeline and a later formal systems-analysis / remediation timeline. Strong cases often reveal that the hospital met neither in a coherent way.
Confidentiality of Submitted Materials
RSA 151:38 provides that information and data made available to the department under the adverse-event section are confidential and exempt from public access. That does not make the framework less significant in litigation. It changes the evidentiary pressure points. Counsel still examine event timing, internal communications, policy revisions, implementation conduct, education or retraining, chart consistency, and whether the institution’s later testimony matches what a disciplined root cause analysis should have identified.
RSA 151:39 — Commissioner’s Duties and Responsibilities
RSA 151:39 makes clear that New Hampshire’s reporting system is designed to facilitate quality improvement and is not structured merely as a punitive reporting mechanism. Yet the statute is still highly useful in litigation because it requires more than passive receipt of reports. The reporting system must include mandatory reporting, mandatory root cause analysis and corrective action planning, state analysis of reported information to identify patterns of systemic failure, sanctions for noncompliance, and communication to facilities, purchasers, and the public to maximize safety improvement.
Systemic Failure Analysis Is Built Into the Statute
One of the most important aspects of RSA 151:39 is that the commissioner must analyze adverse event reports, corrective action plans, and root cause analyses to determine patterns of systemic failure and successful methods to correct them. That is crucial because New Hampshire’s framework is expressly institutional. It is not limited to whether one clinician erred. It asks whether the facility’s systems reveal recurring weaknesses and whether corrective learning actually occurred.
Annual Reporting by Facility
The commissioner must publish an annual report describing, by facility, adverse events reported and outlining aggregate corrective action plans and root cause findings. This public-reporting component has major litigation value because it confirms that the state treats event reporting as a facility-level accountability system, not a hidden internal exercise. It also strengthens discovery themes involving repeat vulnerability, pattern recognition, and institutional credibility.
He-P 802.14 — Duties and Responsibilities of All Hospital Licensees
The hospital licensure rules independently reinforce the adverse-event structure. He-P 802.14 requires licensees to comply with relevant federal, state, and local law, and specifically requires them to report all adverse events to the department and submit additional information when required. It also requires compliance with communicable-disease rules and allows the department to inspect the premises and services to assess compliance. This creates a licensure-based overlay to the adverse-event statutes.
He-P 802.15 — Adverse Event Reporting Rule
He-P 802.15 operationalizes RSA 151:38 for hospitals. It defines reportable adverse events to include NQF serious reportable events and the intentional unsafe bloodborne-pathogen exposure category. It requires an initial report within 15 working days after discovery if the licensee suspects an adverse event occurred, and it requires a 60-day follow-up submission including the type of harm, contributing factors, and a corrective action plan specifying planned actions, responsible parties, implementation timing, and evaluation measures.
Contributing Factors and Measurement Expectations
New Hampshire’s rule is especially useful because the 60-day submission must address contributing factors and explain how corrective action will be measured. That means the hospital is expected to move beyond outcome acknowledgment and into causation, responsibility, implementation, and measurable improvement. In litigation, weak or generic corrective language strongly suggests that the institution did not fully understand or seriously address the event.
Receiving-Hospital Notice Requirement
He-P 802.15 also contains an overlooked but strategically important provision: if a licensee suspects it received a patient from a sending hospital who was subject to an adverse event, the receiving administrator or designee must notify the sending hospital’s administrator or designee and the department. This matters in transfer cases because the hospital that originated the event cannot easily avoid reportability by exporting the patient before the full gravity of the harm becomes undeniable.
He-P 802.22 — Infection Control
He-P 802.22 requires every hospital to develop and implement an infection-control program that educates and provides procedures for the prevention, control, and investigation of infectious and communicable diseases. It also requires policies for staff reporting, communicable-disease compliance, and reporting of infections and process measures required by RSA 151:33 and He-P 309. This matters because severe infection cases in New Hampshire are not just bedside treatment disputes; they are frequently hospital infection-program integrity disputes.
He-P 802.23 — QAPI / Quality Assurance and Performance Improvement
New Hampshire hospital QAPI rules require review and improvement activity in areas such as infection surveillance, morbidity, mortality, environmental safety, and adverse events in accordance with He-P 802.15. That is a major litigation multiplier because it means adverse events and infection surveillance are not isolated compliance silos. They are expected to be absorbed into the hospital’s formal quality system.
RSA 151:33 and He-P 309 — Healthcare-Associated Infection Reporting
New Hampshire separately requires hospitals to maintain a program capable of identifying and tracking infections and to report specified infections and process measures. The statutory framework requires tracking of infectious agents or toxins, location of infection, and relevant diagnoses and procedures. The rule framework requires reporting of central line-related bloodstream infections, catheter-associated urinary tract infections, surgical wound infections, and specified process measures such as central-line insertion adherence, surgical antimicrobial prophylaxis, influenza vaccination rates, and antimicrobial use data if available.
NHSN and Quarterly / Annual HAI Timing Structure
The HAI reporting rules are not abstract. They are operational and time-bound. Hospitals must report certain CAUTI and CDI data quarterly through NHSN within 60 days of the close of each quarter, report specified surgical site infection data using NHSN methodology, and report certain annual measures such as antimicrobial use and surgical antimicrobial prophylaxis by April 30 for the prior year if available. That gives infection-sensitive cases a second regulatory chronology separate from the adverse-event timeline.
Communicable Disease Reporting — He-P 301.03
New Hampshire’s communicable-disease rules create an even faster public-health timeline. Any physician or other healthcare provider who assesses, diagnoses, or treats a person believed to be a case or suspect case of a reportable disease must immediately report the matter to the department. If no provider is in attendance, the person in charge of the institution—including a hospital—must report immediately. This is critical in sepsis, meningitis, measles, pertussis, invasive organism, cluster, exposure, or outbreak-sensitive cases.
Distributed Yet Layered Reporting Architecture
The most important structural point in New Hampshire is that a single event may implicate multiple institutional pathways at once: adverse-event reporting under RSA 151:38 and He-P 802.15, root cause analysis and corrective planning, QAPI review, infection-control obligations under He-P 802.22, healthcare-associated infection surveillance and NHSN-aligned reporting under RSA 151:33 and He-P 309, and immediate communicable-disease reporting under He-P 301. Strong counsel do not ask whether the event was documented. They ask whether every applicable institutional pathway activated on time and stayed internally consistent.
High-Value Litigation Patterns in New Hampshire
Wrong-Site, Wrong-Patient, and Retained Foreign Object Cases
These are among the strongest New Hampshire hospital matters because they fit classic National Quality Forum serious reportable event logic and therefore align naturally with RSA 151:38 reporting obligations. These are not merely technical malpractice disputes. They are event-classification, timeliness, systems-analysis, and corrective-action cases. The strongest theories ask whether the hospital recognized the event immediately, reported it within 15 working days, and produced a real root cause analysis with visible corrective implementation.
Failure to Rescue / Delayed Recognition Cases
Failure-to-rescue cases are especially strong in New Hampshire because they often reveal the exact moment when patient deterioration crossed from difficult care into reportable institutional failure. Missed sepsis, delayed escalation after post-operative decline, missed hemorrhage, monitor failure, delay in response to neurological change, and delayed physician notification often become more powerful where the event sequence suggests the hospital should have recognized a reportable serious adverse event well before its later narrative admits.
Hospital-Acquired Infection / Device-Associated Infection Cases
Infection cases can be especially valuable in New Hampshire because they may implicate adverse-event reporting, infection-control program requirements, HAI tracking and reporting requirements, NHSN-based submission obligations, and immediate communicable-disease reporting where applicable. CLABSI, CAUTI, surgical site infection, contamination drift, isolation failure, cluster formation, delayed diagnosis, and inconsistent infection-prevention documentation can transform one patient’s injury into a broader systems-integrity case.
Medication Catastrophe and Infusion Error Cases
Catastrophic medication events, route errors, high-alert medication failures, infusion pump mismanagement, anticoagulant injuries, and delayed recognition of medication harm often carry significant New Hampshire institutional value because they expose recognition, reporting, causal analysis, monitoring, and corrective-plan weaknesses. These cases become much more dangerous when the hospital treats the event as a bedside charting issue instead of a reportable adverse event with required systems review.
Transfusion / Bloodborne Exposure / Unsafe Conduct Cases
New Hampshire’s explicit reporting requirement for exposure to non-aerosolized bloodborne pathogens caused by intentional unsafe acts gives certain exposure cases unusual regulatory force. Where a patient suffers infectious exposure traceable to reckless or intentional staff conduct, the event can be framed not only as negligence or battery-adjacent misconduct, but as a specifically reportable adverse event under state law.
Falls with Catastrophic Harm
Severe fall cases remain important in New Hampshire because they often reveal missed risk classification, inadequate supervision, toileting delay, unsafe transfer practices, post-fall reassessment failure, and documentation instability. The key question is not merely whether the patient fell. It is whether the seriousness of the event triggered the hospital’s formal adverse-event and systems-review obligations and whether the institution responded as a regulated facility rather than as a chart-defensive actor.
Documentation-Integrity and Narrative-Stability Cases
New Hampshire cases gain force rapidly when the chronology becomes unstable. Missing recognition notes, altered timing, inconsistent physician and nursing narratives, infection-control records that do not match the bedside chart, or follow-up corrective-action themes inconsistent with the actual record all suggest that the institution lacked one coherent account of what occurred. Once that happens, the case becomes less about medical complexity and more about institutional reliability.
Timeline Forensics — Advanced Reconstruction of New Hampshire Institutional Response
New Hampshire hospital cases should be reconstructed across at least seven interacting timelines: the bedside clinical timeline, the event-classification timeline, the 15-working-day adverse-event reporting timeline, the root-cause-analysis timeline, the 60-day corrective-action timeline, the healthcare-associated infection / NHSN timeline, and the immediate communicable-disease reporting timeline. Cases become significantly more dangerous when those timelines diverge.
Phase 1 — Clinical Recognition
The first question is when the hospital had enough information to know that the matter had crossed beyond ordinary treatment complexity into serious patient harm or serious safety-event territory. This may arise from wrong-site procedure, retained foreign object, sudden catastrophic deterioration, major medication injury, severe infection, unsafe bloodborne exposure, or another occurrence suggesting major preventable harm.
Phase 2 — Reportable Event Classification
The next issue is whether the hospital classified the occurrence correctly under New Hampshire’s adverse-event framework. Did the event fit NQF serious reportable event specifications? Did it fall within the bloodborne-pathogen exposure category? Was it treated internally as reportable when the facts first supported that conclusion, or did the hospital narrow the event description to preserve the appearance of routine complication rather than reportable occurrence?
Phase 3 — Fifteen-Working-Day Initial Report
Once the event was or should have been recognized as reportable, did the hospital send the initial report within 15 working days after discovery? This phase should be examined with precision. The chart, leadership emails, risk-management notes, transfer records, operative dictation, and infection-prevention chronology may reveal that the hospital knew much earlier than the reporting date suggests.
Phase 4 — Root Cause Analysis Development
The next stage is whether the hospital performed the root cause analysis that New Hampshire law requires. A serious case should be tested for whether the analysis actually identified causation pathways, contributing factors, communication failures, supervision problems, process breakdown, equipment or environmental issues, and escalation failure—or whether it simply generated a sanitized explanation insufficient to support real institutional learning.
Phase 5 — Sixty-Day Corrective Action / Findings Submission
If the root cause analysis and corrective plan were not included in the initial report, they had to be filed within 60 days of the event. The next question is whether the follow-up submission was timely, specific, and operationally meaningful. Did it identify responsible persons, implementation dates, measurable outcomes, and monitoring expectations? Or did it function as a paper exercise disconnected from actual operational change?
Phase 6 — HAI / Surveillance Comparison
In infection-sensitive cases, counsel should separately compare the bedside chronology with HAI and NHSN-aligned conduct. Did the hospital identify, track, and report the event consistently as a CLABSI, CAUTI, SSI, CDI issue, or another trackable infection problem? Did the surveillance narrative align with the chart? New Hampshire cases become especially dangerous when bedside facts and surveillance conduct diverge.
Phase 7 — Immediate Communicable-Disease Reporting Comparison
Where the facts involve a reportable disease or suspect case, the communicable-disease timeline must be examined independently. New Hampshire requires immediate reporting by providers and, in some circumstances, by the institution itself. Cases become more dangerous when the chart reflects concern for a reportable disease, cluster, or suspect case but the public-health reporting chronology is delayed, absent, or inconsistent.
Phase 8 — Narrative Stability Through Litigation
The final issue is whether the hospital’s story remains stable from charting to event classification to initial report to root cause analysis to corrective-action narrative to HAI surveillance to public-health reporting to deposition testimony. New Hampshire cases gain value rapidly when the institution presents different versions of the same event at different stages. Once that happens, the case becomes less about clinical judgment and more about whether the hospital can provide one reliable institutional account.
Federal Overlay — How CMS Standards Amplify New Hampshire Exposure
New Hampshire’s state structure is already substantial, but the strongest hospital matters usually become significantly more dangerous when the same facts also implicate federal Conditions of Participation. The best New Hampshire cases are often those in which the same occurrence looks deficient clinically, deficient under adverse-event law, deficient under infection-control and surveillance rules, and deficient under federal hospital participation standards.
Hospital Operations and Participation Standards
Serious New Hampshire hospital events often overlap with federal expectations for patient rights, nursing services, medical records, discharge planning, quality assessment and performance improvement, and infection prevention and control. Once a case is framed simultaneously as a New Hampshire adverse-event problem and a federal operational problem, the defense loses room to describe the dispute as an isolated bedside disagreement.
Root Cause Analysis as Systems Evidence
New Hampshire’s statutory requirement for root cause analysis naturally strengthens federal quality-system themes. A hospital that must complete a root cause analysis under state law but cannot show disciplined learning, implementation, and measurement after a severe preventable event becomes more vulnerable to broader institutional-failure arguments under both state and federal frameworks.
Infection Prevention and Surveillance Convergence
Infection cases are especially significant in New Hampshire because the state separately requires infection-control programming, healthcare-associated infection reporting, and immediate communicable-disease reporting where applicable. When a hospital misses an outbreak signal, fails to isolate properly, underreports an infection, or produces conflicting surveillance data, the same facts may support both state and federal theories of institutional failure.
Medical Records and Documentation Integrity
New Hampshire’s reporting and root-cause framework also strengthens documentation-based theories. Incomplete charting, fractured chronology, delayed recognition entries, and records that do not support the hospital’s event-reporting narrative or corrective-action logic become more than impeachment material. They become objective evidence that the hospital’s safety and quality systems were not functioning coherently.
Survey, Inspection, and Administrative Leverage
The licensure rules authorize inspection and enforcement, and New Hampshire assigns specific fines for failure to report adverse events and failure to report infections and process measures. That matters because once a serious case is framed through state reporting duties, systems review, infection-control obligations, and federal participation standards, the defense has less room to reduce the matter to hindsight disagreement over medical judgment.
Litigation Implications — Advanced Institutional Liability Analysis
New Hampshire hospital litigation should not be approached as a simple negligence problem. It should be approached as a multi-document, multi-timeline, institution-level credibility problem. The most effective theories usually show that the outcome was not merely unfortunate, but that the hospital’s own reporting and surveillance structure exposed deeper organizational weakness.
Misclassification and Underreporting
One of the strongest New Hampshire liability themes is that the hospital failed to classify the event at the proper level of seriousness. This may appear as delayed recognition that the occurrence fit NQF serious reportable event logic, narrowing of a catastrophic infection event to routine complication language, or refusal to acknowledge that the event triggered state reporting at all. In deposition and motion practice, the key issue becomes whether the hospital recognized the event’s actual significance when it occurred or later attempted to minimize it.
Superficial Root Cause Analysis
Because New Hampshire affirmatively requires a root cause analysis, the quality of that analysis can become central to liability framing. A superficial analysis, weak contributing-factor narrative, generic action item list, or failure to identify measurable correction themes suggests that the institution did not truly understand the event or did not seriously address it once recognized.
Documentation Integrity as a Liability Multiplier
In New Hampshire, documentation inconsistencies can sharply increase case value. When bedside notes, operative records, physician entries, infection-prevention chronology, HAI reporting conduct, and the hospital’s root cause narrative do not align, the case quickly stops being about whose expert sounds better and starts becoming about why the institution told different versions of the same event at different stages.
Expansion from Individual Fault to Institutional Fault
A provider-focused case can become an institutional case very quickly in New Hampshire. The reasons are predictable: the adverse-event statutes create an external accountability pathway; root cause requirements invite systems scrutiny; HAI reporting widens infection-sensitive cases; communicable-disease rules can create an immediate public-health timeline; and QAPI and federal overlay reinforce the broader operational-failure narrative. This shift often materially changes valuation because institutional-failure theories are more durable than provider-only negligence theories.
Pattern Evidence and Repeat Vulnerability
New Hampshire’s annual reporting and systemic-analysis structure makes it easier to ask whether the event was truly isolated. Even where internal root cause materials are protected, counsel can examine repeat wrong-site concerns, recurring infection-control drift, repeat medication events, repeated fall-related severe injuries, recurring communication failures, and broader patient-safety system weakness suggesting tolerated institutional vulnerability.
Settlement and Trial Impact
A New Hampshire case with weak event-classification logic, late reporting, shallow systems analysis, infection-reporting concerns, or unstable charting will usually carry greater settlement pressure than a similar bedside-only negligence case. At trial, the narrative is stronger: the hospital did not merely make an error; it failed to recognize, report, analyze, correct, document, and account for that error in the manner New Hampshire law expects.
Attorney Application
For Plaintiff Counsel
- Determine whether the occurrence fit New Hampshire’s adverse-event framework, including NQF serious reportable event criteria or the bloodborne-pathogen unsafe-act category.
- Map the bedside chronology against the 15-working-day initial-report deadline and the 60-day root-cause / corrective-action deadline.
- Press on whether the event was under-classified, softened, or incompletely described to avoid state significance.
- Use the root cause analysis requirement to widen the case from bedside care into systems response, communication failure, supervision, escalation, and institutional credibility.
- Where infection issues exist, compare the chart and laboratory chronology to HAI reporting duties under RSA 151:33 and He-P 309.
- Where reportable disease or suspect disease issues exist, test whether immediate communicable-disease reporting occurred under He-P 301.03.
- Develop inconsistency themes aggressively where the chart, infection-prevention records, event report, corrective-action narrative, and later testimony do not align.
For Defense Counsel
- Build a disciplined chronology showing when the hospital recognized the event and how the event moved through New Hampshire’s adverse-event and corrective-action framework.
- Demonstrate coherent event classification, timely reporting, and alignment between charting, root cause findings, corrective action, infection-control conduct, and any public-health reporting narrative.
- Address infection, medication, procedural, transfer, and communicable-disease dimensions directly where they exist rather than leaving them implicit.
- Show that the corrective-action work was real, timely, multidisciplinary, and measurable rather than paper compliance after the fact.
- Stabilize the institutional narrative before discovery fractures credibility across charting, reporting, surveillance, and quality-review layers.
When to Engage Lexcura Summit
New Hampshire hospital matters often justify early clinical-regulatory review because the strongest liability themes usually emerge from the interaction between the chart, NQF serious reportable event logic, the 15-working-day reporting deadline, the mandatory root cause analysis, the 60-day corrective-action submission, infection-control obligations, healthcare-associated infection tracking, and immediate communicable-disease reporting duties. Lexcura Summit is typically engaged when counsel needs more than a chronology and requires disciplined analysis of causation, escalation failure, systems exposure, and reporting integrity.
Engage Early When the Case Involves:
- Unexpected death, severe neurological injury, or major deterioration with unclear adverse-event reporting history
- Possible NQF serious reportable event requiring state report within 15 working days
- Wrong-site surgery, wrong-patient procedure, retained foreign object, or major procedural error
- Failure to rescue, sepsis, post-operative decline, delayed escalation, or monitoring failure
- Medication, infusion, anticoagulant, oxygen, or invasive-treatment error with catastrophic outcome
- Hospital-acquired infection, device-associated infection, outbreak concern, contamination issue, or HAI reporting implications
- Reportable disease, suspect disease, or public-health-sensitive event with uncertain immediate reporting conduct
- Documentation inconsistency, unstable event chronology, or weak corrective-action narrative
- Potential institutional liability extending beyond one provider or one unit
What Lexcura Summit Delivers
- Litigation-ready medical chronologies with event-sequence precision
- Standards-of-care and escalation analysis tied to New Hampshire adverse-event, infection-control, HAI, and public-health duties
- Institutional exposure mapping across event classification, reporting timing, root-cause quality, corrective-action credibility, documentation integrity, surveillance conduct, and systems performance
- Physiological causation analysis in deterioration, infection, and rescue-failure cases
- Strategic support for deposition, mediation, discovery planning, and expert preparation
Records may be submitted through the HIPAA-secure intake portal for preliminary review. Lexcura Summit then issues a letter of engagement outlining scope and cost. Upon confirmation and upfront payment, analysis begins and the completed work product is returned within 7 days.
Closing Authority Statement
New Hampshire hospital liability is defined not solely by the clinical outcome, but by the institution’s ability to recognize, classify, report, investigate, correct, track, and document serious preventable harm within a structured adverse-event and patient-safety framework. Through RSA 151:38, which requires reporting of adverse events and mandates root cause analysis and corrective action; RSA 151:39, which establishes a statewide reporting system designed to identify systemic failure patterns and publish annual facility-level reporting information; He-P 802, which requires hospital licensees to report adverse events, maintain infection-control programs, and integrate adverse events into quality systems; RSA 151:33 and He-P 309, which require the identification, tracking, and reporting of healthcare-associated infections and process measures; and He-P 301.03, which requires immediate reporting of reportable disease and suspect cases, New Hampshire imposes a layered accountability model that evaluates not only what happened at the bedside, but how the hospital translated that occurrence into institutional action.
The analysis therefore begins with clinical reality. Where the medical record reflects wrong-site procedure, retained foreign object, severe infection, device-associated infection, catastrophic deterioration, major medication harm, unsafe bloodborne exposure, delayed rescue, cluster-sensitive illness, or another event suggesting serious preventable harm, the hospital is expected to recognize the significance of that occurrence in real time. When recognition is delayed, incomplete, or internally fragmented, institutional accountability begins from a weakened position.
From that point, the inquiry advances to reporting. New Hampshire does not ask only whether the hospital eventually documented the event. It requires the occurrence to be reported as soon as reasonably and practically possible and no later than 15 working days after discovery. Where the hospital delays classification, narrows the event description, treats a qualifying occurrence as routine complication, or fails to appreciate that the event is reportable under the NQF framework, the issue is no longer limited to clinical care. It becomes a question of whether the institution accurately recognized and managed the event at all.
The next layer examines investigation and correction. New Hampshire does not stop at report submission. It requires a formal root cause analysis and a corrective action plan, or a reported explanation for not taking corrective action. If those materials are not complete at the time of the initial report, they must be filed within 60 days of the event. When the institution’s causal story shifts, contributing factors are ignored, implementation steps are vague, measurement plans are absent, or the corrective narrative does not match the chart, liability expands beyond one treatment decision and into the adequacy of the hospital’s systems themselves.
The analysis then converges on infection control, surveillance, and public health. New Hampshire separately requires hospitals to maintain infection-control programs, identify and track specified healthcare-associated infections and process measures, report them on defined schedules, and immediately report communicable disease or suspect disease in appropriate circumstances. The most consequential New Hampshire cases are therefore those in which the hospital’s adverse-event narrative, infection-prevention record, surveillance submissions, communicable-disease conduct, and bedside chart do not align. When the institution tells one story clinically and another through its regulatory behavior, the discrepancy becomes more than a documentation problem — it becomes evidence that the hospital cannot present one coherent and reliable account of what occurred.
This progression — recognition, classification, initial reporting, root cause analysis, corrective action, infection-control comparison, surveillance comparison, communicable-disease comparison, and narrative integrity — creates a compounding framework of liability. Delayed recognition destabilizes classification. Weak classification undermines reporting. Deficient reporting weakens systems response. Superficial root cause analysis compromises correction. Inconsistent infection and public-health conduct then amplifies exposure at every later stage of litigation.
New Hampshire’s structure is designed to expose precisely this kind of compounding institutional failure. It does not ask only whether harm occurred. It asks whether the hospital’s systems functioned with sufficient discipline to recognize, report, analyze, correct, and account for serious safety failures.
Judicial Framing:
Where a hospital fails to timely recognize a reportable adverse event, delays or narrows its reporting, provides root-cause or corrective-action narratives inconsistent with the chart, neglects related infection-reporting or communicable-disease obligations, and advances testimony that cannot be reconciled with its own regulatory conduct, the resulting harm is not attributable to isolated bedside judgment alone — it is attributable to institutional failure across multiple regulatory and operational layers.
Definitive Conclusion:
The most compelling New Hampshire hospital cases establish that liability is not created by a single adverse event, but by the institution’s cumulative failure to recognize, classify, report, investigate, correct, track, document, and accurately account for that event. In these matters, the central issue is not whether an error occurred, but whether the hospital’s systems functioned with sufficient integrity to respond when it did. Where
::contentReference[oaicite:1]{index=1}
they did not, liability becomes both foreseeable and difficult to defend.