documentation is that NCQA reviewers are not familiar with your practice, its electronic health record or terminology/acronyms, nor are they clinicians so may not be able to interpret the documentation you have provided. Clearly label everything to the story” of what you are providing. “tell NCQA’s document preparation tips can be accessed . Internal Documentation Checklists Whether utilizing the technical assistance of a certified consultant or not, it is helpful to have another team member review a documentation example before it is submitted. This task serves two purposes: 1) it promotes accountability and accuracy since more than one team member is aware of and understands what has been submitted; and 2) it saves technical assistance resources, which can be costly, for tasks that are harder for the PCMH team to complete on their own. By reviewing the documentation prepared by another PCMH team member, the reviewer often develops a greater understanding of NCQA requirements and is better able to prepare their own documentation that meets standards. Additionally, it ensures that documents developed by one team member are not contradictory or redundant with documents developed by another team member. For this reason, we recommend that at least two team members are responsible for the development and submission of documentation, and that they each review each other’s documentation examples. We created checklists for each factor to assist in this review and provide a standardized process. These checklists can also be used during the creation of documentation. The internal documentation checklists can be accessed .
documentation is that NCQA reviewers are not familiar with your practice, its electronic health record or terminology/acronyms, nor are they clinicians so may not be able to interpret the documentation you have provided. Clearly label everything to “tell the story” of what you are providing. NCQA’s document preparation tips can be accessed . Internal Documentation Checklists Whether utilizing the technical assistance of a certified consultant or not, it is helpful to have another team member review a documentation example before it is submitted. This task serves two purposes: 1) it promotes accountability and accuracy since more than one team member is aware of and understands what has been submitted; and 2) it saves technical assistance resources, which can be costly, for tasks that are harder for the PCMH team to complete on their own. By reviewing the documentation prepared by another PCMH team member, the reviewer often develops a greater understanding of NCQA requirements and is better able to prepare their own documentation that meets standards. Additionally, it ensures that documents developed by one team member are not contradictory or redundant with documents developed by another team member. For this reason, we recommend that at least two team members are responsible for the development and submission of documentation, and that they each review each other’s documentation examples. We created checklists for each factor to assist in this review and provide a standardized process. These checklists can also be used during the creation of documentation. The internal documentation checklists can be accessed .