| Outcome | (Work in progress) - Do not do ReactNative in OpenSRP. It's too risky and doesn't have a clear value
- Do not do the API gateway approach. That has long term technical debt that we don't want to take on.
Decision and Path Forward: - Develop in OpenSRP
- Reduce scope of Lots and Batches
- Potentially add scope from our next priorities (such as receiving a shipment; interoperability with mCSD/FHIR standards; single sign-on with OAuth2; or demonstrating how multiple apps interoperate smoothly)
- If there is re-usable code in the SIGLUS Maven .jar library, consider using/reusing that
- Focus on standards for:
- Auth - User Accounts
- Representation of Locations
- Prioritize the immunization nurse use case (and later the SIGLUS-v3 upgrade will need to focus on the pharmacy/storeroom/dispensary use cases, and we will need to demonstrate how different solutions work at different levels of the supply chain; some levels might use OpenSRP where higher-volume levels might use SIGLUS)
Next Steps: - Craig will write a SRS and we will reconvene to ensure the scope is appropriate and achievable
|
|---|