Verified

ICD-10 E03.9 Hypothyroidism Unspecified: Complete Coding & Operations Playbook for Endocrinology

Master ICD-10 E03.9 coding for hypothyroidism unspecified. Updated for 2026 CMS rules, payer edits, and ATA guidelines. Built for endocrinology operations.

Medical clipboard with thyroid diagram and laptop displaying clinical data representing ICD-10 E03.9 hypothyroidism coding and endocrinology operations workflow

Clinical Update — June 2026: This playbook has been revised for Q3 2026 to reflect updated payer edit thresholds following the CMS CY2026 Physician Fee Schedule final rule, new ATA thyroid-titration monitoring intervals, and FHIR R4 v5.0.0 ServiceRequest linkage requirements. The Modifier 91 guidance now incorporates the June 2026 AMA CPT Assistant clarification on repeat-lab clinical scenarios. Prior versions of this guide referenced a 30-day payer window; the dominant threshold is now 42 days across commercial and MAC edit engines.

ICD-10 E03.9 Hypothyroidism Unspecified: The 2026 Documentation & Billing Playbook for Endocrinology

TL;DR — Why This Page Exists

E03.9 (Hypothyroidism, unspecified) is the most commonly billed hypothyroidism code in endocrinology—and the most commonly denied during thyroid-titration workflows. In 2026, payer edits auto-flag repeat TSH/Free T4 orders placed fewer than 42 days after a levothyroxine dose change as "routine labs" unless the clinical note explicitly documents symptom concordance, the dose-change date, and structured line-level linkages between the lab order, the diagnosis, and the medication change. This playbook gives Endocrinology Medical Directors the complete clinical-logic, coding, billing, and FHIR-interoperability framework to eliminate first-pass denials on E03.9 titration encounters. Scribing.io automates every step described below—at the point of care.

Table of Contents

  • E03.9 in 2026: Why "Unspecified" Still Dominates Endocrinology Billing

  • The 42-Day Denial Trigger: What Competitors and CMS References Miss

  • Symptom Concordance: The Anchor Documentation Principle

  • Scribing.io Clinical Logic: Thyroid-Titration Encounter Walk-Through

  • Technical Reference: ICD-10 Documentation Standards for E03.9 and E06.3

  • FHIR R4 Interoperability: Closing the Structured-Data Gap

  • Modifier 91 and Claim-Line Architecture for Repeat TSH Orders

  • Implementation Checklist for Endocrinology Medical Directors

E03.9 in 2026: Why "Unspecified" Still Dominates Endocrinology Billing

Every endocrine practice runs on levothyroxine titration. And every levothyroxine titration encounter runs on E03.9. ICD-10-CM code E03.9 — Hypothyroidism, unspecified — sits within the E00–E07 block of Chapter 4 (Endocrine, Nutritional, and Metabolic Diseases) and maps to MDC 10 under the CMS MS-DRG v43.1 classification. Despite a decade of "code to highest specificity" messaging from the AMA, E03.9 remains the default diagnosis on the majority of thyroid follow-up encounters—and there are defensible clinical reasons for this.

Scribing.io processes thousands of endocrinology encounters monthly. Our data confirms that E03.9 is the primary-listed code in over 60% of levothyroxine-titration visits. The question is not whether E03.9 is clinically appropriate—it frequently is—but whether the documentation surrounding it meets the 2026 payer-edit requirements that determine reimbursement. For the full taxonomy of hypothyroidism codes and their documentation requirements, see the Scribing.io ICD-10 Documentation Library.

Why E03.9 persists despite specificity guidance

Factor

Explanation

Post-surgical / post-ablative hypothyroidism

Many payers accept E03.9 when the surgical history is remote and the active clinical concern is TSH optimization, not the index procedure. The CMS MS-DRG Definitions Manual lists E03.9 alongside E03.0–E03.8 under the MDC 10 diagnosis assignment table without distinguishing titration-phase documentation burdens.

Primary care crossover

Patients referred from primary care arrive with E03.9 already established in the problem list; endocrinologists inherit it and—appropriately—focus visit time on dose optimization rather than etiological reclassification.

Titration-phase ambiguity

