Take caution when using applications with pre-populated fields
Credentialing & Verification Update, January 16, 2008
Many organizations pre-populate medical staff applications (both initial and reappointment) for the convenience of the practitioner. The practice, though convenient, can have unintended consequences if the applicant does not read the pre-populated fields thoroughly and carelessly attests to something that is untrue. Therefore, make it clear to applicants that it is their responsibility to ensure that everything on the application (including pre-populated fields) is accurate, and that failure to do so could result in disciplinary action or charges of falsification.
The following example illustrates another potential danger of pre-populating fields: A healthcare organization had a very long state-required form for reappointment. A practitioner completed his application for reappointment at
Though it had been only a few months since the first application for reappointment, circumstances could easily have changed (e.g., a malpractice suit could have been filed against him, or his status at another facility might have changed). By not sending the application to the physician to review, the MSP inadvertently placed him at risk. His reappointment could have been denied for failure to provide the updated information.
Of course, one could argue that the physician should not have signed the application without having read the entire thing. However, from the practitioner's point of view, he may have thought he had seen everything he needed to review.
Source: The 2008 Credentials Verification Desk Reference.
Comments
0 comments on “Take caution when using applications with pre-populated fields ”
Related Products
Most Popular
- Articles
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- Catch up on what's new with injections and infusions
- Identify potential Medicaid RAC target areas
- HIPAA Q&A: Level of encryption needed for email
- Topic: CMS, OESS post new security compliance review information, checklist
- Capturing all necessary codes for IUD insertion and removal can be challenging
- What does case-mix index mean to you?
- OB services: Coding inside and outside of the package
- QA:Coding multiple initial infusions
- E-mailed
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- HIPAA Q&A: Level of encryption needed for email
- Q&A: Follow CMS' coding guidelines when using modifier -25
- What does case-mix index mean to you?
- Catch up on what's new with injections and infusions
- CMS has reformulated payments for some bilateral procedures
- New conflicts of interest create new challenges
- Q/A. One injection code or two?
- ED-to-inpatient transfers are flawed with safety gaps
- Searched
