FR Functional Requirement
The system shall support the ability to create, define, and evolve the attributes & associated data dictionary for a registry.
The system shall support the ability to create, define, and maintain multi-organizational hierarchies of facilities and related geo-objects.
Facility type (e.g., hospital, clinic, mobile clinic, lab, pharmacy)
Facility ownership/managing authority
Facility physical address
Facility contact information
Facility unique identifier
Type of Services offered - Lab, HIV, TB, etc.
Human resource for health, numbers by cadre
Opening and closing times
Common and Mapped Identifiers per Location
Details on Infrastructure - Power, Water, etc.
The system shall support the ability to set up and manage users, permissions for reading data, writing data (posting, validation, publishing), viewing data and system administration.
At minimum an FR should support the ability to create roles and assign permissions to the roles. Example roles would be the Master Administrator, Data curator, Health Officer.
The system should have flexible standards-based APIs, preferably RESTful API.
The system should have the ability to pull and/or push data to other systems (.csv) based on defined criteria.
The system shall support the ability to do bulk imports.
The system should support the ability to search for facilities by attribute.
The system should support the ability to see the facility located on a map.
The system should allow public access to view data that is relevant to the public (e.g. services provided by a facility)
The system should support facility data curation to manage site status changes (closures, openings, service changes)
The system should generate standard and customizable reports inline with the core FR attributes.
The facility registry should align with the primary Master Facility List at minimum, or influence its update.