Tuesday, April 22, 2014

More coding positions Nurses! Are you checking these out?

Kyle JohnstonI
Remote Inpatient Coder Needs
Kyle Johnston, Regional Director at CSI Healthcare IT
904.338.9515 ext. 223



Hi Joyce, 

Even though it's official, ICD-10 is delayed, there are still plenty of remote coding contract needs. Below I have listed my current openings in hopes that you know someone in your network who might be interested, given your expertise.

All of the roles are 100% remote, contract based. The candidate would work for my firm, but provide coding for our client. We pay on a hourly basis, pay weekly, provide laptop and audit internally.

An internal test, interview and reference check will apply. Thanks!

1. A University Hospital in New Jersey is looking for an IP coder to come on contract for 6 months plus, 40 hours per week and flexible schedule.
2. A General Hospital in Florida is looking for an IP coder to come on contract for an extended period of time, 30 - 40 hours per week, flexible schedule and they have an assessment test.
3. A Health System in Michigan is looking for an IP coder to come on contract for an extended period of time, 40 hours per week and flexible schedule. 

4. A Teaching Hospital in Minnesota is looking for an IP coder and Lead coder to come on contract for dual coding on an extended period of time, 40 hours per week and flexible schedule. They have a Level 1 Trauma center, so experience there is a plus. Also, the candidate must of already coded ICD-10 before and they must have a AHIMA only credential or certification.

Tuesday, April 15, 2014

RN-Coders Show Your Interest! in Remote Coding Jobs

Weekly REMOTE Job Report - 4/15/14 - 31 Remote Job Openings!! 

Please send resumes to blansiquot@kforce.com #medicalcoding #jobs

Bertram Mr.B Lansiquot
★ Healthcare Executive Helping Medical Coders Find Successful Careers ★ Send Resumes to blansiquot@kforce.com ★Top Contributor
Hi Everyone, 

We partner with 450+ health systems for long-term REMOTE opportunities with: 

* Great Compensation Plan 
* Insurance: Medical, dental, vision, plus more 
* FREE ICD-10 Education from your 1st day 
* PTO, New Coding Books, Coding Hotline, 401k, Employee Stock, many more. 

Please contact me directly for details!! 

Must have: 
* 3 years of Recent Acute Care Experience (not insurance, military, or billing) 
* Must be fully certified (either CCS, CPC, RHIT, RHIA, CPC-H, CCS-P, CTR) 

FULL TIME Opportunities: 
Remote: Coding Lead with Inpatient/Outpatient/ER Experience
Remote: Coding Supervisor
Remote: ICD-10 Trainer
Remote: Inpatient Coder - 15 Openings
Remote: Inpatient/Outpatient Coder - 7 Openings
Remote: Inpatient/Outpatient/ER Coder - 2 Openings
Remote: Outpatient Psych Coder
Remote: Outpatient/ER Coder
Remote: Physician Coder with EPIC Experience - 2 Openings

Remember, you can also score a referral bonus (up to $1000) for any referral hired by Kforce!! 
Send my contact information to your friends and coworkers!! 

Please send resumes to 
blansiquot@kforce.com 

Please Note: All of these positions have prehire requirements. 

Thanks for your time, 
Bertram

Wednesday, April 9, 2014

How to Prevent Another ICD10 Delay

 ICD10 Watch
by CARL NATALE


How to inoculate ICD-10 coding from another delay

Let's be honest. We shouldn't be surprised that an ICD-10 delay became law. It's a concept that is easier to hate than embrace.
The ICD-10 upgrade will be expensive, it's hard to explain without boring people, and a lot of the codes are used as punchlines by politicians. So you can understand why no politician stood up and defended ICD-10 coding as a standard during the debate over the “Protecting Access to Medicare Act of 2014” debate.
And no one ever will unless the healthcare IT industry makes some serious changes in how it explains ICD-10 coding.

'ICD-9 Kills'

What we need is a dramatic bumper sticker. Something that is succinct and scares the beejesus out of us. Because it's not enough not say we're one of the last civilized countries to use ICD-9 codes. Who cares what they do in Europe? We're Americans. If we can get along without themetric system, we can get along with ICD-10 codes.
Yes, I'm being incredibly flip about it, and I don't want to make stuff up. But we need to have more compelling arguments for implementing ICD-10 coding.
So we need videos of people who have gotten sick or died because there was not enough data about their diagnoses to create informed treatments. Explain how better data can save lives. Put faces and names to the problem.
Specificity is key.
Seriously. If we can't demonstrate how ICD-10 saves lives, learn to love ICD-9 codes.

