Work through these ten groups in order, because later hospice applications build on earlier conventions and documentation rules. Each concept pairs a decision rule with a resolved example and a targeted mistake, so you practice choosing, not just recognizing. Compare your reasoning against the stated resolution, and revisit any concept where your answer diverges. This guide teaches subject matter; it is not an official syllabus and does not replace the official guidelines or your agency's policies.
ICD-10-CM Structure and Conventions
1. Index First, Then Tabular Verification
Locate every code through the Alphabetic Index first, then verify it in the Tabular List, because the classification's own conventions and instructions take precedence over the general guidelines when the two conflict.
Example: A hospice record lists debility. The coder locates the Index term, follows it to the Tabular List, and applies any instructional note found there before finalizing the code.
Mistake to avoid: Assigning a code directly from the Tabular List without tracing the Alphabetic Index pathway that leads to it.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
2. Placeholder X for Seventh-Character Codes
When a code requires a 7th character but has fewer than six characters, insert the placeholder X in the empty positions. A code with an applicable 7th character is invalid without the appropriate one, so the placeholder is structural, not optional.
Example: A subsequent pathologic fracture encounter needs a 7th character, so the 6-character placeholder X is inserted before the 7th character to keep the code length valid.
Mistake to avoid: Reporting a five-character code with a seventh character appended directly, producing an invalid code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
3. Seventh Character A Versus D in Fracture Care
For pathologic fractures, 7th character A applies while the patient receives active treatment and D applies after active treatment ends, during routine healing or recovery care. The choice turns on treatment status, never on whether the provider is seeing the patient for the first time.
Example: A hospice patient with a pathologic fracture finished active treatment and now receives routine healing-phase care; 7th character D applies even though a new physician just took over.
Mistake to avoid: Choosing 7th character A simply because the hospice physician is a new provider for the patient.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
4. Laterality From Other Clinicians and Conflicts
When the provider does not document laterality, code assignment may rely on documentation from other clinicians. If the record contains conflicting information about the affected side, the provider must be queried, and unspecified side codes should remain rare.
Example: A home health nurse documents a left-sided pressure injury, but the physician's note implies the right side; the coder queries the provider rather than picking either note.
Mistake to avoid: Silently choosing one clinician's side documentation when another clinician documented the opposite side.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
5. Distinguishing Other From Unspecified Codes
An 'other' code is used when the documentation provides specific detail but no code exists for that exact condition, whereas an 'unspecified' code is used when the clinical detail itself is unknown. Confusing the two misrepresents what the record actually says.
Example: A record documents a pneumonia type not represented by a specific code, so the 'other' pneumonia code is assigned rather than an unspecified pneumonia code.
Mistake to avoid: Defaulting to an unspecified code when the documentation actually describes a specific variant needing an 'other' code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
6. Code Length and Category Validity
All categories are three characters; subcategories have four or five, and codes may run three to seven. A three-character category with no subdivision is itself a valid code, but a subdivided category reported at three characters is incomplete and unusable.
Example: A three-character category with no further subdivision is reported as the complete code, while a category subdivided further cannot be reported at three characters.
Mistake to avoid: Reporting a subdivided three-character category as though it were a complete, billable code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Documentation Authority and Query Boundaries
7. Provider Diagnosis as the Coding Basis
Code assignment rests on documentation by the patient's provider, meaning the physician or other qualified practitioner legally accountable for establishing the diagnosis. Clinical staff notes alone do not establish reportable diagnoses outside a short list of defined exceptions.
Example: A nurse writes 'aspiration pneumonia' in a progress note, but the physician never documents it; the coder cannot assign the pneumonia code from the nurse's entry.
Mistake to avoid: Assigning a diagnosis code from nursing or aide documentation when no provider documented the condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
8. The Limited Non-Provider Documentation Exceptions
A defined exception list permits non-provider documentation for BMI, pressure ulcer stage, non-pressure ulcer depth, coma scale, stroke scale, laterality, blood alcohol level, underimmunization status, and firearm injury intent. The associated diagnosis, however, still requires provider documentation.
Example: A dietitian records the BMI value and a nurse stages the pressure ulcer, but the obesity and pressure ulcer diagnoses themselves must appear in provider documentation before coding.
Mistake to avoid: Coding a condition such as obesity or acute stroke solely because a non-provider clinician documented the measurement.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
9. Social Determinants From Non-Provider Clinicians
Social determinants of health classified to Chapter 21 may be coded from documentation by clinicians involved in the patient's care, such as social workers, case managers, community health workers, or nurses, because this is social information rather than a medical diagnosis.
Example: A social worker's note that the hospice patient lacks reliable transportation to appointments supports assigning the transportation-access code without a physician entry.
Mistake to avoid: Ignoring a social worker's documented food insecurity because no physician repeated it in the record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
10. Patient Self-Reported SDOH With Clinician Sign-Off
Patient self-reported information may support social determinant codes only when a clinician or provider signs off on it and it is incorporated into the official medical record. Unsigned patient statements outside the record do not establish code assignment.
Example: A patient-reported housing problem, countersigned by the case manager and filed in the official record, supports the homelessness code on the hospice claim.
Mistake to avoid: Coding a social determinant from an unsigned patient intake form that never entered the official record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
11. Secondary-Only Status of Measurement and SDOH Codes
Codes for BMI, coma scale, stroke scale, blood alcohol level, underimmunization status, and social determinants of health are restricted to secondary diagnosis positions. They supplement a provider-documented condition and are never reported as the principal or first-listed code.
Example: A dietitian documents a BMI of 31; the BMI code is reported as a secondary code only, supporting the provider-documented obesity diagnosis.
Mistake to avoid: Sequencing a BMI or SDOH code as the first-listed diagnosis on a hospice encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
12. Borderline Diagnoses Are Coded as Confirmed
A provider-documented borderline diagnosis is coded as confirmed unless the classification provides a specific entry for that borderline condition, in which case the specific entry is used. No inpatient-versus-outpatient distinction applies because borderline conditions are not uncertain diagnoses.
Example: The physician documents borderline diabetes mellitus; because a specific borderline entry exists in the classification, that specific code is assigned rather than a confirmed diabetes code.
Mistake to avoid: Treating a documented borderline condition as unconfirmed and deferring the code to a later encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Principal Diagnosis Selection in Hospice
13. UHDDS Definitions Apply to Hospice Care
The Uniform Hospital Discharge Data Set definitions govern principal diagnosis selection, and their application expressly extends to hospice services at all levels of care. The principal diagnosis is the condition established after study to be chiefly responsible for occasioning the admission.
Example: A hospice admission occurs chiefly for uncontrolled pain from documented lung cancer; the cancer, not a symptom code, is sequenced as principal.
Mistake to avoid: Assuming hospice encounters are exempt from UHDDS principal diagnosis rules that govern other non-outpatient settings.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
14. Symptoms Cannot Be Principal When a Definitive Diagnosis Exists
Symptom, sign, and ill-defined condition codes from Chapter 18 may not serve as the principal diagnosis when a related definitive diagnosis has been established. The definitive condition replaces the symptom in the principal position once study establishes it.
Example: End-stage heart failure is established as the reason for a hospice admission, so the heart failure code is principal and the dyspnea code is dropped from that position.
Mistake to avoid: Leaving a symptom such as debility or dyspnea in the principal slot after the underlying condition is confirmed.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
15. Two Interrelated Conditions and Sequencing Freedom
When two or more interrelated conditions, such as diseases in the same chapter or manifestations characteristically associated with a disease, each potentially meet the principal diagnosis definition, either may be sequenced first unless admission circumstances, therapy, the Tabular List, or the Index direct otherwise.
Example: A hospice admission relates to coexisting COPD and cor pulmonale, characteristically associated conditions; either may be sequenced first absent contrary instruction.
Mistake to avoid: Automatically sequencing the alphabetically first condition when either interrelated condition could legitimately lead.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
16. Equally Qualifying Diagnoses Without Direction
In the unusual case where two or more diagnoses equally meet the principal diagnosis criteria based on admission circumstances, workup, and therapy, and neither the Index, Tabular List, nor guidelines supply sequencing direction, any one of the diagnoses may be sequenced first.
Example: Two unrelated terminal conditions equally occasion a hospice admission and no coding direction exists; the coder sequences either one first and documents the rationale.
Mistake to avoid: Inventing a sequencing hierarchy that neither the classification nor the guidelines actually provide.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. Circumstances of Admission Govern the Choice
The circumstances of the admission always govern principal diagnosis selection, not merely which conditions appear in the record or receive some attention. Focus on what chiefly occasioned this admission for care, as established after study.
Example: A patient enters hospice for symptom management of a malignancy rather than for a incidental fall injury; the malignancy is principal despite the injury being treated.
Mistake to avoid: Selecting the principal diagnosis by which condition has the longest history rather than what occasioned the admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Classification Conventions Outrank Guidelines in Sequencing
Coding conventions within the ICD-10-CM itself, including Tabular List and Alphabetic Index instructions, take precedence over the official guidelines when selecting the principal diagnosis. Always resolve classification-level instruction before applying general sequencing guidance.
Example: A Tabular List note requires sequencing a manifestation after its underlying etiology; that note overrides a general guideline permitting either order for interrelated conditions.
Mistake to avoid: Applying a general guideline sequencing option that a specific Tabular List note overrides.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Additional Diagnoses in Hospice Reporting
19. UHDDS Other-Diagnoses Criteria
Other diagnoses are additional clinically significant conditions that affect patient care by requiring clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care and monitoring. Coexistence at admission or subsequent development both qualify.
Example: A hospice patient's type 2 diabetes requires ongoing medication adjustment and monitoring during the stay, so it qualifies as an additional diagnosis.
Mistake to avoid: Reporting every listed historical condition without asking whether it affected care during this episode.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
20. Excluding Conditions With No Bearing on the Current Stay
Diagnoses relating to an earlier episode that have no bearing on the current stay are excluded from additional diagnosis reporting. The test is whether the condition coexisted at admission, developed subsequently, or affected treatment received or length of stay.
Example: A remote cholecystectomy appears in the history but needs no evaluation or treatment during the hospice stay; it is excluded from the claim.
Mistake to avoid: Carrying a resolved, historical condition onto the current claim simply because it appears on a problem list.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. Final Diagnostic Statement Presumption
If the provider includes a diagnosis in the final diagnostic statement, such as a discharge summary or face sheet, it should ordinarily be coded. The provider's final statement carries presumptive weight for identifying which conditions count for the encounter.
Example: The physician's final hospice certification statement includes hypothyroidism; it is ordinarily coded even if the chart elsewhere minimizes it.
Mistake to avoid: Omitting a condition the provider explicitly listed in the final statement because it seemed minor.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. Dementia Severity Progression During an Inpatient Stay
When a patient is admitted to an inpatient acute care hospital or other inpatient facility setting with dementia at one severity level and it progresses to a higher severity level during that stay, assign a single code for the highest severity level reported. The rule is tied to an inpatient facility stay, so confirm the care setting before collapsing severity codes.
Example: A patient admitted to an inpatient hospice unit with moderate dementia progresses to severe dementia before the end of the stay; one code at the highest documented severity is assigned.
Mistake to avoid: Reporting two dementia codes to show a severity change within one continuous inpatient episode of care.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. Assign Enough Codes to Fully Explain the Encounter
Assign as many codes as necessary to fully explain each healthcare encounter. This is especially relevant when documentation is sparse, such as disaster aftermath records, where any available documentation supports external cause and Z codes capturing the full picture.
Example: A patient admitted after a hurricane has a laceration, displacement from home, and unavailable medical facilities; the injury, external cause, and applicable Z codes are all reported.
Mistake to avoid: Stopping at the first-listed diagnosis when the record clearly supports additional reportable conditions.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Nursing Care and Monitoring as a Qualifying Criterion
Increased nursing care and monitoring alone can establish clinical significance for an additional diagnosis. In hospice, where nursing intensity often defines the plan of care, conditions driving that intensity, such as wounds or symptom burdens, meet the reporting threshold.
Example: A pressure injury requiring daily wound care and turning schedules adds an additional diagnosis because it increases nursing care and monitoring.
Mistake to avoid: Overlooking conditions managed entirely through nursing interventions as not significant enough to report.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Condition-Specific Rules in Hospice Records
25. Dementia Severity Requires Provider Judgment
Dementia codes classify by etiology and severity, and severity selection requires the provider's clinical judgment documented in the record. When no severity information is documented, assign the unspecified severity code; coders never deduce severity from services rendered.
Example: A hospice record documents dementia without any severity descriptor; the coder assigns the unspecified severity code rather than inferring moderate from care needs.
Mistake to avoid: Assigning a severity level based on the level of assistance the patient needs rather than provider documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
26. HIV Coding Limited to Confirmed Cases
Only confirmed cases of HIV are coded, and the confirmation requirements differ between inpatient and outpatient settings. Distinguish exposure or suspicion from confirmed illness; an exposure without confirmed infection does not support an HIV diagnosis code.
Example: A note mentions a possible HIV exposure from a needlestick but no confirmed test result; no HIV code is assigned for that patient at that encounter.
Mistake to avoid: Coding HIV from a documented exposure or screening mention without a confirmed diagnostic statement.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
27. Acute Injury Versus Chronic Musculoskeletal Conditions
Current, acute injuries are coded from Chapter 19, while conditions resulting from healed injuries and recurrent musculoskeletal problems generally code to Chapter 13. When documentation does not make the acute-versus-chronic distinction clear, query the provider.
Example: A patient has chronic knee pain attributed to an old healed injury; the Chapter 13 chronic condition code is assigned, not a current Chapter 19 injury code.
Mistake to avoid: Assigning a current injury code for a chronic or recurrent condition stemming from a healed injury.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Multiple Sites Coding Logic
The classification defines multiple as involving two or more sites. When chapter-specific guidance is absent, assign codes for specified sites individually when documented; only when the sites are not documented does the multiple-sites code apply.
Example: A patient has pressure injuries on the sacrum and right heel; both sites are coded individually because each is separately documented.
Mistake to avoid: Defaulting to a multiple-sites code when the record actually names each affected site.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Pain Due to Indwelling Medical Devices
Pain associated with devices, implants, or grafts left in a surgical site is assigned to the appropriate Chapter 19 code, with an additional category G89 code identifying whether the pain due to the device is acute or chronic.
Example: A hospice patient reports pain from a hip prosthesis; the device-related pain code is assigned with an additional G89 code identifying its chronic nature.
Mistake to avoid: Coding device-related pain only as a generic pain code without the additional G89 device-pain code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Transplant Complications Require Functional Impact
Transplant complication codes apply only when the complication affects the transplanted organ's function, and two codes are needed: the T86 complication code plus a secondary code identifying the complication. Pre-existing or post-transplant conditions without functional impact are not complications.
Example: A transplanted kidney shows stable chronic disease without documented rejection; the transplant complication code is not assigned and the coder queries if unsure.
Mistake to avoid: Assigning a transplant complication code for chronic disease following transplant without documented failure or rejection.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Sequelae, Intent, and External Cause Reporting
31. Sequela External Cause Codes With Seventh Character S
Late effects of previous injuries are reported using the external cause code with the seventh character S for sequela, used with any report of a late effect resulting from a previous injury. A sequela external cause code must never be used with a related current injury code for the same condition.
Example: A patient receives ongoing care for knee stiffness documented as a late effect of a femur fracture suffered in a motor vehicle crash two years earlier; the late effect is reported along with the transport accident external cause code carrying the 7th character S for sequela.
Mistake to avoid: Reporting a sequela external cause code alongside a current injury code for the same injury.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
32. Late-Effect Codes Only When a Late Effect Is Documented
Use a late-effect external cause code only for subsequent visits treating a documented late effect of the initial injury. Follow-up visits to assess healing or receive rehabilitative therapy, without any documented late effect, do not qualify for sequela external cause coding.
Example: A patient returns for routine healing checks of a treated fracture with no documented late effect; the late-effect external cause code is not used.
Mistake to avoid: Applying sequela external cause codes to ordinary healing-phase follow-up visits.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. Unknown Intent Defaults to Accidental
When the intent of an injury's cause is unknown or unspecified, code the intent as accidental. External cause codes for undetermined intent are reserved for records that specifically state the intent cannot be determined, a much narrower situation.
Example: A hospice patient is found with injuries of unstated cause; the intent is coded as accidental because the record never states the intent cannot be determined.
Mistake to avoid: Assigning an undetermined-intent code whenever the documentation simply omits intent.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. External Causes Are Never Principal or First-Listed
External cause of morbidity codes are supplemental and are never recorded as the principal diagnosis, or first-listed in non-inpatient settings. The appropriate injury code is always sequenced before any external cause codes that explain how it happened.
Example: A fall-related fracture is the reason for care; the fracture code is sequenced first and the external cause code for the fall follows, never the reverse.
Mistake to avoid: Sequencing an external cause code in the first-listed position ahead of the injury being treated.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
35. Terrorism Identification and First-Listed External Cause
When the Federal Government identifies an injury's cause as terrorism, the first-listed external cause code must come from the terrorism category. This is a sequencing rule within external cause reporting and does not change the rule that injury codes precede all external causes.
Example: An injury is officially identified by the Federal Government as terrorism-related; the terrorism category code becomes the first-listed external cause code.
Mistake to avoid: Sequencing a routine external cause code first when the event was federally designated as terrorism.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
36. Disaster-Related Z Codes as Secondary Information
Disaster aftermath encounters may need Z codes such as homelessness, inadequate housing, extreme poverty, unavailability of healthcare facilities, or ventilator dependence during power failure, reported as principal or secondary depending on circumstances. These are examples, not an exhaustive list.
Example: A displaced patient on a ventilator during a power failure receives the ventilator-dependence-during-power-failure Z code as a secondary code alongside the acute condition codes.
Mistake to avoid: Treating the disaster-related Z code list as exhaustive and ignoring other applicable codes the documentation supports.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Z Codes and Social Determinants in Hospice
37. Z Codes in Any Setting and Their Position
Z codes may be used in any healthcare setting, either as the reason for the encounter or to provide additional information about it. The distinction determines position: a Z code stating the reason for the encounter can be first-listed, while informational Z codes are secondary.
Example: A hospice encounter occurs solely for palliative symptom management; the Z code for that reason may serve as the first-listed code for the encounter.
Mistake to avoid: Relegating every Z code to secondary status even when it states the encounter's reason.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
38. Living Alone Versus Problems Related to Living Alone
A patient who lives alone and suffers an acute injury temporarily limiting routine activities supports the living-alone problem code when documented as such. Merely living alone, without documentation of a risk or unmet need for assistance, does not support that code.
Example: A chart notes the patient lives alone with no documented risk or unmet need; the living-alone problem code is not assigned from that fact alone.
Mistake to avoid: Assigning the living-alone problem code from a demographic fact with no documented risk or need.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
39. Food Insecurity Documentation Standard
Documentation by a clinician, or patient-reported information signed off by a clinician, that the patient expressed concerns about access and availability of food supports the food insecurity code. The concern must be captured in the official record, not merely mentioned informally.
Example: The patient tells the nurse she worries about running out of food; the nurse's signed note supports the food insecurity code on the encounter.
Mistake to avoid: Coding food insecurity from an unsigned patient remark that never entered the official record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
40. Homelessness Coding From Record Documentation
Medical record documentation indicating the patient is experiencing homelessness supports assignment of a code from the homelessness subcategory. Like other social determinants, this is social information that non-provider clinicians may document, subject to inclusion in the official record.
Example: A record documents that the patient is experiencing homelessness; the coder assigns the homelessness code from subcategory Z59.0 based on that documentation.
Mistake to avoid: Inferring homelessness from a shelter address without any documentation of the housing circumstance.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
41. Mapping SDOH Categories Z55 Through Z65
Social determinant codes cluster in categories covering education and literacy, employment, occupational risk, physical environment, housing and economic circumstances, social environment, upbringing, primary support group and family circumstances, and other psychosocial circumstances. Match the documented issue to its category.
Example: A hospice social worker documents caregiver strain in the home; the coder locates the appropriate family-circumstances category and assigns the matching code.
Mistake to avoid: Forcing a documented psychosocial issue into an unrelated Z category instead of finding its proper home.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
42. Status Z Codes for Lifelong Perinatal History
Codes for prematurity or low birth weight status are used for a child or adult whose newborn history affects current health status. This is a status code providing context, distinct from coding an active perinatal condition, and it is reported as additional information.
Example: A patient with a documented history of low birth weight whose current health is affected receives the immaturity status code as an additional code.
Mistake to avoid: Coding an active perinatal disorder code for an adult whose prematurity history merely affects current status.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
HIPAA Privacy Foundations for Hospice Coders
43. Hospice Agencies as Covered Entities
The Privacy Rule applies to health plans, healthcare clearinghouses, and any healthcare provider that transmits health information electronically in connection with standard HIPAA transactions, such as claims or eligibility inquiries. A hospice agency submitting electronic claims meets this definition regardless of size.
Example: A hospice agency bills Medicare electronically for services; it is a covered entity because it transmits health information in connection with standard transactions.
Mistake to avoid: Assuming a small hospice provider escapes covered entity status because of its size.
Reference: HHS Summary of the HIPAA Privacy Rule
44. PHI Spans Electronic, Paper, and Oral Forms
Protected health information is individually identifiable health information held or transmitted by a covered entity or its business associate in any form, whether electronic, paper, or oral. Verbal discussion of a patient's condition is fully within the Privacy Rule's scope.
Example: A coder discusses a patient's terminal diagnosis over the phone with a colleague within earshot of a visitor; that oral exchange is protected information.
Mistake to avoid: Treating oral hallway or phone discussion of patients as outside privacy protections.
Reference: HHS Summary of the HIPAA Privacy Rule
45. Business Associates and Written Safeguards
A business associate is a non-workforce person or organization performing functions for a covered entity involving protected health information, such as claims processing, billing, or data analysis. The covered entity must impose written safeguards through a business associate agreement.
Example: A hospice agency hires an outside billing contractor that handles claims containing patient identifiers; a written business associate agreement with safeguards is required.
Mistake to avoid: Engaging a billing or consulting contractor handling patient data without a business associate agreement.
Reference: HHS Summary of the HIPAA Privacy Rule
46. Minimum Necessary and Role-Based Access
Covered entities must make reasonable efforts to use, disclose, and request only the minimum protected health information needed for the purpose. Role-based policies should restrict access, and an entire medical record may not be used unless specifically justified as the amount reasonably needed.
Example: A coder needs one diagnosis detail for a reconciliation task; accessing the entire medical record is not justified unless the whole record is reasonably needed.
Mistake to avoid: Granting coders blanket access to full records for tasks that only require selected documentation.
Reference: HHS Summary of the HIPAA Privacy Rule
47. Treatment, Payment, and Operations Without Authorization
A covered entity may use and disclose protected health information without individual authorization for its own treatment, payment, and health care operations, and for treatment activities of any provider. Coordination of care among clinicians falls squarely within permitted treatment uses.
Example: A hospice nurse consults the patient's attending physician by phone about symptom management; no authorization is needed for that treatment disclosure.
Mistake to avoid: Demanding signed authorizations for routine care coordination and billing activities that TPO already permits.
Reference: HHS Summary of the HIPAA Privacy Rule
48. De-Identification Removes Privacy Restrictions
De-identified health information neither identifies nor provides a reasonable basis to identify an individual, and no restrictions apply to its use or disclosure. De-identification requires either a qualified statistician's formal determination or removal of specified identifiers with no actual knowledge of re-identifiability.
Example: A hospice quality team strips names, full addresses, and exact dates from a dataset for an internal study; the de-identified data carries no use restrictions.
Mistake to avoid: Removing only the patient's name and assuming the remaining record qualifies as de-identified.
Reference: HHS Summary of the HIPAA Privacy Rule
Permitted Disclosures and Rights in Hospice Practice
49. Decedent Disclosures to Funeral Directors and Coroners
Covered entities may disclose protected health information to funeral directors as needed, and to coroners or medical examiners to identify a deceased person, determine cause of death, and perform other authorized functions. These decedent disclosures are permitted without individual authorization.
Example: A hospice agency provides the death record information a funeral director needs to carry out duties; no written authorization is required for that disclosure.
Mistake to avoid: Requiring an estate authorization before releasing necessary information to the funeral home.
Reference: HHS Summary of the HIPAA Privacy Rule
50. Family Notification With Informal Permission
A covered entity may disclose to family, relatives, friends, or others the patient identifies information directly relevant to that person's involvement in care or payment, relying on informal permission. When the patient is incapacitated or unavailable, professional judgment may permit disclosure in the patient's best interest.
Example: A daughter asks about her mother's comfort care; the nurse shares only information directly relevant to the daughter's involvement, based on the patient's informal agreement.
Mistake to avoid: Reciting the full medical record to a relative whose involvement concerns only one care issue.
Reference: HHS Summary of the HIPAA Privacy Rule
51. Personal Representatives Treated as the Individual
A personal representative, someone legally authorized to make health decisions for the individual or to act for a deceased individual or estate, must be treated the same as the individual for uses, disclosures, and rights. An exception exists where the representative may be abusing or endangering the patient.
Example: A healthcare power of attorney requests the hospice record; the agency treats the personal representative as the individual, absent any endangerment concern.
Mistake to avoid: Refusing a legally authorized representative's record access as though they were a third party.
Reference: HHS Summary of the HIPAA Privacy Rule
52. Psychotherapy Notes Need Authorization
Psychotherapy notes, a mental health professional's separated notes analyzing private counseling conversations, require authorization for most uses, including most treatment, payment, and operations purposes. They exclude medication monitoring, session times, and treatment plan summaries, which follow ordinary rules.
Example: A hospice wants to send counseling process notes to a payer; authorization is required, even though the payer could otherwise receive treatment information.
Mistake to avoid: Releasing counseling process notes under a payment rationale without the required authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
53. Authorization Elements for Non-Permitted Disclosures
Any use or disclosure not permitted for treatment, payment, operations, or another permitted purpose requires written authorization in plain language, specifying the information, who discloses and receives it, expiration, and the right to revoke in writing. Treatment cannot generally be conditioned on granting authorization.
Example: A hospice discloses records to a life insurer for coverage purposes; a written authorization naming the recipient, purpose, and expiration is obtained first.
Mistake to avoid: Accepting a vague blanket release that omits recipient, purpose, or revocation rights.
Reference: HHS Summary of the HIPAA Privacy Rule
54. Accounting of Disclosures and Its Exclusions
Individuals may obtain an accounting of disclosures covering the six years preceding the request. Disclosures for treatment, payment, operations, to the individual, under authorization, or of limited data sets are excluded, so routine hospice care coordination does not appear on the accounting.
Example: A family requests an accounting six years back; the agency lists the coroner and oversight disclosures but not treatment coordination with the attending physician.
Mistake to avoid: Including routine treatment and payment disclosures in an accounting where the Rule excludes them.
Reference: HHS Summary of the HIPAA Privacy Rule
Professional Hospice Coding Practice
55. Documentation Reconciliation as a Core Duty
A core HCS-H role is documentation reconciliation: comparing the clinician's assessment, the physician certification, and the coded output so all three align. Discrepancies between what was assessed and what was certified must be resolved through collaboration, not silently coded in either direction.
Example: The clinician assessed anxiety but the certification lists only the malignancy; the coder reconciles the discrepancy with the clinician before finalizing codes.
Mistake to avoid: Coding strictly from the certification while ignoring conditions the clinician clearly assessed and treated.
56. Collaboration With Clinicians and Administrators
Hospice coding specialists collaborate with clinicians, physicians, and managers or administrators as part of the credentialed role. Ambiguous documentation is resolved through that collaboration, keeping code assignment anchored to what the care team actually established.
Example: A coder questions whether documented 'failure' means cardiac or general decline; the physician clarifies before the code is assigned.
Mistake to avoid: Resolving ambiguous documentation unilaterally instead of returning it to the documenting clinician.
57. Legal and Ethical Conduct in Hospice Coding
Credentialed hospice coders ensure activities are done legally and ethically, supporting hospice agency policy, regulatory requirements, and professional guidelines. Coding decisions must withstand this framework, which means record support governs over convenience or internal pressure.
Example: A coder declines to add a diagnosis the record does not support, even though it would improve the agency's reported case picture.
Mistake to avoid: Adjusting codes to satisfy internal expectations when the documentation does not support them.
58. Coding to the Level of Certainty Known
Each encounter is coded to the level of certainty known at that time. When no definitive diagnosis is established by the encounter's end, sign and symptom codes are appropriate in place of a diagnosis, and it is improper to select a specific code the documentation does not support.
Example: A note says 'possible pneumonia versus aspiration'; with no definitive statement, the coder reports the documented symptom rather than either pneumonia.
Mistake to avoid: Converting a documented 'possible' condition into a confirmed diagnosis code for the encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
59. Reviewing the Entire Record Before Coding
The entire record should be reviewed to determine the specific reason for the encounter and the conditions treated. Relying on a single document, such as only the face sheet, risks missing the conditions that actually drove the admission and the care delivered.
Example: A hospice admission note references an old surgical complication, but the coder reviews the full record and finds the current reason is symptom control, changing the sequence.
Mistake to avoid: Coding from the face sheet alone while the interdisciplinary notes establish a different reason for care.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
60. Querying When Documentation Is Unclear
Query the provider whenever documentation is unclear about a relationship, a borderline condition, laterality conflicts, or whether a condition qualifies. Querying is the sanctioned path to accuracy; guessing or coding around ambiguity undermines both the guidelines and the hospice record's integrity.
Example: A wound etiology is documented only as 'pressure area' by nursing; the coder queries the provider for the ulcer diagnosis rather than coding from the nurse's phrase.
Mistake to avoid: Assigning the most clinically plausible code instead of querying when the documentation is genuinely ambiguous.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
References and further reading
Source links checked on Oct 2, 2026.