• Another week, another opportunity to learn something new in anesthesia pain management. This week’s spotlight focuses on an unusual but increasingly common technique used for post-operative pain control: fascial plane blocks—with a special focus on the Erector Spinae Plane (ESP) block.

    What Is a Fascial Plane Block?

    Fascial plane blocks are regional anesthesia techniques where local anesthetic is injected between layers of fascia, rather than directly targeting a single named nerve. The medication spreads along the fascial plane, allowing coverage of multiple nerve branches and dermatomes.

    Why the ESP Block Is Considered Unusual

    The Erector Spinae Plane (ESP) block is considered unusual because it is performed at a location distant from the spinal cord and major nerve roots, yet it provides broad thoracic or lumbar analgesia. The block is placed deep to the erector spinae muscle, allowing cranio-caudal spread of anesthetic.

    Common uses include:

    • – Thoracic surgery
    • – Rib fractures
    • – Breast surgery
    • – Abdominal and colorectal procedures
    • – Spine surgery

    Fascial Plane Block CPT Codes

    Fascial plane blocks, including ESP blocks, are reported using the following CPT codes:

    Thoracic (ESP) Fascial Plane Block Codes

    CPT 64466 – Single injection, (unilateral)

    CPT 64467 – Continuous catheter (unilateral)

    CPT 64468 – Single injection, (bilateral)

    CPT 64469 – Continuous catheter (bilateral)

    Lumbar & Sacral (ESP) Fascial Plane Block Code

    CPT 64999 – Unlisted Procedure

    Documentation Requirements

    To support billing for fascial plane blocks, documentation should clearly include:

    • – Indication for post-operative pain control
    • – Anatomical level(s): thoracic or lumbar
    • – Single-shot versus continuous catheter technique
    • – Laterality when applicable
    • – Separate documentation from the surgical anesthesia record
    • – Timing of the block (pre-op, intra-op for post-op pain, or post-op)

    Common Audit Pitfalls

    A frequent audit issue occurs when documentation simply states ‘ESP block performed’ without specifying the level, technique, or indication for post-operative pain. Incomplete documentation may result in denials or downcoding.

    Closing Thoughts

    Fascial plane blocks like the ESP block highlight how anesthesia pain management continues to evolve. For coders and auditors, understanding both the clinical intent and the CPT coding requirements is essential to ensure accurate reporting and compliance.

    DISCLAIMER:  Chart Talk:  Anesthesia Coding Conversations is intended for educational and informational purposes only. The information presented reflects the sole interpretation and professional opinion of the presenter. It does not represent the views or official guidance of my employer, the Centers for Medicare & Medicaid Services (CMS), the American Medical Association (AMA), or any other regulatory or governing body.

    Every reasonable effort has been made to ensure the accuracy of the information provided at the time of publication. However, coding guidelines, regulations, and payer policies are subject to change. It is the responsibility of the reader or participant to verify current guidance and apply professional judgment when making coding and billing decisions.

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • Here we are again—another week laid out in front of us like a blank page.
    No matter how last week went, this one arrives quietly with an invitation: try again.

    Another chance to reset.
    Another chance to grow.
    Another chance to become a little more of the person you desire to be.

    You don’t have to conquer everything at once. Sometimes the biggest victories are small and unseen—showing up when you’re tired, choosing peace over pressure, believing in yourself even when no one else is clapping yet.

    This week, maybe the goal isn’t perfection.
    Maybe it’s consistency.
    Or courage.
    Or simply not giving up on yourself.

    So pause for a moment and ask yourself:

    What are you hoping to conquer this week?

    • A fear you’ve been avoiding?
    • A habit you want to build—or break?
    • A goal you’ve been putting off because self-doubt got too loud?
    • Or maybe just learning to give yourself a little more grace?

    Whatever it is, remember this:
    You are allowed to grow at your own pace.
    You are allowed to try again.
    And you are absolutely capable of more than you think.

    Here’s to another week.
    Another chance.
    And the quiet courage it takes to keep moving forward—one step at a time. 🌱

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • DISCLAIMER:  Chart Talk:  Anesthesia Coding Conversations is intended for educational and informational purposes only. The information presented reflects the sole interpretation and professional opinion of the presenter. It does not represent the views or official guidance of my employer, the Centers for Medicare & Medicaid Services (CMS), the American Medical Association (AMA), or any other regulatory or governing body.

    Every reasonable effort has been made to ensure the accuracy of the information provided at the time of publication. However, coding guidelines, regulations, and payer policies are subject to change. It is the responsibility of the reader or participant to verify current guidance and apply professional judgment when making coding and billing decisions.

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • Every year, CPT® and the ASA coding committee introduce updates intended to clarify, modernize, and improve how anesthesia services are coded and reported. The 2026 ASA code changes are no exception: several revisions reflect evolving practice, enhanced specificity, and efforts to support more accurate coding across a variety of clinical scenarios.

    That said, as with any major update, not every change aligns perfectly with real-world practice. There are a few revisions in the 2026 update that—based on clinical workflow, typical anesthesia practice, or the underlying procedure logic—may not seem to fit well with the procedures they are intended to describe. These areas have raised questions among anesthesia coders, auditors, and clinicians alike, and I hope they will be revisited, clarified, or refined in future guidance.

    In the attached PowerPoint, I will walk through the key 2026 ASA changes, highlight the areas that are causing confusion or concern, and offer insight into how to interpret and apply these changes in your coding and documentation.

    Disclaimer:
    Chart Talk: Anesthesia Coding Conversations is intended for educational and informational purposes only. The content shared does not constitute legal, billing, compliance, or reimbursement advice. Coding, billing, and reimbursement decisions should be based on official sources such as CPT®, ICD-10-CM, ASA guidelines, payer policies, and individual facility policies, as well as the specific documentation in the medical record. Users are encouraged to consult authoritative resources and/or their compliance department for guidance applicable to their organization.

  • Hypothermic circulatory arrest (HCA) is one of the most complex and high-risk techniques used in cardiac and major vascular surgery. Because of its complexity—and its frequent confusion with hypothermia alone—it is also an area where anesthesia coding errors commonly occur.
    This post breaks down what HCA ishow it differs from hypothermia without arrest, and when ASA code 00563 is appropriate.


    What Is Hypothermic Circulatory Arrest?

    Hypothermic circulatory arrest is a planned, intentional cessation of systemic blood circulation, achieved after cooling the patient to a deep hypothermic state (typically ≤20°C / 68°F).

    Key elements of HCA:

    • Complete stoppage of circulation
    • Deep hypothermia induced via cardiopulmonary bypass
    • Neuroprotection achieved by reducing cerebral metabolic demand
    • Time-limited arrest period, followed by controlled reperfusion and rewarming

    This technique is most often used when bloodless surgical fields are required—such as in complex aortic arch repairs—where clamping alone is not sufficient.


    Hypothermia vs. Hypothermic Circulatory Arrest

    (Why this distinction matters for coding)

    Hypothermia OnlyHypothermic Circulatory Arrest
    Cooling used as a protective measureCooling plus total circulatory arrest
    Circulation continuesCirculation is completely stopped
    Common during routine cardiac bypassUsed only in select high-risk cases
    Not separately reportableSeparately reportable with ASA 00563

    Important: Hypothermia alone—even deep hypothermia—does not qualify for ASA 00563 unless circulatory arrest is clearly documented.


    What Is ASA 00563?

    ASA 00563 represents anesthesia services involving hypothermic circulatory arrest.
    It is not an add-on for hypothermia, and it should not be reported unless the case meets strict clinical and documentation criteria.

    Typical procedures where HCA may apply:

    • Aortic arch reconstruction or replacement
    • Complex thoracic aortic aneurysm repair
    • Certain congenital cardiac surgeries requiring bloodless fields

    Documentation Requirements to Support ASA 00563

    Clear, explicit documentation is critical. The anesthesia record should support all of the following:

    1. Intentional Circulatory Arrest

    • Explicit wording such as:
      • “Circulatory arrest initiated”
      • “Systemic circulation stopped”
    • Vague statements like “deep hypothermia achieved” are not sufficient

    2. Arrest Start and Stop Times

    • Precise start and end times of circulatory arrest
    • Duration documented in minutes

    3. Core Temperature

    • Documentation of deep hypothermia (often ≤20°C)
    • Recorded via reliable monitoring (e.g., nasopharyngeal, bladder, or esophageal probe)

    4. Reperfusion and Rewarming

    • Documentation that circulation was restarted
    • Controlled rewarming process noted

    Common Coding Pitfalls

    🚫 Do not report ASA 00563 when:

    • Hypothermia is used without stopping circulation
    • Only cardiopulmonary bypass is documented
    • Arrest time is implied but not clearly stated
    • Surgeon documentation is vague and anesthesia record lacks confirmation

    ✅ Do report ASA 00563 when:

    • Circulatory arrest is clearly intentional and documented
    • Arrest duration is specified
    • Deep hypothermia is confirmed
    • The anesthesia record independently supports the service

    Audit Tip: Defending ASA 00563

    When preparing for an audit:

    • Ensure anesthesia documentation stands alone
    • Do not rely solely on operative reports
    • Verify arrest times match perfusion and anesthesia records
    • Use consistent terminology across the case record

    A simple checklist approach can dramatically reduce denials and post-payment recoupments for this high-risk code.


    Final Takeaway

    ASA 00563 is reserved for true hypothermic circulatory arrest—not hypothermia alone.
    The distinction hinges on complete cessation of circulation, supported by clear, time-based anesthesia documentation.

    Accurate coding protects both compliance and reimbursement—and ensures that the complexity of these high-risk anesthesia services is properly recognized.


    DISCLAIMER:  Chart Talk:  Anesthesia Coding Conversations is intended for educational and informational purposes only. The information presented reflects the sole interpretation and professional opinion of the presenter. It does not represent the views or official guidance of my employer, the Centers for Medicare & Medicaid Services (CMS), the American Medical Association (AMA), or any other regulatory or governing body.

    Every reasonable effort has been made to ensure the accuracy of the information provided at the time of publication. However, coding guidelines, regulations, and payer policies are subject to change. It is the responsibility of the reader or participant to verify current guidance and apply professional judgment when making coding and billing decisions.

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • Brachial Plexus – CPT 64415/64416

    A brachial plexus nerve block is a regional anesthesia technique where local anesthetic is injected near the brachial plexus (a network of nerves for the arm) in the neck, above the collarbone, or armpit to numb the entire arm for surgery or to manage chronic pain, often as alternative to general.  When brachial plexus is used for acute post op pain management 

    How does it work and its purpose?

    • Blocks Pain:  Temporarily stops pain and movement in the arm by numbing the nerve bundle.
    • Surgical Anesthesia:  Allows for awake or sedated surgery on the arm shoulder, or hand, avoiding general anesthesia side effects.
    • Pain Management:  Provides relief for arm and shoulder pain.

    Common Approaches:

    • Interscalene:  Near the neck (between scalene muscles), best for shoulder surgery.
    • Supraclavicular:  Above the collarbone, excellent for elbow, wrist, and hand surgery.
    • Infraclavicular:  Below the collarbone
    • Axillary:  In the armpit, for hand, wrist, and forearm procedures.  

    Procedure & Guidance:

    A doctor uses landmarks and often ultrasound to guide a needle to inject anesthetic near the nerves, sometimes placing a catheter for continuous pain relief.  Ultrasound is bundled with code 64415/64416.

    Axillary Nerve Block – CPT 64417

    An ancillary nerve block is used for post op pain control, often for surgeries in the forearm, hand, wrist, or shoulder.  It is billed for a single injection, providing pain relief by temporarily interrupting nerve signals, and requires specific documentation showing it’s separate from the main surgical anesthetic for. Post-op pain management.

    How it Works for Post-Op Pain:

    • The axillary nerve block targets the axillary nerve, a key nerve from the brachial plexus, located near the armpit.
    • Anesthetic is injected near the nerve, often within a fascial compartment, to numb the area and block pain signals.
    • It’s a common component of multimodal pain strategies to reduce reliance on opioids.

    Common Usage Examples:

    • Pain control after wrist fractures, elbow surgeries or shoulder surgeries.
    • Part of a comprehensive approach (along with other blocks like the suprascapular nerve block) for shoulder analgesia.

    * Axillary approach to Brachial Plexus is coded as 64415 (typically shoulder cases).  True Axillary Blocks target the Axillary nerve and are coded 64417 (typically forearm/wrist/hand procedures).  Review the block note to confirm the targeted nerve

    Suprascapular Nerve Block – CPT 64418

    A suprascapular nerve block (SSNB) is a highly effective technique for managing acute postoperative shoulder pain, especially after arthroscopic procedures, by injecting local anesthetic around the nerve that supplies about 70% of the shoulder’s sensation, significantly reducing opioid needs, nausea, and pain scores, and allowing for earlier rehabilitation. It’s a safe alternative for patients with lung issues who can’t have general nerve blocks and can be combined with other blocks (like axillary) for even better results, though it’s less effective than a full interscalene block but offers better safety. 

    How It Works:

    • Injection: A doctor injects a local anesthetic (like lidocaine/bupivacaine) near the suprascapular nerve, often guided by ultrasound for precision.
    • Pain Interruption: The anesthetic temporarily blocks pain signals from the shoulder joint to the brain.
    • Safer Alternative: Avoids phrenic nerve block (diaphragm paralysis) seen with interscalene blocks, making it ideal for patients with lung disease, notes ASRA Pain Medicine.

    When It’s Used:

    • Arthroscopic shoulder surgeries (rotator cuff repair, etc.).
    • Chronic shoulder pain (arthritis, frozen shoulder, tendonitis). 

    Techniques:

    • Posterior Approach: Common, targeting the nerve at the suprascapular notch.
    • Anterior Approach: Also described and effective.
    • Combination: Often paired with an axillary nerve block (SSNB+ANB) for comprehensive pain relief, though it may not surpass a standard interscalene block (ISB) but offers fewer side effects like breathing issues. 

    Suprascapular Nerve Block – CPT 64418

    A suprascapular nerve block (SSNB) is a highly effective technique for managing acute postoperative shoulder pain, especially after arthroscopic procedures, by injecting local anesthetic around the nerve that supplies about 70% of the shoulder’s sensation, significantly reducing opioid needs, nausea, and pain scores, and allowing for earlier rehabilitation. It’s a safe alternative for patients with lung issues who can’t have general nerve blocks and can be combined with other blocks (like axillary) for even better results, though it’s less effective than a full interscalene block but offers better safety. 

    How It Works:

    • Injection: A doctor injects a local anesthetic (like lidocaine/bupivacaine) near the suprascapular nerve, often guided by ultrasound for precision.
    • Pain Interruption: The anesthetic temporarily blocks pain signals from the shoulder joint to the brain.
    • Safer Alternative: Avoids phrenic nerve block (diaphragm paralysis) seen with interscalene blocks, making it ideal for patients with lung disease, notes ASRA Pain Medicine.

    When It’s Used:

    • Arthroscopic shoulder surgeries (rotator cuff repair, etc.).
    • Chronic shoulder pain (arthritis, frozen shoulder, tendonitis). 

    Techniques:

    • Posterior Approach: Common, targeting the nerve at the suprascapular notch.
    • Anterior Approach: Also described and effective.
    • Combination: Often paired with an axillary nerve block (SSNB+ANB) for comprehensive pain relief, though it may not surpass a standard interscalene block (ISB) but offers fewer side effects like breathing issues. 

    DISCLAIMER:  Chart Talk:  Anesthesia Coding Conversations is intended for educational and informational purposes only. The information presented reflects the sole interpretation and professional opinion of the presenter. It does not represent the views or official guidance of my employer, the Centers for Medicare & Medicaid Services (CMS), the American Medical Association (AMA), or any other regulatory or governing body.

    Every reasonable effort has been made to ensure the accuracy of the information provided at the time of publication. However, coding guidelines, regulations, and payer policies are subject to change. It is the responsibility of the reader or participant to verify current guidance and apply professional judgment when making coding and billing decisions.

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • I’ve been asking myself a question lately—one that I think many educators, writers, and content creators ask at some point:

    Is this really helping anyone?

    I spend hours researching, writing, creating tip sheets, and sharing knowledge through this blog. Yet sometimes… it feels quiet.
    No comments.
    Little interaction.
    No visible feedback.

    And in those moments, it’s easy to wonder:
    Is this beneficial? Should I continue spending my time doing this if no one is interacting?

    Here’s what I’ve come to realize.

    Quiet Does Not Mean Useless

    Not everyone who benefits from something speaks up. Many people read quietly. They save posts. They bookmark resources. They revisit information when they need it most. Especially in healthcare and coding, people are often overwhelmed, busy, or unsure of what to say—but that doesn’t mean the information isn’t valuable.

    I remind myself that education isn’t always loud. Sometimes its impact is silent.

    Not Every Seed Sprouts Immediately

    This blog wasn’t created for instant gratification. It was created to educate, support, and guide—especially those navigating anesthesia coding, compliance, and documentation who may feel unsure or alone.

    Some seeds take time. Some won’t sprout until months—or even years—later. And some may help someone in a way I’ll never see or hear about.

    That doesn’t make the effort wasted.

    Why I Started This in the First Place

    I didn’t start this blog for likes or comments. I started it because:

    • I’ve spent decades in this field
    • I’ve made mistakes and learned from them
    • I know how confusing anesthesia coding can be
    • And I wanted to create a place that made it just a little easier for someone else

    That purpose hasn’t changed—even on the quiet days.

    So… Should I Continue?

    That’s the question, isn’t it?

    And my answer—at least for now—is yes.

    Because if even one person finds clarity, confidence, or reassurance from something I’ve shared, then it is helping someone. Even if I never know their name. Even if they never comment.

    Sometimes impact isn’t measured by interaction. Sometimes it’s measured by consistency, intention, and heart.

    If you’re reading this and you’ve ever questioned whether your efforts matter—this is your reminder:
    They do.

    And

    that’s reason enough to keep going.

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • Post-operative pain blocks continue to be an area of confusion for many coders, auditors, and providers—particularly when it comes to what is separately reportable, which CPT codes apply, and what documentation is truly required to support billing. This multi-part series is designed to break post-op pain block coding down into clear, practical segments, beginning with a foundational overview of the applicable CPT codes and the documentation elements that must be present to support compliant billing. Each installment will build on the last, addressing common scenarios, compliance pitfalls, and audit-focused considerations to help ensure post-operative pain management services are coded accurately, defensibly, and consistently.

    What is required in the documentation in order for the post op block to be billable?

    1. Who placed the block? We as coders and auditors cannot assume that the attending Anesthesiologist/CRNA for the anesthesia sedation service also performed the block. The block note documentation must clearly identify the specific provider or who placed the block.  
    2. Who requested the block? The documentation for the block should clearly indicate that it was placed at the surgeon’s request. Phrases such as “per surgeon’s request” or “for post-operative pain management, at the request of the surgeon” are commonly used and help establish this. This language is important to support medical necessity in the event of payer questions or audits. Ultimately, the surgeon is responsible for post-operative pain management and must delegate that responsibility when appropriate. 
    3. What type of block? Coders and auditors should identify the block type by looking for the specific name of the block performed — for example, interscalene, adductor canal, femoral, intercostal, etc. 
    4. What delivery method was used to administer the post-operative pain procedure? The documentation must clearly indicate whether it was a single-shot injection or a continuous catheter technique. CPT selection should be based on the documented method of delivery. 
    5. Where was the block placed? Accurate code selection depends on the anatomical location documented in the documentation Specifically, the documentation should clearly identify the nerve or region that was injected, infused, or blocked. For example, a block labeled as “Saphenous” may be reported using CPT 64447 (Femoral nerve block) if performed in the mid-thigh region (Adductor Canal), or CPT 64450 (Other peripheral nerve or branch) if performed below the knee. Additionally, the documentation must specify laterality—whether the block was performed on the left, right, or both sides—to ensure correct coding. 
    6. Why was the block placed? Anesthesiologists must clearly document the indication for the block. When a block is performed specifically for post-operative pain and is separately billable as a fee for service, it requires distinct documentation that supports its medical necessity as a separate service. If the documentation is unclear or leaves room for interpretation regarding whether the block was part of the primary anesthetic, coders should query the clinician for clarification to ensure accurate coding and compliance. 
    7. When was the block placed? The AMA (American Medical Association) has clarified that anesthesia time can be billed for the period spent placing a block, provided the block placement occurs after induction of the primary anesthetic but before emergence. If the block is placed after anesthesia start time but before induction, discontinuous anesthesia time should be applied, meaning the time spent performing the block is excluded from the total billable anesthesia time. To accurately determine if block time is billable or if discontinuous time must be applied, coder should review the following key documentation elements:   Start time of the block injection/placement of catheter   * Stop time of the block injection/catheter   Induction time (primary anesthetic)  
    8. Was the block performed under ultrasound guidance? In 2025, most block codes now include ultrasound guidance, but there are some (64450) that still don’t so it is important to know what type of verbiage we need in order to bill 76942. Ultrasound guidance may be separately billable when it is not included in the description of the nerve block and is adequately supported by documentation. To meet medical necessity requirements, the ultrasound image must be retained in the patient’s permanent medical record and clearly identify the patient and date of service.  The documentation should include language similar to the following examples:  Ultrasound guidance used to guide the needle for satisfactory placement (e.g. “Under US, needle guided and appropriately placed.” “Ultrasound guidance used for needle placement”). Ultrasound guidance used to view medication diffusion (e.g., “US used to visualize spread of anesthetic,” “Medication spread viewed under U/S”). 

    Below is a quick overview of different blocks and there CPT Codes. In the Post-Op Block Series, I will be covering different blocks each week.

    Description2026 Code
    Brachial Plexus64415
    Brachial Plexus 64416
    Axillary Nerve*64417
    Suprascapular Nerve64418
    Intercostal Nerve, Single Level64420
    Intercostal Nerve (each additional level)64421
    Ilioinguinal, iliohypogastric Nerves64425
    Pudendal Nerve64430
    Paracervical (uterine) Nerve64435
    Sciatic Nerve64445
    Sciatic Nerve64446
    Femoral Nerve64447
    Femoral Nerve64448
    Lumbar Plexus; Continuous64449
    Other Peripheral Nerve or Branch64450
    Sacroiliac Joint64451
    Genicular Nerve64454
    Paravertebral block (PVB) (paraspinous block)64461
    Paravertebral block (PVB) (paraspinous block)64462
    Paravertebral block (PVB) (paraspinous block)64463
    Thoracic Fascial Plane Block Codes***64466
    Thoracic Fascial Plane Block Codes64467
    Thoracic Fascial Plane Block Codes64468
    Thoracic Fascial Plane Block Codes64469
    Lower Extremity Fascial Plane Blocks64473
    Lower Extremity Fascial Plane Blocks64474
    Abdominal Fascial Plane Blocks (TAP Blocks)64486
    Abdominal Fascial Plane Blocks (TAP Blocks)64487
    Abdominal Fascial Plane Blocks (TAP Blocks)64888
    Abdominal Fascial Plane Blocks (TAP Blocks)64889
    Unlisted64999
    * Axillary approaoch to Brachial Plexus is coded as 64415 (typically shoulder cases).  True Axillary Blocks target the Axillary nerve and are coded 64417 (typically forearm/wrist/hand procedures).  Review block note to confirm targeted nerve

    Disclaimer:
    Chart Talk: Anesthesia Coding Conversations is intended for educational and informational purposes only. The content shared does not constitute legal, billing, compliance, or reimbursement advice. Coding, billing, and reimbursement decisions should be based on official sources such as CPT®, ICD-10-CM, ASA guidelines, payer policies, and individual facility policies, as well as the specific documentation in the medical record. Users are encouraged to consult authoritative resources and/or their compliance department for guidance applicable to their organization.

  • The first week of a new year always carries a special kind of energy. It’s a pause and a push at the same time—a moment to reflect on where you’ve been and a chance to decide where you’re going.

    So let me ask you:

    How did your first week go?
    Did it feel calm and intentional—or rushed and overwhelming?
    Did you ease into the year, or did it hit the ground running before you had time to breathe?

    Did You Set Goals—or Just Hopes?

    There’s a difference between hoping things will change and deciding they will.

    Maybe you set clear goals:

    • Professional growth
    • Learning something new
    • Protecting your time
    • Saying “no” more often
    • Saying “yes” to yourself

    Or maybe you’re still figuring it out—and that’s okay too. The first week doesn’t have to come with all the answers. Sometimes clarity comes after you give yourself permission to slow down and think.

    What Are Your Priorities This Year?

    Not just work priorities—but life priorities.

    • What deserves your energy?
    • What needs firmer boundaries?
    • What are you ready to let go of?

    This is the year to stop putting yourself last. Productivity means nothing if you’re burned out, disconnected, or constantly chasing someone else’s expectations.

    Is This the Year You Chase Your Dreams?

    Be honest with yourself.

    Is this the year you:

    • Go after the certification you’ve been thinking about?
    • Start (or grow) the blog, business, or creative project?
    • Speak up, apply, or step into a role you’ve quietly wanted?
    • Believe that you are ready—even if you’re still a little scared?

    Fear doesn’t mean you’re not capable. It usually means you care.

    A Gentle Reminder

    You don’t have to do everything this week—or even this month.
    Progress is built in small, intentional steps, not overnight transformations.

    What matters is this:

    • You showed up.
    • You reflected.
    • You started.

    And that alone makes this year different already.

    ✨ Here’s to a year of clarity, courage, growth, and choosing yourself.
    Tell me—how did your first week of the year go?

    — Dianne
    Chart Talk: Anesthesia Coding Conversations

  • You know you’re capable.
    You know you can do it.

    And yet… you hesitate.

    Not because you lack the skills.
    Not because you haven’t put in the work.
    Not because you’re unprepared.

    So what’s really holding you back?

    Is it the fear of being told no?
    The fear of not being chosen?
    The quiet voice that whispers you’re “not good enough,” even though your experience says otherwise?

    Sometimes the hardest part of going after a dream isn’t the work—it’s giving yourself permission to try.

    We talk ourselves out of opportunities before anyone else ever can. We convince ourselves that now isn’t the right time, that we need one more certificationone more yearone more sign before we’re allowed to take the next step. But deep down, we already know we’re ready.

    Growth requires courage. Not the absence of fear—but the decision to move forward despite it.

    So ask yourself:

    • What am I afraid will happen if I try?
    • What am I risking if I don’t?
    • Whose approval am I waiting for?

    You already know what you want.
    You already know what you’re capable of.

    The real question is this:
    What would happen if you stopped letting fear make the decisions for you?