Explain how computer-assisted coding capabilities will contribute to the effectiveness of the coding processes and the EHR.
HIM 220 Final Project Guidelines and Rubric
Overview The way healthcare data is managed has changed significantly over time in order to better accommodate healthcare professionals and patients. In an ever- growing digital world, health systems are full of data, allowing for more personalized patient care. Collecting data on its own is only half of the battle. When an organization adopts new technology such as electronic health records (EHRs), they must carefully consider how this technology will be implemented and how it will work with existing technologies. Technology and data are only effective in patient treatment if they are implemented in a way that considers the needs of an organization and its patients. For this project, you will be tasked with making EHR recommendations for a fictional organization from the provided scenario. You will start by reviewing the organization itself so that you can get a good look into what services they provide to better accommodate their specific needs. Next you will review options for EHRs and make recommendations that you think will work best based on the organization’s needs. The project is divided into three milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. These milestones will be submitted in Modules Three, Four, and Five. The final product will be submitted in Module Seven. This assessment addresses the following course outcomes:
Assess the capabilities of health information storage systems for ensuring security of patient health information and regulatory compliance Develop appropriate database design recommendations that can be integrated into an organization’s electronic records and billing systems
Determine the data necessary to be collected and stored for ensuring quality care based on the needs of an organization
Determine effective approaches to testing system architecture for maintaining functionality and user experience
Prompt For this project, you will review the provided scenario and develop recommendations for an organization looking to adopt an EHR and how to best implement the new technology.
Scenario
Healthcare organization Alpha is looking at converting from its outdated combination of paper documentation and electronic scheduling systems to a more robust EHR that will be able to accommodate all of its service lines. Alpha is a 150-bed hospital, with five designated intensive care beds. Its emergency department is designated as a level III trauma center.
2
Alpha has designated care areas for:
Outpatient surgery
Orthopedic surgery Women’s health
Pediatrics
Cardiology The auxiliary service lines consist of:
5 family practice clinics 2 internal medicine clinics
1 cardiology clinic
1 neurology clinic
1 orthopedic and sports medicine clinic 1 eye care clinic
1 women’s health clinic
1 pediatric clinic In addition, Alpha provides outpatient rehabilitation services and a community wellness program. Alpha is looking for a solution that will allow it to seamlessly share information between all of its service lines, and yet be user-friendly enough to not alienate its dedicated staff.
Specifically, the following critical elements must be addressed:
I. Analysis: Organizational Overview: In this section of the project, you will establish some key details about the organization you will be assisting as they look to adopt a new EHR system. These key details will directly inform the next steps in selecting and implementing an EHR system effectively.
A. Describe the organization and potential aspects that will need to be considered when recommending a database. B. Describe the scope of services the organization provides based on the information provided. C. Determine the key stakeholders that would need to be part of the EHR selection process. Provide rationale for each choice.
II. Design: Applications: In this section of the assessment, you will begin to look at considerations that should be taken into account when recommending
applications to be used within the EHR.
3
A. Determine the necessary requirements of applications to ensure they adhere to applicable regulations. Explain each requirement. B. Describe the scope of functionality these applications will be depended on for and justify why these applications are essential to the EHR. C. Establish the secondary data the organization will need to be part of the EHR. Explain why this data is necessary. D. Describe how these applications will handle health information exchange (HIE). E. Describe the security features within the application and explain how these features will be effective in protecting patient information. F. Interpret the processes of the computer-assisted coding that will be used in your coding management application. G. Explain how computer-assisted coding capabilities will contribute to the effectiveness of the coding processes and the EHR.
III. Design: EHR Selection: In this section of the assessment, you determine the EHR that you will recommend for the organization and share some of your
thought process and rationale. A. Identify the certified EHR that you have chosen for this organization and justify why this EHR will best suit the organization’s needs. B. Determine how this EHR meets CMS regulations. Support your response with examples. C. Determine the type of EHR that you have chosen for the organization and justify how it will address the organization’s needs. D. Describe how this EHR will support patient centered technology, specifically portals and collection of patient information. E. Recommend a user interface design that will be included in any applications or peripherals that will maximize the functionality of this EHR.
IV. Implementation: In this section of the assessment, you will brainstorm your approach to implementing a new EHR.
A. Determine how data entry will be completed and explain why this approach is efficient for users. B. Determine an appropriate approach to testing the new EHR to ensure functionality and eliminate any bugs. C. Describe how you would approach education and training around the new EHR within the organization.
Milestones Milestone One: Organizational Overview and Applications In Module Three, you will determine the organization’s EHR needs by reviewing the key details of the organization. You will use this information to determine what should be taken into account when recommending applications to be used within the EHR. This milestone will be graded with the Milestone One Rubric. Milestone Two: EHR Selection In Module Four, you will submit your recommendation for an EHR and explain your rationale behind your choice for the organization. This milestone will be graded with the Milestone Two Rubric. Milestone Three: Implementation In Module Five, you will brainstorm your approach to implementing your new chosen EHR. This milestone will be graded with the Milestone Three Rubric
4
Final Submission: EHR Recommendations In Module Seven, you will submit your final project. It should be a complete, polished artifact containing all of the critical elements of the final product. It should reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Rubric.
Deliverables
Milestone Deliverable Module Due Grading One Organizational Overview and Applications Three Graded separately; Milestone One Rubric
Two EHR Selection Four Graded separately; Milestone Two Rubric
Three Implementation Five Graded separately; Milestone Three Rubric
Final Submission: EHR Recommendations Seven Graded separately; Final Project Rubric
Final Project Rubric Guidelines for Submission: Your EHR recommendations must be 5–7 pages in length, use 12-point Times New Roman font, double-spaced, and follow APA format for citations if necessary.
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Analysis: Organizational
Overview: Organization
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes the organization and potential aspects that will need to be considered when recommending a database
Describes the organization and potential aspects that will need to be considered when recommending a database, but description is cursory or contains inaccuracies
Does not describe the organization
6
Analysis: Organizational
Overview: Services
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes the scope of services the organization provides based on the information provided
Describes the scope of services the organization provides based on the information provided, but description is cursory or contains inaccuracies
Does not describe the scope of services offered by the organization
6
5
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Analysis: Organizational
Overview: Stakeholders
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Determines the key stakeholders that would need to be part of the EHR selection process and provides rationale for each choice
Determines the key stakeholders that would need to be part of the EHR selection process and provides rationale for each choice, but rationale is cursory or illogical
Does not determine the key stakeholders that would need to be part of the EHR selection process
6
Design: Applications:
Requirements
Meets “Proficient” criteria, and determination demonstrates keen insight regarding adherence to regulations
Determines the necessary requirements of applications to ensure they adhere to applicable regulations, explaining each requirement
Determines the necessary requirements of applications to ensure they adhere to applicable regulations, explaining each requirement, but explanation is cursory or lacking details
Does not determine the necessary requirements of applications
3.85
Design: Applications: Scope
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes the scope of functionality the applications will be depended on for and justifies why the applications are essential to the EHR
Describes the scope of functionality the applications will be depended on for and justifies why the applications are essential to the EHR, but description is cursory or illogical or justification is inaccurate
Does not describe the scope of functionality that the applications will be depended on for
3.85
Design: Applications: Data
Meets “Proficient” criteria, and explanation demonstrates keen insight regarding the role of secondary data in an EHR
Establishes the secondary data the organization will need to be part of the EHR and explains why this data is necessary
Establishes the secondary data the organization will need to be part of the EHR and explains why this data is necessary, but explanation is cursory or inaccurate
Does not establish the secondary data the organization will need to be a part of the EHR
5.42
Design: Applications: Health
Information Exchange
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes how the applications will handle HIE
Describes how the applications will handle HIE, but description is cursory or inaccurate
Does not describe how the applications will handle HIE
5.42
Design: Applications:
Security
Meets “Proficient” criteria, and description draws cogent connections between security features and protecting patient information
Describes the security features within the application and explains how these features will be effective in protecting patient information
Describes the security features within the application and explains how these features will be effective in protecting patient information, but description is cursory or inaccurate or explanation is illogical
Does not describe the security features within the application
3.85
6
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Design: Applications:
Computer-Assisted Coding
Meets “Proficient” criteria, and demonstrates a sophisticated understanding of how the computer-assisted coding processes can impact the coding management application
Interprets the processes of the computer-assisted coding that will be used in coding management application
Interprets the processes of the computer-assisted coding that will be used in the coding management application, but interpretation is cursory or inaccurate or explanation is illogical
Does not interpret the processes of the computer- assisted coding that will be used in the coding management application
4
Design: Applications: Capabilities
Meets “Proficient” criteria, and demonstrates a sophisticated awareness of the impact computer-assisted coding capabilities have on the effectiveness of an EHR
Explains how the computer- assisted coding capabilities will contribute to the effectiveness of the coding processes and the EHR
Explains how the computer- assisted coding capabilities will contribute to the effectiveness of the coding processes and the EHR, but contains inaccuracies or explanation is illogical
Does not explain how the computer-assisted coding capabilities will contribute to the effectiveness of the coding processes and the EHR
3.85
Design: EHR Selection: EHR
Meets “Proficient” criteria, and makes cogent connections between the chosen EHR and the needs of the organization
Identifies the certified EHR chosen for this organization and justifies why the EHR will best suit the organization’s needs
Identifies the certified EHR chosen for this organization and justifies why the EHR will best suit the organization’s needs, but justification is cursory or illogical
Does not identify a certified EHR
8.63
Design: EHR Selection: CMS
Regulations
Meets “Proficient” criteria, and determination makes cogent connections between CMS regulations and an EHR
Determines how the EHR meets CMS regulations and supports response with examples
Determines how the EHR meets CMS regulations and supports response with examples, but determination is cursory or examples used are illogical
Does not determine how the EHR meets CMS regulations
3.85
Design: EHR Selection: Type of
EHR
Meets “Proficient” criteria, and demonstrates keen insight regarding specific EHR types
Determines the type of EHR chosen for the organization and justifies how it will address the organization’s needs
Determines the type of EHR chosen for the organization and justifies how it will address the organization’s needs, but justification is cursory or contains inaccuracies
Does not determine the type of EHR chosen
8.63
Design: EHR Selection: Patient
Centered Technology
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes how the EHR will support patient-centered technology, specifically portals and collection of patient information
Describes how the EHR will support patient-centered technology, specifically portals and collection of patient information, but description is cursory or lacks detail
Does not describe how the EHR will support patient centered technology
6.42
7
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Design: EHR Selection:
Peripherals
Meets “Proficient” criteria, and recommendation makes cogent connections between EHR functionality and peripherals that will maximize the functionality of this EHR
Recommends a user interface design that will be included in any applications or peripherals that will maximize the functionality of this EHR.
Recommends a user interface design that will be included in any applications or peripherals that will maximize the functionality of this EHR, but description is cursory or illogical
Does not recommend a user interface design that will be included in any applications or peripherals that will maximize the functionality of this EHR
4.82
Implementation: Data Entry
Meets “Proficient” criteria, and explanation demonstrates keen insight regarding user efficiency
Determines how data entry will be completed and explains why this approach is efficient for users
Determines how data entry will be completed and explains why this approach is efficient for users, but explanation is cursory or illogical
Does not determine how data entry will be completed
4.82
Implementation: Testing
Meets “Proficient” criteria, and determination demonstrates a complex grasp of testing and the elimination of bugs
Determines an appropriate approach to testing the new EHR to ensure functionality and eliminate any bugs
Determines an appropriate approach to testing the new EHR to ensure functionality and eliminate any bugs, but determination is illogical, lacks detail, or is not appropriate for the new EHR
Does not determine an approach to testing the new EHR
4.82
Implementation: Education and
Training
Meets “Proficient” criteria, and description is exceptionally clear and contextualized
Describes how education and training would be approached regarding the new EHR within the organization
Describes how education and training would be approached regarding the new EHR within the organization, but description is cursory or illogical
Does not describe how education and training would be approached
4.82
Articulation of Response
Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy-to-read format
Submission has no major errors related to citations, grammar, spelling, syntax, or organization
Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas
Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas
4.95
Total 100%
