AIRA Knowledge Sharing Document Review Guidelines

The Review Process

When someone hits the Send button on the KSR Document Submission form, all the information from the form and the document itself are routed directly to AIRA's Research and Development Manager.

If the document has already been reviewed and approved, it is entered into the KSR database and will be available online. If the document has not been reviewed, it will be posted on the Special Interest Group page of the relevant AIRA committee for review and approval. The committee members will be alerted that there is a document in their forum to be read and reviewed. All members of that committee will have read access to this document.

Once AIRA's Research and Development Manager is informed that the document has been reviewed and approved, the document will be entered into the KSR database and will be available online.

The Rules for Review

All documents submitted for inclusion into the KSR need to satisfy certain basic criteria with regards to style and content. The job of the person reviewing the document is not to rewrite or correct the document, but rather to decide whether the quality of the document is such that it would be a valuable addition to the KSR.

Style

• Documents need to be well written, well organized, and follow a logical flow.
• Acronyms and abbreviations should be defined at their first usage.
• Spelling and grammar errors should be noted.

Subject

The document should be read keeping in mind the interests of the KSR users. The subject should be relevant, useful, practical and current. The content is expected to be accurate, reliable and complete.

Keywords

If keywords are not provided with the document, the person reviewing the document should provide relevant keywords.

Focus Areas

Each document should be assigned as many focus areas as apply to the topic. If the document was submitted with focus areas, this should be checked for completeness and revised as necessary.

This is the breakdown of the focus areas. Many do overlap.

• Privacy and Confidentiality including HIPAA, FERPA, state and federal legislation
• Funding including costs, cost analysis, cost benefits, grant proposals
• Data Use including vaccine management, consumer information, disease surveillance, coverage assessments, provider quality assurance, service delivery, PROW, AFIX, HEDIS, VFC reports
• Data Quality including accuracy, timeliness, completeness, de-duplication, methodologies, scans, tools
• Integration including linkages to other health information systems, PHIN, NHII, NEDSS, HAN
• Provider Participation including private and public providers, HMOs, MCOs, advocacy, education, marketing, recruitment, training
• Standards including PROW, certification, HL7, CIRSET
• Technical Capabilities including functionality, implementation, software

Best Practices

If the document qualifies as a best practice based on the definition below, designate it as such on the KSR submission form or in the note on the forum.

A best practice is a process, technique, or innovative use of resources (technology, equipment, personnel, data) that has resulted in outstanding and measurable improvement in the operation or performance of an immunization registry.

This best practice will have demonstrated success by significantly and measurably improving such factors as cost, data quality, provider participation, coverage rates, integration with other health care systems, ease of use, compliance with standards, or functionality.

A best practice should be able to be documented to allow other registries to adapt this practice and realize success in their own environment

Final Check

Review the information provided with the document. Update, if necessary.