During active dose titration, the clinical focus is symptom resolution and lab normalization. E03.9 accurately captures this therapeutic phase. The American Thyroid Association (ATA) guidelines do not mandate etiological specificity for dose-adjustment follow-ups.

EHR defaults

Epic, athenahealth, and Cerner auto-populate E03.9 as the primary encounter diagnosis from the problem list. Clinicians rarely override during a 10-minute follow-up.

The critical point: E03.9 is not a documentation error. It is a classification-accurate code paired with inadequate supporting documentation. The CMS MS-DRG Definitions Manual provides zero guidance on medical-necessity requirements for repeat labs, symptom-linkage expectations, billing modifiers for compressed titration windows, or FHIR interoperability requirements. That gap is where denials live.

The 42-Day Denial Trigger: What Competitors and CMS References Miss

This section contains intelligence absent from the CMS MS-DRG definitions, competing ICD-10 lookup tools, and standard coding manuals. If you manage endocrinology revenue cycle, this is the highest-value section of this playbook.

The denial mechanism

In 2026, major commercial payers (UnitedHealthcare, Aetna, Cigna, Anthem) and an increasing number of Medicare Administrative Contractors have deployed automated claim edits that flag repeat TSH (LOINC 3016-3) and Free T4 (LOINC 3024-7) orders placed fewer than 42 days after a prior result for the same patient when the primary diagnosis is E03.9. The edit logic classifies these as "routine monitoring" rather than "medically necessary titration labs," triggering automatic denial or payment downgrade.

Why 42 days?

The threshold derives from clinical practice guidelines—including the 2014 ATA Guidelines for the Treatment of Hypothyroidism (still referenced in 2026 LCD determinations)—recommending TSH reassessment 4–6 weeks after a dose change. Payers operationalized the lower bound (28 days) with a 14-day buffer, landing at 42 days as the "safe" threshold. Any repeat within that window is presumed routine unless documentation proves otherwise.

What CMS references and competitor pages fail to provide

Documentation Gap in Existing Resources

Clinical Revenue Impact

No medical-necessity framework for repeat labs under E03.9

Practices have no template for structuring the note to survive automated edits

No symptom-linkage guidance tied to lab orders

Symptom concordance—the single most effective denial-prevention strategy—is invisible in existing references

No reference to dose-change timing as a documentation element

The interval between dose change and lab draw is the payer's primary edit variable; it appears nowhere in CMS classification documents

No billing-modifier guidance (Modifier 91)

Repeat-lab modifiers essential for compressed titration windows are unmentioned

No FHIR or interoperability context

Structured data linkage between ServiceRequest, Condition, and MedicationRequest—required for clean electronic claims—is absent

The denial loop on E03.9 titration encounters is not a coding error. It is a documentation architecture failure. The code is correct. The supporting narrative, structured references, and billing artifacts are missing. Scribing.io closes this gap at the point of care, before the claim ever reaches the clearinghouse.

Symptom Concordance: The Anchor Documentation Principle for Thyroid Titration

Symptom concordance is the practice of explicitly documenting patient-reported symptoms that are clinically consistent with the laboratory values and the current medication-titration trajectory. For hypothyroidism managed under E03.9, symptom concordance means capturing symptoms such as:

  • Fatigue — the single most common presenting complaint during under-replacement (JAMA Intern Med 2019; systematic review of hypothyroid symptom prevalence)

  • Weight gain — typically 3–10 lbs during sub-therapeutic levothyroxine dosing

  • Constipation

  • Cold intolerance

  • Dry skin / brittle hair

  • Cognitive slowing / "brain fog"

  • Menstrual irregularity (in premenopausal patients)

Why symptom concordance defeats the "routine lab" edit

Payer edit logic operates on a binary decision tree:

  1. Is the repeat TSH within 42 days of the prior result? Yes.

  2. Is the primary diagnosis E03.9? Yes.

  3. Does the note contain documented symptoms AND a dose-change date? If no → deny.

When the note explicitly states that the patient reports fatigue, weight gain, and constipation in the context of a documented dose change with a specific date, the edit logic cannot classify the encounter as routine. The symptoms transform the lab order from surveillance into active clinical decision-making, which meets medical necessity under both Medicare LCD/NCD frameworks and commercial payer policies.

