What the Note Says Is What the Claim Says: Tracing Opioid Use Disorder Documentation Through Coding to Payment for an Emergency Buprenorphine Program
[Student Name]
University of Phoenix
NSG/544: Evaluation and Application of Information
Week 2 Assignment
[Instructor Name]
[Date]
The hospital, its program and all figures are a composite written for a model paper.
In Week 1, data on rising overdose visits and evidence on emergency department-initiated buprenorphine supported a strategic decision to start a program at our community hospital. The program was approved on the condition that it be financially sustainable. That condition turns attention to a second use of data: reimbursement. This paper traces how clinical documentation becomes payment and what happens when documentation falls short.
The Path From Note to Payment
Payment for a hospital visit depends on data that pass through several hands. A clinician documents the visit. A coder, reading that documentation, assigns diagnosis codes from ICD-10-CM and procedure or service codes. Billing assembles the codes into a claim with charges. The payer applies its rules to the codes and pays. At every step, the payer sees only what the codes say, and the codes can say only what the documentation supports. Official coding guidelines direct coders to assign codes based on the provider's documentation, not on assumptions (Centers for Medicare & Medicaid Services & National Center for Health Statistics, 2024). A clinician who does not write down the severity of a disorder has, in effect, told the payer the disorder was unspecified.
A Worked Example
A 34-year-old man comes to the emergency department in opioid withdrawal after running out of heroin. He is assessed with a withdrawal scale, started on buprenorphine after moderate withdrawal is confirmed, observed, given a prescription and naloxone kit and referred to the bridge clinic. The physician's note, as first written, says "Opioid withdrawal. Started Suboxone. Refer to clinic."
Coded from that note, the diagnosis is opioid dependence with withdrawal, unspecified severity codes being unavailable for dependence, but the note does not document the severity of use disorder under current criteria or the associated conditions. A more complete note, "Severe opioid use disorder with moderate withdrawal, COWS 15; heroin injected daily; buprenorphine-naloxone 8 mg given with symptom relief; naloxone kit and teaching provided; bridge clinic appointment in 48 hours," allows the coder to assign codes that reflect severity and withdrawal, supports the medical necessity of the observation time and documents the counseling and naloxone teaching.
Why Specificity Matters Financially
Specific documentation affects payment in several ways. The emergency department visit level depends on the complexity of the problem and the work documented; a note showing assessment with a validated scale, a treatment decision, prescription management and arrangement of follow-up supports a higher level than a three-line note. Observation time must be documented to be billed. And payers use diagnosis codes to decide whether services, such as the bridge clinic follow-up, are covered. D'Onofrio et al. (2015) described an emergency department protocol that included assessment, buprenorphine initiation and arranged follow-up; documenting each of those elements is also what makes them billable.
An Audit of the First Three Months
The program's first three months included 86 visits in which buprenorphine was started. An audit compared documentation with coding and billing. In 39 visits, 45%, the severity of opioid use disorder was not documented. In 28, the withdrawal scale score was recorded in the nursing flowsheet but not referenced in the physician note, so the coder did not use it. In 21, observation start and end times were missing, so observation could not be billed. And in 12, naloxone teaching was documented only in a nursing note that the coder did not review.
The Financial Effect
The revenue integrity department estimated that incomplete documentation in the audit sample reduced expected payment by about $27,000 over three months, mostly from lower visit levels and unbilled observation. The figure is modest for a hospital but large for a new program whose sustainability was a condition of approval.
The Payer's View
Payers look at claims in bulk. A payer reviewing many emergency visits for opioid withdrawal coded without severity, with minimal documented work, will see a low-complexity service and pay accordingly, and may question whether bridge clinic visits that follow are necessary. Claims that show severe disorder, a validated assessment, an initiation decision and arranged follow-up tell a coherent story that supports payment for each step. The program's financial sustainability, a condition of its approval, depends on that story being told accurately in the data.
Coders as Partners
The audit was done jointly with two coders from the health information department, who explained which phrases in a note they can and cannot use. Their input shaped the new template: for example, a withdrawal score in the flowsheet cannot be coded from unless the provider references it in the note, so the template pulls the score into the note automatically.
Why Nursing Data Matter Here
Much of the missing documentation existed in nursing data: withdrawal scores, observation times and teaching. The problem was not that nurses failed to document but that nursing data did not flow into the note the coder reads. This is a data design problem as much as a documentation problem.
Confidentiality of Substance Use Disorder Data
Substance use disorder data carry extra protections. Records created by federally assisted programs that hold themselves out as providing substance use disorder treatment are governed by a federal confidentiality regulation that restricts their use and disclosure (Confidentiality of Substance Use Disorder Patient Records, 2024). Recent revisions aligned many of its rules more closely with HIPAA, including allowing use for treatment, payment and health care operations with a single consent, but they still limit use of the records in legal proceedings against patients. The hospital's compliance office determined which program records fall under the regulation, and the billing workflow was adjusted so that claims include only the information payers need.
Changes to Documentation and Data Flow
Three changes followed the audit. A structured note template for buprenorphine initiation prompts the clinician for severity, withdrawal score, dose, response, naloxone and follow-up, and pulls the latest withdrawal score from the flowsheet automatically. Observation start and end times are captured by the nurse with buttons in the record and flow into the note. Naloxone teaching documented by nurses is added to the visit summary coders review. A repeat audit is planned after three months.
Measuring the Change
The repeat audit will use the same four checks, severity, withdrawal score in the note, observation times and naloxone teaching, on a new sample, so any improvement can be compared directly with the first audit.
Conclusion
Following one visit from note to payment showed that the payer sees only what the codes say and the codes say only what documentation supports. An audit found that nearly half of the program's visits lacked documented severity and many lacked observation times, reducing payment. Much of the missing information existed in nursing data that did not reach the note. Structured templates and data flow from nursing documentation will make the record support accurate payment, within the confidentiality rules that protect these patients.
References
Centers for Medicare & Medicaid Services & National Center for Health Statistics. (2024). ICD-10-CM official guidelines for coding and reporting FY 2025.
Confidentiality of Substance Use Disorder Patient Records, 42 C.F.R. Part 2 (2024).
D'Onofrio, G., O'Connor, P. G., Pantalon, M. V., Chawarski, M. C., Busch, S. H., Owens, P. H., Bernstein, S. L., & Fiellin, D. A. (2015). Emergency department-initiated buprenorphine/naloxone treatment for opioid dependence: A randomized clinical trial. JAMA, 313(16), 1636-1644. https://doi.org/10.1001/jama.2015.3474
How this NSG 544 Week 2 example is structured
The NSG/544 description includes using data for reimbursement. This paper traces a single data path, from what a clinician writes to what a payer receives, through a worked example and an audit, so the relationship between documentation, coding and payment is concrete, and it ends with changes that make documentation support accurate payment. Students search this week as NSG 544 Week 2, NSG544 Wk 2 or NSG/544 Wk 2; all three are the same assignment.
NSG/544 Week 2 questions, answered
What does NSG/544 Week 2 usually ask for?
The course description includes data used for reimbursement. Many sections ask students to trace how documentation becomes coded data and payment, and how data quality affects it.
How does documentation affect coding for opioid use disorder?
Diagnosis codes for opioid use disorder vary by severity and by whether withdrawal or other complications are present. If the note does not specify these, coders must choose less specific codes.
Are substance use disorder records treated differently?
Records from federally assisted substance use disorder treatment programs are protected by a separate federal confidentiality regulation, which limits how they can be used and disclosed, although recent changes have aligned it more closely with HIPAA.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.