| Table of Contents |
|---|
...
| Task | Component | Details | Responsible | Status as of Nov 2017 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Minimum Integration | ||||||||||||||
| Auth | ||||||||||||||
| Auth | OLMIS-3135: Service Accounts (Service accounts – backend connections/tokens with Nexleaf) | OpenLMIS | |||||||||||
| Service Account | Create account or meta data with group structure to ensure that domain, path, tokens (access service account) for accessing openLMIS are known to the components in the NL system which will consume the data. | Nexleaf | ||||||||||||
| Future: single sign-on | Not in scope for Minimum Integration / first phase | |||||||||||||
| Master Data Alignment | ||||||||||||||
| OLMIS-3385: OpenHIE's mCSD Facility Registry Description: Support Care Services Update Consumer/Provider for Facility Registries So OpenLMIS can be a "consumer and provider" Needed for FHIR | OpenLMIS | ||||||||||||
| Geographic hierarchies | This may be addressed in the facility registry via the location resource in FHIR. | |||||||||||||
| OLMIS-3386: For interoperability with Nexleaf, provice FHIR Device resources for OpenLMIS CCE Inventory For interoperability with Nexleaf, provice FHIR Device resources for OpenLMIS CCE Inventory | OpenLMIS | ||||||||||||
| NexLeaf product being a consumer of the facility registry | Nexleaf needs to know how to read FHIR resources to discover facilities and CCE. Nexleaf needs to build a sync tool to do initial discover and updating (scheduled? push button?) of master data from openLMIS. | Nexleaf | ||||||||||||
Tech design for CCE Inventory sync | Need to hold joint planning/tech design to identify the approach or the mappings of certain fields. There are 3 possible options on the table. #1 and #3 are the best. | OpenLMIS, Nexleaf | ||||||||||||
| CCEquipment catalog synchronization | OpenLMIS share their Equipment List with Nexleaf. Both sides ensure there is consistent mapping between fields indicating the make and model. Needs to know make/model of devices at each facility. Need to make sure CCE catalog in both OpenLMIS and Nexleaf are synced | OpenLMIS, Nexleaf | ||||||||||||
| Alerts | ||||||||||||||
| OLMIS-3136: Allow CCE Inventory Alerts to be pushed into OpenLMIS | OpenLMIS | ||||||||||||
| Advocacy & Long-Term | ||||||||||||||
| PQS Catalog Standardization | Larger advocacy to get standardized, consistent, non-disappearing PQS list that is available as CSV/Excel (and not just PDF). | OpenLMIS, Nexleaf | ||||||||||||
| ATOM feed to query for changes from a facility registry | Maybe this includes advocacy with FHIR and OpenHIE communities? Promote this as a future standard? | OpenLMIS, Nexleaf | ||||||||||||
| what else? | ||||||||||||||
| Discussed | we could look at fields in SELV API; talk about what we know about our users; what specifically means "needs attention" for us; what is the combination of Nexleaf metrics that tips something into the Non-Functional status? Notes from : Who is the person looking at the information in OpenLMIS? We will want to make sure the person taking care of the equipment has time to address. Decided we focus on What is the type of information exchanged? The configuration of the flag would live within Nexleaf and a generic set of data will be passed. Based on configuration in Nexleaf.
What would be the format of the information?
Does OpenLMIS store the data? Can previous days get updated?
How frequently should there be updates?
| |||||||||||||
| Discussed on |
| |||||||||||||
| To be discussed on |
| |||||||||||||
| Languages | Architecture note: Languages should also be supported. ISO standard | |||||||||||||
| OpenLMIS 3.0 upgrade in existin countries | Is there an OpenLMIS-using country planning to scale up to 3.0 and start using these features? - Conversation is definitely happening in Mozambique, but no clear plans yet. Can keep team updated on updates with other countries as well | |||||||||||||
| What this achieves: Shared facility list, shared CCE inventory device list, OpenLMIS consumes alerts from ColdTrace, standardization of catalog devices (long term). | ||||||||||||||
...
- Gavi demo is scheduled for
- Update on API: https://docs.google.com/document/d/1cwdTIOtPbuf1O2_s5BPgEKEAps9HyU4A9TEbM6Owmk0/edit
- Update on looking into the web hooks and appropriate retry policy
- FHIR resources completed
- However, one minor correction
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4064 - https://test.openlmis.org/referencedata/docs/#!/default/get_api_Location
- http://docs.openlmis.org/en/latest/components/index.html
- However, one minor correction
- Needs Attention functionality to be defined this sprint
- Demo Data
- Facility/location (example, Dep—sito Distrital Cuamba) https://github.com/OpenLMIS/openlmis-referencedata/tree/master/demo-data
- Equipment - https://github.com/OpenLMIS/openlmis-cce/tree/master/demo-data
...
Current thinking for the demo (DRAFT)
Facility: Dep—sito Distrital Cuamba (still need to define the HF but I think it is Matias, Cuamba)
Devices:
Draft User journey | Narrative and Key things to note | Issues/concerns/missing/questions (MJ Notes) | |
|---|---|---|---|
| 1 | As the DIVO, view the CCE equipment inventory at the district store and note the "needs attention flag" due to the integration with ColdTrace | Describe out the integration is based in the FHIR standards of location and device. Any system can utilize/leverage. Note the alert thresholds we set up in ColdTrace to trigger the needs attention flag. |
|
| 2 | As the DIVO, I can add/modify CCE inventory at my store. | Don't go through the whole process. | Don't go through the whole process. |
| 3 | As the DIVO, I can update the needs attention flag to non-functional |
do we want to show the integration in further detail by logging into ColdTrace....
- Should we sync up the demo data so they are aligned?
- On the coldtrace side, how can we 'send an alert'?
- OpenLMIS 3.3 Demo : Martin Lukac to update
- One piece of equipment will have an active alert
- One piece of equipment will have an old alert
- user: divo1, password: password
- Martin Lukac would you help me with a slide on ColdTrace and brief summary of the blog we did? Thanks!
Check in Meeting
Update from NexLeaf
- tested the serializtion numbers, works good
Update from VR
- View the historical alerts
- Planning to wrap up
andJira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4257
shortlyJira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4249
Out of Scope:
- Synchronizing user accounts & permissions across platforms
- Achieving a shared, standardized PQS catalog (this is a long term goal that is not covered by this)
...