Explain that we're already using ICD-10 codes

And it hasn't killed anyone. Well, that's because ICD-10 codes have been used since 1999 to describe causes of death.
So show ICD-10 opponents how the codes have been used to understand what is killing us.

Incentivize ICD-10 coding

If the Centers for Medicare and Medicaid Services (CMS) had created meaningful use type payments to implement ICD-10 coding, we would have a lot less vigorous opposition.
I understand Congress these days isn't in the habit of giving away money. But if there is any cash available, it would make physicians a lot less angry.

Explain the flaming water skis

Why do we have a diagnosis code for injuries due to flaming water skis? And don't tell me it's useful to know how injuries occurred. You have to do better.
Someone asked for this particular diagnosis. Out that person or association who wanted to count water ski injuries.
Make them explain why it's useful to know that information. Don't let the wanna-be comedians get away with keeping it as a punchline.
Grab every macaw bite, lamppost run-in and jet engine death. Stand someone up who wants to count those diagnoses and make them explain why it matters.
We need to know that these diagnosis codes were not created by sadistic bureaucrats or international conspirators.
Again, I'm advocating specificity because speaking about ICD-10 benefits in general terms isn't working. We need real examples that will give politicians, medical professionals and patients reasons to want ICD-10 codes.

Tuesday, April 1, 2014

Elizabeth “Betty” T. Jordan Shares a Nurse’s Perspective on Health IT

Elizabeth Betty T. Jordan Shares a Nurse's Perspective on Health IT
Nurses are vital to the implementation and adoption of healthcare technology. In this conversation, Intel’s Joan Hankin, MSN, RN, sits down with Elizabeth “Betty” T. Jordan, DNSc, RNC, FAAN and Associate Professor University of South Florida College of Nursing, to discuss a nurse’s perspective on health IT, how IT impacts patient care, and how generational attitudes shape health IT adoption.
About Elizabeth “Betty” T. Jordan
Elizabeth “Betty” T. Jordan, DNSc, RNC is an assistant professor at Johns Hopkins University School of Nursing in Baltimore. Jordan received her Doctoral of Science degree from Johns Hopkins School of Nursing, her Master of Science in nursing from the University of Delaware and her Bachelor of Science in nursing from the University of Maryland, College Park, Md. Jordan completed her business of nursing post-graduate certificate at the Johns Hopkins University School of Nursing.
With more than 25 years of clinical experience and significant research expertise in labor and delivery, Jordan is a recognized national leader in maternal and newborn outcomes research, education and practice. Her areas of expertise include high-risk maternal-newborn care; prenatal care; predictors of neonatal outcomes; outcomes measurements in perinatal care; secondary data analysis; legal consulting for perinatal nursing care; and educating nursing students as “doulas,” birth companions.
She has been published in Nursing and Health Care Perspectives, and the Journal of Obstetric, Gynecologic, and Neonatal Nursing. Jordan is an elected member of the board of directors for the Association of Women’s Health, Obstetric and Neonatal Nurses and also serves on the board of directors for the National Healthy Mothers, Healthy Babies Coalition. She maintains a clinical nursing practice with the Baltimore City Health Department, reviewing infant and fetal deaths and aspects of prenatal care.
Elizabeth "Betty" T. Jordan Shares a Nurse's Perspective on Health IT by 

Why nurses deserve a seat at the health IT development table March 4, 2014 | By 

    As the use of technology in healthcare becomes more ubiquitous, one question that deserves more attention is that of the role of nurses in making development and implementation decisions; essentially, what should that role be?

In a recent interview, Elizabeth "Betty" Jordan, R.N., an assistant professor at the University of South Florida College of Nursing, said that nurses should be included in all health IT decisions. From conception to evaluation, she said, nurses deserve a seat at the IT table.
"Our healthcare space is getting bigger, and nurses working on those units really rely on technology to be able to communicate," Jordan said. "Once they're comfortable with it, they won't be able to live without it."

In particular, Jordan talked about how often times, nurses are given demonstrations on IT tools that already exist--including tablets and other monitoring devices--but are not given the opportunity to join in on such conversations during the planning stages.

