I am trying to save the below Immunization to a patient “Betty Williams”, and I am sending the below JSON snippet to the FHIR URL /ws/fhir2/R4/Immunization and I am not able to understand the diagnostics returned.
More metadata issues. CIEL:1410 is the Vaccination date concept. While that concept appears to be loaded on dev3, the mapping that says it is SAME-AS CIEL:1410 is missing. OpenMRS - Login
OK, after our discussion in the O3 squad call today, I’m trying to make sure I’ve updated all the metadata we need for this.
@ibacher you recently mentioned to me that “it looks like some CIEL mappings aren’t included in the Immunizations export” - in followup with @jamlung I learned that Parent concepts, i.e. concepts with a -1 superscript/inverse notation, do NOT get auto-pulled in (see Joe’s notes in slack here). So eg for 1410, it had 2 parent concepts, 1441 and 1421. I’ve now added both those to our Immunization Medatada set with this pr here.
I’ve also confirmed that “CIEL 5261A…”, mentioned in Vineet’s first post in this thread, is now included in the collection. Along with concepts for things like lot number etc.
@vasharma05 once my PR (#650) is merged, can you check and see if you are still blocked?
My lesson learned is: In the future, before we commit any metadata to our 3.x /ocl distro config, we should first check for errors using the OCL Subscription Module workflow in dev3.
So: After realizing I should use the OCL Subscription Module error UI to check for errors in our metadata config files, I have gone through every single one of our O3 refapp /ocl config metadata collections and checked all of them for errors - since I feel quite bad for the experience that @Hadijah, @Vineet Sharma and @Juliet Wamalwa have had trying to debug the Immunizations metadata. Hoping to prevent this from happening to others. I found 2 other demo data collections with similar issues and have made PRs to resolve these errors.You can see my full Findings and notes here: O3 Exploratory QA: OpenMRS 3.x Requirements Rubric - Google Sheets
Thanks so much I really appreciate your work with the entire OCL team but its unfortunate I can save the form its the error below that is standing between me and the PR for final review and I believe in you for the success.
@dkayiwa what do you think about this error message? Generally when I have seen ones similar to this it was because a concept or mapping was missing. But I believe I have exhaustively fixed that.
I am genuinely stumped here. But I also don’t know what this error message means at all so I’m not sure how to help next.
It looks like none of the concepts that were brought in from OCL have the mappings attached (CIEL, SNOMED, etc.). That means that when you search by CIEL code, nothing comes up. I would reimport the collection after it has been re-expanded on OCL to include all cascading references. When someone wants to reference a concept by the CIEL ID, do they have to convert to the UUID from CIEL? Should there be a mapping to CIEL in the concept as well when it comes in from the subscription module?
Andy, am so glad the concept CIEL:1418 was mapped but still getting the same error but this time complaining concept CIEL:1419 not mapped. Am glad @jamlung has offered to sync with me. Thanks so so much for your help I learnt something new and am grateful for that.