Introduction Information Technology curriculum prepares us for planning, analysis, design and implementation of practice management systems. These courses include applying and learning skills related to systems development life cycle, project management, requirement analysis and specification, feasibility and cost-benefit analysis, workflow analysis, process improvement, logical and physical design, system validation, human factors and post implementation review.
Information Technology gives us an opportunity to look at health care systems by reducing human errors, improving clinical outcomes, facilitating care coordination and improving practice efficiencies. We can use this information to track data over time and make strategic decisions to improve patient care.
Reflections and Artifacts Reflection #1 HCIN 543 Program Outcome Learning where data lives in an electronic health record can be useful for tracking various information for business purposes and patient care. Database Design and Knowledge Management course teaches us how to apply real life scenarios, extract data and build meaningful reports. This course takes a deep dive into Access, SQL (Structured Query Language) and report building.
Artifact #1 is a project that looks at building a database, how to combine data from different tables, and finally looks at presenting the data in meaningful way. For this project, I looked at the business side of healthcare by trying to find a pattern in patient balances by location and provider. This information can be useful for troubleshooting payers and identifying if staff needs more training. A report like this is something that I can use in my current role and educate front office and billing staff on insurance plans, differences between copays, coinsurance, and deductibles.
Reflection #2 HCIN 543 Program Outcome Systems Analysis and Design for Health Care Informatics was one the best courses in the program. Artifact #2 is a EHR GO-LIVE Planning Checklist. While on the surface this one-page document may seem pretty simple, a lot planning went into each step. First, we needed to create project teams and outline responsibilities for each role. Meeting each deadline was essential to the success of EHR implementation. This assignment looks at all the moving parts, how each team and assignment are reliant upon each other, and most importantly that communication is key.
Building teams and setting goals is important but how we hold each other accountable to those goals is crucial. All of us, as part of the project team, have an important role in maintaining each step. If one step is missed it delays the whole project. This impacts costs, business decisions and patient care. Keeping the team on task is not easy and how we do so is essential to any project’s success.
Reflection #3 HCIN 543 Program Outcome How do you measure the success of a project? Success of a project can mean different things to different team members. The project should include a post implementation report that consists of key questions that determine whether or not the goals of the project were achieved. In Artifact #3, I take you through a series of interview questions selected that illustrate the impact and scope of an EHR implementation project. These questions speak to the skills and talent of staff, costs of the project, EHR functionality and needs of the health care organization. Like most EHRs, some do better than others when it comes to functionality. Some have great clinical workflows while others are perceived by providers as having “too many clicks.” Some have efficient billing systems while others you need a developer on staff. Finding an EHR that is user friendly, has great financial and quality reporting capabilities, and a robust billing system is not always easy to find. As I reflect on this artifact, I learned a great deal by considering the needs of health center staff and stakeholders.