FierceHealthIT Editorial Advisory Board member Theresa Meadows, senior vice president and CIO at Cook Children's Health Care System in Fort Worth, Texas, agreed. Meadows, who also is a registered nurse, told FierceHealthIT that nurses can bring a unique perspective to such discussions because of their involvement in all aspects of care.

"I believe the skill that we bring to the table is the ability to discuss the process of patient care in great detail," Meadows said. "Nurses have the ability to form relationships with patients, physicians and other caregivers; they are trusted advisors. "

Meadows added that 80 percent of a nurse's day consists of decision making, communication and education.
"These skills are critical when deploying technology," she said.


Considering the federal government's continued emphasis on pushing for increased patient engagement, it would seem a wise decision to involve clinicians who already are proven to be able to "empower patients" in participating in their own care in the development of tools they're very likely to use.

"Nurses will continue to play a key role in the implementation and adoption of technology," Meadows said. "If the nursing staff is positive about adoption, you will find that others will be positive, as well."


Read more: Why nurses deserve a seat at the health IT development table - FierceHealthIT http://www.fiercehealthit.com/story/why-nurses-deserve-seat-health-it-development-table/2014-03-04#ixzz2xhMmpkBM
Subscribe at FierceHealthIT

Not a word about ICD10!

In response to the Senate's silence on 

ICD-10, a word about the delay

The importance of ICD-10 to legislators in the context of the sustainable growth rate patch was made abundantly clear by the number of mentions the implementation received in more than three hours of debate preceding the bill's vote Monday evening.
For those who didn't have the distinct pleasure of watching every second of the proceedings, U.S. Senators mentioned the ICD-10 portion of H.R. 4302, The Protecting Access to Medicare Act, a grand total of zero times; not one word. Considering the measure--all seven lines--was seemingly slipped into the middle of the bill, cloak-and-dagger style, even 10 seconds devoted to ICD-10 would have been better than nothing at all.
Of course, the transition--now delayed for the second time in nearly two years--is anything but a trivial pursuit for hospital providers who were finally prepared to make the leap from the ICD-9 coding system. And, unlike the Senate, they didn't hesitate to talk to FierceHealthIT about it.
"Significant efforts and dollars have gone into readiness," Sue Schade, CIO at the University of Michigan Hospitals and Health Centers told FierceHealthIT via email. She added that a delay only increases the amount of resources needed.
Roger Neal, vice president and CIO at Duncan (Okla.) Regional Hospital, agreed with Schade. "I think delaying ICD-10 for those who have been working on it and have spent tons of cash to get all of their systems in place, tested and moving is one of the worst things that can happen," he told me in an email.
Jeff Smith, director of federal relations for the College of Healthcare Information Management Executives--which expressed dismay with the measure shortly after the Senate vote was made official--told FierceHealthIT that the delay essentially rewinds the clock to 2012 for the healthcare industry.
"[I]t's not clear at all that we can keep doing this at the price levels," he said. "It's not clear that this time next year, we'll be in a position to put forth a full repeal bill for the same amount of money. Obviously money was the sticking point this time around; people couldn't agree how to pay for the thing in bulk."
What's more, the American Health Information Management Association, in its statement chiding the vote, said that a delay "casts a cloud on the employment of more than 25,000 students," all of whom have been trained to code exclusively in ICD-10 in anticipation of the transition. "As demands for quality healthcare data continue to increase, this delay will add an additional significant hurdle for the healthcare system to fill these important [health information management] positions," AHIMA CEO Lynne Thomas Gordon said.
AHIMA's statement also noted that a delay likely will cost the healthcare industry an additional $1 billion to $6.6 billion on top of costs already incurred from the previous delay. "This does not include the lost opportunity costs of failing to move to a more effective code set," the statement pointed out.
Between the waste of money and the inability to move forward with a code set that, according to the World Health Organization, is already being used by much of the rest of the world, you would think there might be something worth mentioning--especially considering the delay was important enough for inclusion in the bill in the first place.
Too bad the Senate didn't see it that way. - Dan @FierceHealthIT


Read more: In response to the Senate's silence on ICD-10, a word about the delay - FierceHealthIT http://www.fiercehealthit.com/story/response-senates-silence-icd-10-word-about-delay/2014-04-01#ixzz2xgdw4QBK
Subscribe at FierceHealthIT