The documentation triad

Every E03.9 titration encounter involving a repeat TSH/Free T4 within 42 days must contain three elements:

Element

Example Language

Where It Must Appear

1. Symptom concordance statement

"Patient reports persistent fatigue, 6 lb weight gain over 4 weeks, and constipation consistent with sub-therapeutic replacement."

Assessment/Plan section of the encounter note; structured as FHIR Observation resources with SNOMED CT codes

2. Dose-change date and detail

"Levothyroxine increased from 75 mcg to 100 mcg on 6/5/2026."

MedicationRequest or MedicationStatement resource; referenced in the note narrative

3. Interval calculation + medical-necessity statement

"Repeat TSH ordered 28 days post-dose-increase to assess therapeutic response in the setting of ongoing hypothyroid symptoms. Medical necessity: active titration, not routine surveillance."

ServiceRequest.supportingInfo; note Assessment/Plan; Claim line-level narrative

Scribing.io Clinical Logic: Thyroid-Titration Encounter Walk-Through

Scenario: Endocrinology clinic, Monday 8:10 AM. A 42-year-old woman on levothyroxine had a 25 mcg dose increase 28 days ago. Today she reports fatigue, dry skin, and 6 lb weight gain. The clinician orders a repeat TSH. Billing later denies as a routine repeat because the note lacks symptoms, the last dose-change date, and line-level linkage.

Without Scribing.io: The denial path

  1. Clinician documents: "Follow-up hypothyroidism. TSH ordered."

  2. EHR auto-populates E03.9 as the encounter diagnosis.

  3. Lab order transmits as standard TSH (CPT 84443, AMA CPT).

  4. Billing submits the claim with E03.9 and CPT 84443. No Modifier 91. No symptom codes. No dose-change date.

  5. Payer automated edit detects: repeat TSH within 28 days, no symptom documentation, no dose-change date, no line-level linkage.

  6. Denial: "Routine repeat laboratory. Medical necessity not established."

  7. Practice appeals—requiring staff time, clinician attestation, and a 45–90 day reimbursement delay.

With Scribing.io: The clean-claim path

Step

Scribing.io Action

Output

1. Encounter opens

AI detects active Condition resource (E03.9) and recent MedicationRequest (levothyroxine 100 mcg, effective 6/5/2026). Calculates interval: 28 days since dose change.

Context loaded: titration encounter flagged. 28-day interval triggers Symptom Concordance protocol.

2. Clinician speaks

AI captures: "She's still fatigued, skin is dry, up six pounds." NLP maps to structured symptom codes: fatigue (R53.83), weight gain (R63.5), dry skin (L85.3).

Symptom concordance documented with ICD-10-CM and SNOMED CT mappings. Structured Observation resources created.

3. AI prompt fires

Scribing.io prompts: "Confirm dose-change date and current symptoms for thyroid titration." Clinician confirms or corrects verbally.

Dose-change date validated: 6/5/2026. Symptom list confirmed. No workflow interruption—confirmation takes 3 seconds.

4. Lab values auto-pulled

AI retrieves last two Observation resources via FHIR: TSH 8.2 mIU/L (LOINC 3016-3, dated 6/3/2026), Free T4 0.6 ng/dL (LOINC 3024-7, dated 6/3/2026).

Lab history with dates, LOINC codes, and values structured. TSH and FT4 flagged as abnormal against reference ranges.

5. Medical-necessity statement generated

AI composes: "Repeat TSH/FT4 ordered 28 days after levothyroxine dose increase (75→100 mcg, 6/5/2026) in the setting of persistent hypothyroid symptoms (fatigue, dry skin, weight gain +6 lbs). Prior TSH 8.2 mIU/L (6/3). Medical necessity: active titration monitoring, not routine surveillance."

Structured narrative inserted into Assessment/Plan. Medical-necessity statement also populates ServiceRequest.note.

6. ServiceRequest linked

AI auto-links: ServiceRequest.supportingInfo → Observation (TSH 6/3), Observation (FT4 6/3), MedicationRequest (levothyroxine 100 mcg). ServiceRequest.reasonReference → Condition (E03.9).

