Work in progress
This is page is a work in progress. This info bubble will be removed once the TWG feels it is complete.
This page focuses on creating a working definition of Community Health Information Systems (CHIS) and the actors who use these systems. This will be adjusted when the Delphi study results complete.
A Community Health Information System (CHIS) is an information system that supports the routine and emergency health care of a patient population within community contexts in defined geographic areas. CHISs target supporting patient and population health where there is minimal physical health infrastructure in order to support universal health coverage.
The following actors are important within a CHIS ecosystem:
These actors are defined in the User Personas section of the Interoperability workflows
Notes: (Model this section off of https://ohie.org/architecture-specification/)
Community Health Information Systems focus on supporting healthcare provided in the community context and have different functional requirements than electronic medical record systems that are targeted for deployment in brick and mortar health locations. This section defines the functional specifications for a CHIS.
Craig wrote these on 21 Dec - They are unordered, just to get some thoughts out there.
|#||CHIS Functional Requirement||Recommended/Required|
The system shall support synchronization and local caching of the appropriate information in order to support the full health workflows that are required for that patient's needs completely offline for long periods of time.
The system should support the full lifecycle management of location-based information for key administrative areas, structures, and points of interest that aid in the full management of care coordination. This location information shall include the ability to collect GPS geometries in point, polygon, or multi-polygon format so they can be displayed on a digital map.
|CHIS-3||The system shall support regular automated attempts to access the internet to sync.||Required|
|CHIS-4||The system should compressing information in minimal format when exchanging it between the centralized system and the point of service device in order to reduce the cost||Recommended|
|CHIS-5||The system should support enterprise mobility management (EMM) solutions to support the remote deployment of updates, enforcement of business and security policies, and monitoring of internet access costs.||Recommended|
|CHIS-6||The system shall support the orchestration of activities among the workforce so that community health workers are appropriately managed by their frontline management team. This includes providing views of health worker activity, supporting feedback loops with information through reports, and orchestration of activities natively within the system.||Required|
|CHIS-7||The system shall have a clearly defined process for managing conflicts in data submissions in order to robustly handle asynchronous submissions when front line devices have been offline for long periods of time.||Required|
|CHIS-8||The system should support syncing information between devices that are both offline (Peer-to-Peer sync)||Recommended|
|CHIS-9||The system shall provide robust reports that track the time lag between data collection to submission in important views so that managers clearly see sync activities.||Required|
|CHIS-10||The system shall have functions that support the privacy and security of personally identifiable information including user management, access controls, and auditing. This includes the ability to set up and manage users, permissions for reading data, writing data (posting, validation, publishing), viewing data, and system administration.||Required|
|CHIS-11||The system should support the regular synchronization of appropriate information between the central server and a health information exchange to support the workflows required in this context||Recommended|
|CHIS-12||The system should support the generation of "official" standardized reports from the point of service to the central system that supports stakeholder needs.||Recommended|
|CHIS-13||The system should be able to be deployed on premise within a country context to support data sovereignty laws that are applicable to the context||Recommended|
|CHIS-14||The system should have flexible standards-based APIs, preferably RESTful.||Recommended|
|CHIS-15||The system should have the ability to pull and/or push data to other systems based on defined criteria to a standardized format such as CSV, DXF2, JSON, XML, etc.||Recommended|
|CHIS-16||The system should generate standard and customizable reports in line with the core CHIS attributes.||Recommended|
|CHIS-17||The system should support a minimum set of data attributes as defined by the CHIS CoP||Recommended|
|CHIS-18||The system's point of service interface should support the needs of low-skilled health workers, providing decision support tools that measure and ensure quality of care is provided.||Recommended|
|CHIS-19||The system should support mechanisms to longitudinally track and manage the care of a patient and population within the assigned context.||Recommended|
|CHIS-20||The system should support modeling teams so that information about a given patient can be updated by any of the actors on the team. This allows frontline health workers and managers to ensure the continuity of care even if an individual team member is not able to provide it as scheduled.||Recommended|
|CHIS-21||The system shall support operating on low cost mobile devices that can be deployed at scale.||Required|
|CHIS-22||The system should be able to collect codes that link to standardized terminologies that support interoperability||Recommended|