The Department of Health and Human Services (HHS) has proposed delaying the implementation of ICD-10 by one year to Oct. 1, 2014, through a proposed rule: “Administrative Simplification: Adoption of a Standard for a Unique Health Plan Identifier; Addition to the National Provider Identifier Requirements; and a Change to the Compliance Date for ICD-10-CM and ICD-10-PCS Medical Data Code Sets”. As the delay is being determined through the standard rulemaking/regulatory process, the actual time frame may change once feedback from the open comment period has been considered and the HHS initial proposal is taken into account. The comment period will be for 30 days prior to its official publication in the Federal Register.
Older post
Contributors
-
Alan Brookstone, MDFamily Physician, Chairman, Cientis Technologies and Co-Founder of AmericanEHR PartnersView Posts -
Michael S. Barr, MD, MBA, FACPFormer Senior Vice President, Division of Medical Practice, Professionalism & Quality, American College of PhysiciansView Posts -
-
Mary GriskewiczMary P. Griskewicz is the Senior Director of Healthcare Information Systems for the Health Information and Management Systems Society (HIMSS).View Posts -
Mitchell A. Adler, MDCMIO, Physician & Ambulatory Network Services, NorthShore-LIJ Health SystemView Posts -
Jerome Carter, MD, FACP, FHIMSSEditor, Electronic Health Records, Second Edition and creator of the EHR Science blogView Posts -
William S. Underwood MPHSenior Associate, Center For Practice Improvement & Innovation, American College of PhysiciansView Posts -
Edgar WilsonEdgar Wilson is an independent consultant from Oregon who writes on trends in education, healthcare, and public policy.View Posts
-
Abhinav ShashankCEO & Co-Founder of Innovaccer. Abhinav is an expert in entrepreneurial skills and robust technologies. His goal is to create the World's most intuitive Big Data Platform which would revolutionize Population Health Management.View Posts
-
Frank IrvingEditor, PhysBizTech, an online publication covering business and technology issues at small physician practices.View Posts
-
Megan NicholsMegan Nichols is a science writer who enjoys writing about healthcare, psychology and other scientific fields of study.View Posts
-
Duane NickullCTO Hot Tomali Communications and AmericanEHR Partners Advisor Former Senior Technical Evangelist, AdobeView Posts -
-
Alex TateDigital marketing specialist, content strategist, and health IT Consultant at CureMD.View Posts -
-
Paul BrientPaul has more than two decades of experience in healthcare information technology and as CEO of PatientKeeper, he is focused on making electronic medical records easier to use for physicians so that more time can be spent focused on patient care. Prior to joining PatientKeeper in 2002, Brient held senior executive-level positions at leading healthcare and consulting firms including McKesson Corporation, HPR, and The Boston Consulting Group.View Posts -
David Wiljer & Sara UrowitzDavid Wiljer, PhD is Director, Knowledge Management and Innovation at University Health Network, Toronto. Sara Urowitz, MSW, PhD is Manager, Education Informatics and ELLICSR: Health, Wellness and Cancer Survivorship Centre and Assistant Professor, Department of Psychiatry and Institute for Health Policy, Management and Evaluation, University of TorontoView Posts
-
-
-
Michael W. JakovcicMichael W. Jakovcic is E.V.P. Fusion Consulting, Healthcare Division.View Posts -
Benjamin ShibataBenjamin Shibata graduated from UCLA with a degree in bioengineering. He is currently a Master of Public Health student at George Washington University studying health policy.View Posts
-
-
Abbas DhilawalaAbbas is the CTO of Galen Data and has over 13 years of experience developing enterprise grade software for the medical device industry. He is well versed with technology and industry standards regulating security and privacy of data. His expertise lies in programming, cloud, cyber security, data storage and regulated medical device software.View Posts -
-
-
Sara UrowitzSara Urowitz, MSW, PhD is Manager, Education Informatics and ELLICSR: Health, Wellness and Cancer Survivorship Centre and Assistant Professor, Department of Psychiatry and Institute for Health Policy, Management and Evaluation, University of Toronto.View Posts
-
I’m a solo practitioner general surgeon and have been using an integrated medical records system for the last 10 years. I believe that many physicians do not completely understand why an electronic medical record system is so valuable. They are lost in the fact that it seems cumbersome to enter the patient’s information. I strongly believe that there is no role for drop-down menus when recording a patient’s history. I continue to use a dictated note as has been done for years, but in my case I use voice recognition to directly import my note into my record system. A computer generated note from drop down menus is really not helpful.The fact that a patient must provide each physician’s office with a medical history at each new patient visit is ridiculous during this age of information technology . A patient transferred from one hospital to another arrives with hand written scribble is ridiculous in 2012.I have worked with a small, user friendly company for 10 years. The system is adaptable and has continued to improve. As a solo practitioner it has been easy to transition my office staff to the current chartless status. I have sought the opportunity to share my thoughts however no one wants to hear from a solo country surgeon. I will continue with my system and continue to enjoy the benefits. I would leave this final note: If a doctor believes that an EMR is there to make things quicker and more economical than he will struggle with the transition. If the doctor realizes that the EMR will make the records transferable and accessible that adoption will be more smooth.
Part of the problem of aggregating claims, clinical, labs and scripts data is that it comes in different forms, from different databases and has different naming standards. Organizations first need to understand who has access to that data (and then think about who SHOULD have access to it) and then they may want to de-identify PHI to keep the data secure. One key here is to consistently de-identify data from each contributor (and no PHI should leave any of the contributors during that process).