...
Summary: Users with this problem want to enable healthcare users to have some basic EMR functionality where they typically have low or no internet access, such as in a clinic or in a health post (visual examples of these types of sites below - example photos are mostly from real-world OpenMRS implementations!). These sites may have internet problems for a variety of reasons: there may be no network service in the area, or spotty/poor/intermittent service, or there may be intermittent power problems that can last hours or days causing the routers not to have power (e.g. the solar panel blew off the roof last night and broke, or the generator ran out of petrol and it's going to take a few days to get more fuel).
Case #2 is not designed to address Community Health Worker (CHW) / Outreach Worker use cases. CHWs' workflows are separated from a clinic or more traditional clinical team, which means they have different offline requirements that don't have to consider clinic workflows, nor do they necessarily need to get data updated at different locations relatively quickly, because there is often only 1 or a few CHWs responsible for a given residential community - they go to the patient. In contrast, patients tend to travel to a variety of clinics/centers. (For more nuanced CHW/outreach use cases, we recommend tools specifically designed for these users and use cases, such as Medic Mobile/CHT, CommCare, mUzima, etc.)Things that Case #2 is not:
- Case #2 is not a redesign of a whole EMR to an "EMR Lite" that looks very different. The look and feel should still ultimately be the same as much as possible, or at least consistent with the look and feel of the OMRS 3.0 RefApp UX.
- Case #2 is not aiming to include most functionality of a typical EMR. Functionality will be limited to the most basic of workflows.
...