...
- Shows registry clients
- Right click on a connector, version, show local changes
2019-05-07
FHIR
- Convert requisitions in JSON to FHIR formats
- Industry standard format for interoperability
- Originally using Nifi between OpenLMIS and DHIS2
- OpenLMIS create data into FHIR, which then can be used by multiple sources, one is DHIS2
- DHIS2 Integration Software Requirements Specification
- What is a Measure
- FHIR resource that tracks measure quantity, e.g. beginning balance, holds all the attributes of the thing that you are measuring
- MeasureReport
- A bunch of Measures, create a MeasureReport from all of them
- Using a service-based token for getting FHIR resources
- Wambere (Unlicensed) to add the required customizations / configurations for FHIR integration to documentation
- Using just the Measure (FHIR) version provided by the FHIR server
- Assuming that only "our" Measures are on the FHIR server, we should document that assumption somewhere
- Getting FTAPs by administrator user, and assumes all products we care about are associated with facility type of health center
- Getting Measures only runs once, but should need to be run again each time the products list are updated, can only do this manually in the Nifi UI
- Using AttributesToCSV processor to see why DetectDuplicate is failing
- Processors can be renamed to have their purposes more clear (without opening them to look at config)
- Getting all the FHIR facilities the processor currently uses facility name which is not unique, this should use facility ID or a unique ID instead
- Getting locations, when evaluating JSON, all geo zones would have to be entered in properties for processor, which will not scale for many geo zones
- Get location name assumes district level and region level
- Get location id for requisition has hardcoded location names (demo data of Malawi and Mozambique)
- Get requisitions api needs to be updated to only return certain statuses (currently returns all)
- Generate Measure and Measure Reports process groups may not be generated correctly on Nifi startup; to ensure they are corrected generated, have to do it in Nifi UI after startup
- Stock status is hardcoded
- Are emergency requisitions reported in the Measure report? Should they?