HIA Launches Buddy Up Program for New Hires
This past year, HIA implemented “Buddy Up,” a program designed to help the new hire have a smooth transition into their new HIA roles with the assistance of a “buddy.”
What is a Buddy?
The Buddy is simply a peer who can guide the new hire in order to make them feel more comfortable. We are very proud of this program and have many success stories that we would like to share. Take a look at the wonderful feedback we have received below.
Thank you to all of our amazing People Behind The Numbers who have volunteered their time to be a buddy!
Thank you! I wanted to let you know that the buddy program was VERY helpful for me. My Buddy was so kind and always there when I need anything or had any questions. It was so nice to have this communication with a coworker, it helped me to feel like I had made a friend and that I could reach out to them if I needed. My Buddy would provide me with suggestions and would always make sure I wasn’t having any issues. The support was awesome!
My buddy is great. She has been keeping track of me. She is super friendly and helpful. This is a great program. Thank you.
I appreciate having someone to go to with my general questions and not have to bother my Manager.
I have asked questions for advice on things (not specific charts – just in general) and she has followed up. It’s nice to have the communication with someone too.
At first, I admit I was shocked that she was not an inpatient coder, I was thinking how we are going to relate. Then I reread what the buddy system was all about. So now I am looking at my buddy as my friend at work and we are sharing and getting along and sharing life stories. So yes, it’s going well.
Everything is going well with my buddy, she has been helpful and has answered lots of questions for me.
Even after my orientation ended, my Buddy has continued to be very kind to me. I really appreciate her support.
My Buddy frequently checked in on me and would always make sure I wasn’t having any issues. The support was awesome!
We have finished with the step-by-step coding tidbits on coding of spinal fusions. If you were not able to catch Parts 1-13 of this series focused on spinal fusions, please visit hiacode.com/topics/series/spinal-fusion-coding/.
In Part 12, we focused on intra-operative peripheral neuro monitoring used during spinal fusion surgery. In Part 13, we are going to focus on harvesting of autograft and is it coded. Remember in Part 6, we learned that autograft is bone from the patient.
In Part 11, we focused on identifying the computer assisted navigation used during spinal fusion surgery. In Part 12, we are going to focus on intra-operative peripheral neuro monitoring.
In Part 10, we focused on identifying whether or not hardware from a previous spinal fusion is coded. In Part 11, we are going to discuss computer assisted navigation.
In Part 9, we focused on identifying if decompression was also performed and if so, on which body part. In Part 10, we are going to focus on identifying if hardware was removed from a previous fusion site.
In Part 8, we focused on identifying if a discectomy was performed, and if so, if it was a partial or a total discectomy. In Part 9, we are going to focus on identifying if a decompression was performed, and if so, was it of the spinal cord, spinal nerves or both?
In Part 7, we focused on identifying any instrumentation that may be used during a spinal fusion. In Part 8, we are going to focus on identifying if a discectomy is performed and if this is an excision or a resection of the disc.
In Part 6, we focused on identifying the type of bone graft product used for the spinal fusion. In Part 7, we are going to focus on identifying any instrumentation or device used.
In Part 5, we focused on identifying the approach being used for the spinal fusion. In Part 6, we are going to focus on identifying the type of bone graft used for the spinal fusion.
In Part 4, we focused on determining the spinal column being fused. In Part 5, we are going to focus on identifying what approach is being used to complete the spinal fusion (anterior, posterior or both).
In Part 3, we focused on determining the level of the fusion(s) and how to determine the number of vertebrae fused. In Part 4, we are going to focus on identifying which column is being fused (anterior, posterior or both).
Part 3: Spinal Fusion Coding — Determine the Level(s) or Region of Fusion and Number of Vertebrae Fused
In Part 1, we learned the diagnoses associated with the need for spinal fusions, and in Part 2 the need to identify if the fusion is an initial or refusion of the vertebrae. In Part 3, we are going to focus on determining the level(s) of fusion, as well as the number of vertebrae fused.
In Part 2, we are going to look at the differences between initial fusion and a refusion. In ICD-9, there were specific codes to show if the fusion was an initial fusion, or if it was a refusion. In ICD-10-PCS, initial fusions and refusion procedures are coded to the same root operation “fusion.”
This is Part 1 of a 14 part series focusing on education for spinal fusions. Spinal fusion coding is a tough job for coders. There are so many diseases/disorders that result in the need for spinal fusion, and even more choices in reporting the ICD-10-PCS codes.
The official definition from the Centers for Medicare & Medicaid Services (CMS) states that a Medicare overpayment is a payment that exceeds amounts properly payable under Medicare statutes and regulations. When Medicare identifies an overpayment, the amount becomes a debt you owe the Federal government.
The question asked in a physician query may be the most important element of the document. Query questions need to be as simple and concise as possible. The physician should have no doubt what the coder is asking.
Coding complications of transplanted organs has always been a coding dilemma. With the implementation of ICD-10-CM that didn’t change. However, coders have multiple directives to help in determining what a complication of the transplant is vs. non-transplant conditions and diseases.
We interviewed our most productive coders, reviewers and members of our education team, asking them what steps they take to find a rhythm that works for them. This week, we talked with Beth Martilik, MA, RHIA, CDIP, CCS, Assistant Director of Education, about the steps she takes to find her routine.
With the implementation of ICD-10-CM came more codes for reporting many different conditions and diseases, and atrial fibrillation is one of those. For many years there was only one code available for reporting this condition, even when the physician further specified the type of atrial fibrillation that the patient had. In ICD-10-CM, there are four codes to report atrial fibrillation.
We have a case where the physician removes mucoid casts found during bronchoscopy. We have also seen mucus plugs removed during bronchoscopy. The MD performs bronchial washings then removes a large amount of tenacious and thick mucoid casts via bronchoscopy. Is this coded drainage, extirpation or excision? What body part is used?
The key to making the query process more efficient is to look for words or documentation while reviewing the record that may signal a potential query opportunity and to note the finding at that time. By the time a coder reaches the end of a record, documentation may have been found to eliminate the need for the query.
Question: This patient is noted to have “Lymphangitic carcinomatosis of lungs with mediastinal lymph nodes.” How would I code the diagnosis? Would I code metastatic cancer to the lung (C78.01) or metastatic cancer to the lymph nodes (C77.1)?
Coding these can be challenging for coders when trying to decipher the operative notes and terms that are used. The physicians are still using the terms excision and resection interchangeably and review of the entire operative note is required to select the appropriate root operation. Remember, it is the coder’s responsibility to determine the root operation based on the details from the physician in the operative report.
We interviewed our most productive coders and reviewers, asking them what steps they take to find a rhythm that works for them. This week, we talked with Valerie Abney, CDIP, RHIT, CCS, about the steps she takes to find her routine.
Osteoporosis alone is responsible for over a million fractures every year. Stress fractures are not as common but they do occur. There are more than 1 million total joint replacements in the U.S. each year, so there was a need to create codes for injuries that occur around or near the prosthesis. These are called “periprosthetic” fractures.
Back in April, the Office of the Inspector General (OIG) published a report detailing its findings from a review of two groups of high-risk diagnosis codes, acute stroke and major depressive disorder. The objective was to determine whether selected diagnosis codes submitted to the Centers for Medicare and Medicaid Services for use in CMS’s risk adjustment program complied with Federal requirements.
There seems to be differences of opinions on the issue of a 40w0day gestation Can you clarify if P08.21 should be assigned for 40w0day infant or if it would not be assigned unless the infant’s gestation age was 40w1day or greater?
Coders may find situations where a patient is documented as meeting SIRS or sepsis criteria, or has some clinical indicators reflective of possible sepsis, but the physician never documents sepsis as a diagnosis. Should the coder always query for sepsis in these instances?
In this example, would it be appropriate to code the complication code T82.03XA, Leakage of heart valve prosthesis, initial encounter as the principal diagnosis over the HFpEF (heart failure exacerbation) code?