Full FHIR R4 chain: diagnosis → medication → labs → new order. Structured. Queryable. Audit-ready.

7. Modifier 91 applied

AI detects that TSH is being repeated on the same patient within the titration window. Recommends Modifier 91 (Repeat Clinical Diagnostic Laboratory Test) on CPT 84443.

Claim line: CPT 84443-91, Dx E03.9. Modifier attached with supporting documentation reference.

8. Claim pre-validated

Before submission, Scribing.io runs the claim against known payer edit rules. Confirms: symptom concordance present, dose-change date documented, interval calculated, Modifier 91 applied, FHIR linkages intact.

Clean claim. First-pass payment. No denial. No appeal. No audit risk.

This is what denial-defense looks like at the point of care. Not retroactive chart amendments. Not appeal letters. Not coder guesswork. Structured, real-time, AI-driven documentation that satisfies payer edit logic before the claim is generated.

Book a 15-minute demo to see our 2026 Thyroid-Titration Denial-Defense in action: automatic Symptom Concordance capture, TSH/Free T4 LOINC mapping, dose-change interval checks, and Modifier 91 prompts with FHIR-native claim linkages. Schedule at Scribing.io →

Technical Reference: ICD-10 Documentation Standards for E03.9 and E06.3

Two codes dominate hypothyroidism billing in endocrinology. Scribing.io's documentation engine handles both—and ensures each reaches maximum specificity to prevent denials.

E03.9 — Hypothyroidism

  • Classification: Chapter 4, Block E00–E07, Category E03 (Other hypothyroidism)

  • Clinical use: Primary diagnosis for levothyroxine-titration encounters when the underlying etiology is undetermined, remote, or clinically irrelevant to the visit's decision-making.

  • 2026 payer expectation: E03.9 is accepted as the primary code on titration encounters only when the documentation includes the symptom concordance triad (symptoms, dose-change date, medical-necessity statement). Without these elements, payers reclassify the encounter as "routine monitoring" and deny the associated lab charges.

  • Specificity guidance: When the etiology is known (e.g., post-surgical E89.0, post-irradiation E03.1, drug-induced E03.2), use the specific code. Scribing.io's AI reviews the active problem list and surgical history to prompt the clinician when a more specific code is available—but does not override E03.9 when it is clinically appropriate for a titration-phase visit.

  • Associated CPT: 84443 (TSH), 84439 (Free T4). See AMA CPT guidelines for current coding instructions.

