Implementer’s Guide
This resource serves as an overview for getting started with Avetis. Our team will work with you every step of the way.
Start Here:
The Implementer’s Guide is not comprehensive. It is just meant to provide an overview of how we work and provide insight into what it is like to work with us.
What is eHealth?
1. Introduction
The term eHealth encompasses a set of different concepts, including health, technology, and commerce. Health, as used in these definitions, usually refers to health care as a process, rather than to health as an outcome.
2. Examples
eHealth is a broad concept which includes more specific projects, including –
- Electronic Health Records (EHR)
- Electronic Medical Records (EMR)
- Telehealth and telemedicine
- Health IT systems
- Consumer health IT data
- Virtual healthcare
- Mobile Health (mHealth)
- Big data systems used in digital health
3. Why use eHealth in clinical care?
The use of eHealth technologies can improve patient care, reduce costs and enhance physician happiness if done correctly. By taking a holistic approach to eHealth and investing in the underlying compatibility of different projects, we believe we can address each of these three needs simultaneously.
4. What makes a good eHealth project?
An eHeath project should accomplish the following:
- Improve Patient Safety
- Support delivery of effective patient care
- Facilitate management of chronic diseases
- Improve efficiency
- Have feasibility as an implementation criteria
What is Avetis?
1. Introduction
Avetis is an eHealth project with a mission to increase adoption of all eHealth initiatives in Armenia both directly through our projects as well as indirectly by helping to define standards and train individuals in Armenia to take on this work.
2. Overview
- Demonstration of digital health record systems for healthcare screenings and single use case clinical applications. As we develop our own projects, we will be sharing our documentation and hosting a sandbox environment to allow others to see our work. Additionally, we are happy to meet with any organization that is working on their own projects to share our experiences and lend our expertise as appropriate.
- Implementation of Avetis with other organizations. Later this year, we hope to provide funding, technical development support and health informatics guidance to a select group of organizations that are looking for implement electronic records in their projects.
- Education of healthcare informaticists in Armenia. This fall, we will be providing scholarships to competitive individuals to pursue a graduate certificate in healthcare informatics from a US program as well as a two year living stipend while the individual is studying.
Getting started with Avetis
1. Overview
Starting with Avetis requires two separate parallel tracks: clinical implementation and technical implementation. The length of time from start to initial implementation varies with complexity, the readiness of the implementing organization and our team’s bandwidth. Ideally we aim to go from idea to implementation in two months.
2. Clinical Implementation
This work includes specifying the use case for an eHealth solution, designing novel workflows or mapping existing workflows to be digitized, designing forms and data input streams, creating a data element dictionary to standardize inputs and testing with clinical personnel.
The Avetis team will guide each partner through this collaborative process. We outline the process below, but this is just meant to provide insight on what will be expected of your organization.
3. Technical Development
The technical work is done by software engineers to set up servers, customize the database, build custom features, enforce security practices and the like.
The Avetis team will provide the necessary technical resources and manage the software development. Ideal partner organizations do have someone who is comfortable with computers and is responsible for administration of the software. But they do not need to be able to code!
Identifying a Use Case
What use case to select?
Start with a simple use case if this is your first time implementing digital health records. We can help identify which existing workflows might be a good fit.
For future implementations, Avetis is able to support more complex visits, share data between providers within the same organization and handle things like lab values and imaging.
Mapping Workflows
Start with Mapping Workflows
Start by defining each step of the clinical workflow. One way to do this is by creating a patient journey map which will start with the first time the patient interacts with your organization, to their physical arrival at the clinic, to the receiving care, checking out and any follow up contacts. After creating the map, it is generally straightforward to figure out what data each step should generate which will guide the development of the electronic health record.
Defining Data
Introduction
Once you know what data you expect to capture, we will work with you to identify standardized data types and custom data concepts. This will ensure interoperability and keep things organized. This will form the basis of your data element dictionary.
Assigning Roles
Introduction
Using the patient journey map, it is likely that the patient will interact with multiple people from your organization. It is best to limit access to only the functionality that an individual needs to do their job. It is common to have a clinical and administrative role, but can be more complex as needed.
Gathering Feedback
Introduction
With all the requirements collected in the first four steps, we will then start developing the custom forms and features for your Avetis implementation. During this process, we will hold regular meetings for feedback sessions and to present updates.
Request More Information
We are thrilled to meet with anyone interested in electronic health records in Armenia. Please reach out to schedule time to meet!