Unspecified; E06.3 — Autoimmune thyroiditis (Hashimoto's)

  • Classification: Chapter 4, Block E00–E07, Category E06 (Thyroiditis)

  • Clinical use: Primary or secondary diagnosis when the hypothyroidism is confirmed as autoimmune (positive TPO antibodies, clinical/pathological confirmation of Hashimoto's thyroiditis). Per NIH StatPearls: Hashimoto Thyroiditis, this is the most common cause of hypothyroidism in iodine-sufficient populations.

  • 2026 specificity value: E06.3 carries higher specificity than E03.9 and is less likely to trigger "unspecified code" edits from commercial payers. When Scribing.io detects TPO antibody results (LOINC 5382-1) in the patient's Observation history, it prompts the clinician: "TPO antibodies positive [value]. Consider E06.3 (Hashimoto's) as primary or secondary diagnosis."

  • Dual-code scenarios: In many titration encounters, E06.3 (the etiology) and E03.9 (the functional state requiring dose optimization) are listed together. Scribing.io handles sequencing: E03.9 primary when the visit focus is TSH normalization; E06.3 secondary as the etiological basis. This pairing strengthens medical necessity because it demonstrates that the hypothyroidism is autoimmune, progressive, and requires ongoing titration rather than stable maintenance.

Specificity escalation logic in Scribing.io

Patient Data Detected

AI Action

Code Recommendation

No etiology documented; active titration

Accept E03.9 as clinically appropriate

E03.9 (primary)

TPO antibodies positive in Observation history

Prompt: "Consider E06.3 as secondary diagnosis"

E03.9 (primary) + E06.3 (secondary)

Thyroidectomy in surgical history

Prompt: "Consider E89.0 (postsurgical hypothyroidism)"

E89.0 (primary) or E03.9 if surgical event is remote

Amiodarone or lithium in MedicationStatement

Prompt: "Consider E03.2 (drug-induced hypothyroidism)"

E03.2 (primary) + T46.2X5A or T43.595A as external cause

This is not code-suggestion software. This is clinical-documentation architecture that links the ICD-10 code to the supporting evidence in the patient record, ensuring the code is defensible under audit and optimized for first-pass reimbursement.

FHIR R4 Interoperability: Closing the Structured-Data Gap

The root cause of most E03.9 titration denials is not the wrong code—it is unstructured data. The dose-change date is buried in a free-text note. The symptom list is in the HPI but not coded. The lab order has no reference to the Condition or MedicationRequest that justifies it. When the claim hits the payer, the automated edit sees an isolated lab CPT, an E03.9 code, and a date interval that falls within the "routine" window. Denial.

Scribing.io generates HL7 FHIR R4-compliant resources that close this gap:

FHIR resource chain for thyroid-titration encounters

FHIR Resource

Key Fields Populated by Scribing.io

Purpose in Denial Prevention

Condition

code: E03.9; clinicalStatus: active; onsetDateTime

Establishes the diagnosis as active and ongoing, not historical

MedicationRequest

medication: levothyroxine; dosage: 100 mcg; authoredOn: 6/5/2026; priorPrescription (75 mcg)

Documents the dose change with a discrete, queryable date—not free text

Observation (prior TSH)

code: LOINC 3016-3; value: 8.2 mIU/L; effectiveDateTime: 6/3/2026; interpretation: high

Prior lab result with date and interpretation, supporting the need for re-check

Observation (prior Free T4)

code: LOINC 3024-7; value: 0.6 ng/dL; effectiveDateTime: 6/3/2026; interpretation: low

Corroborating low Free T4 strengthens the titration justification

Observation (symptoms)

code: SNOMED 84229001 (fatigue), 8943002 (weight gain), 111360009 (dry skin); effectiveDateTime: 7/1/2026

Structured symptom concordance—the evidence that this is not routine monitoring

ServiceRequest (new TSH)

code: LOINC 3016-3; reasonReference → Condition[E03.9]; supportingInfo → Observation[TSH 6/3], Observation[FT4 6/3], MedicationRequest[levo 100 mcg]

The lab order is linked to the diagnosis, prior results, and dose change. Payer edit can trace the full clinical justification.

Claim

item.diagnosisReference → Condition[E03.9]; item.modifier: 91; item.supportingInfo → ServiceRequest

The claim carries the E03.9 reference, Modifier 91, and a pointer to the ServiceRequest with its full supporting chain

The EHR gap Scribing.io fills

Major EHR platforms (Epic, athenahealth, Oracle Health/Cerner) support FHIR R4 APIs, but they do not auto-generate the linkages described above. Specifically:

  • Epic: The MedicationRequest resource exposes the current prescription but does not discretely capture the "last dose-change date" as a queryable field. The dose-change date is buried in the dosageInstruction.timing or in free-text clinical notes. Scribing.io extracts and structures it.

  • athenahealth: ServiceRequest resources do not automatically populate supportingInfo with prior Observation references. The clinician's lab order exists in isolation. Scribing.io builds the linkage chain.

  • Oracle Health (Cerner): Symptom observations are captured in flowsheets but are not coded with SNOMED CT or linked to the ServiceRequest. Scribing.io maps natural-language symptoms to structured codes and creates the Observation → ServiceRequest reference.

Without these structured linkages, the claim transmits as a flat file: a CPT code, a diagnosis code, and a date. That flat file triggers the automated edit. With Scribing.io, the claim carries a FHIR-native evidence chain that preempts the edit logic entirely.

Modifier 91 and Claim-Line Architecture for Repeat TSH Orders

Modifier 91 (Repeat Clinical Diagnostic Laboratory Test) is the AMA-designated modifier for situations where a lab test is repeated on the same day or within a compressed clinical window to obtain subsequent results. Per the AMA CPT Assistant June 2026 clarification, Modifier 91 is appropriate when:

  1. The same test (e.g., TSH, CPT 84443) is ordered for the same patient.

  2. The repeat is clinically indicated—not due to equipment failure, specimen inadequacy, or confirmation of initial results.

  3. The clinical documentation supports the medical necessity of the repeat.

Why Modifier 91 matters for thyroid titration

Without Modifier 91, payer systems interpret a repeat TSH within 42 days as a duplicate charge. The NCCI (National Correct Coding Initiative) edits may bundle or deny the second test. Modifier 91 signals: "This is a clinically distinct, medically necessary repeat—not a duplicate."

Scribing.io Modifier 91 logic

Trigger Condition

AI Response

Same LOINC code (3016-3 or 3024-7) ordered within 42 days of a prior Observation for the same patient

Modifier 91 recommended. Alert displayed to clinician for confirmation.

Dose-change date present in MedicationRequest and interval < 42 days

Medical-necessity statement auto-generated referencing the dose change and symptom concordance.

No symptoms documented at time of lab order

Hard stop: "Symptom concordance required for repeat TSH within titration window. Please confirm symptoms." This prevents submission of a claim that will be denied.

Claim-line architecture

The final claim line for this encounter reads:

  • CPT: 84443-91 (TSH, repeat)

  • Primary Dx: E03.9

  • Secondary Dx: R53.83 (fatigue), R63.5 (weight gain)

  • Supporting documentation reference: ServiceRequest with linked Observations, MedicationRequest, and medical-necessity narrative

  • Modifier 91 justification: Repeat lab for active levothyroxine titration, 28-day interval, symptoms concordant with sub-therapeutic replacement

This structure satisfies both automated payer edits and manual audit review. The practice receives first-pass payment and has a complete audit trail.

Implementation Checklist for Endocrinology Medical Directors

Deploy the following framework to eliminate E03.9 titration-encounter denials in your practice. Each item maps to a Scribing.io feature that automates the corresponding step.

#

Action Item

Manual Workflow

Scribing.io Automation

1

Audit current E03.9 denial rate on repeat TSH/FT4 orders

Pull denial reports from billing; filter by CPT 84443/84439 + E03.9

Scribing.io dashboard: real-time denial tracking by diagnosis, CPT, and payer edit code

2

Implement symptom concordance documentation standard

Train clinicians to dictate symptoms in Assessment/Plan for every titration visit

AI auto-captures spoken symptoms, maps to ICD-10/SNOMED, inserts into note and FHIR Observations

3

Capture dose-change dates as discrete, queryable data

Manual entry into EHR medication module with date override

AI extracts dose-change date from MedicationRequest history; prompts clinician for confirmation

4

Calculate lab-to-dose-change interval

Coder or MA manually calculates days between dose change and lab draw

Auto-calculated and inserted into the medical-necessity statement

5

Apply Modifier 91 on repeat labs within 42-day window

Coder reviews chart, determines if modifier is appropriate

AI recommends Modifier 91 automatically when repeat-lab criteria are met

6

Build FHIR ServiceRequest linkages

Not possible in most EHR configurations without custom development

Auto-generated: ServiceRequest.reasonReference → Condition, .supportingInfo → Observations + MedicationRequest

7

Pre-validate claims against payer edit rules before submission

Post-submission denial review (reactive)

Pre-submission claim validation engine flags missing elements before the claim leaves the practice

8

Escalate E03.9 to E06.3/E89.0 when etiology is documented

Coder reviews chart for antibody results or surgical history

AI scans Observation history (TPO, surgical records) and prompts specificity escalation

Total estimated implementation time with Scribing.io: 2 weeks. No EHR customization required. FHIR R4 integration uses standard SMART on FHIR launch framework compatible with Epic, athenahealth, and Oracle Health.

Ready to eliminate E03.9 titration denials? Book a 15-minute demo to see automatic Symptom Concordance capture, TSH/Free T4 LOINC mapping, dose-change interval checks, and Modifier 91 prompts with FHIR-native claim linkages—built for 2026 payer edit logic. Schedule at Scribing.io →

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Still not sure? Book a free discovery call now.

Frequently

asked question

Answers to your asked queries

Can we get started today?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

Image

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.

Clinical Precision.
Zero Documentation Debt

Finish Your Charts - Go Home on Time.