Helping MSF sort through OCL concept import errors

Actually, @akanter, I think you’ve got it backwards. The SAME-AS mapping should be to the “official” code for the concept for the source. And OCL assumes concepts are stored under this official code. So, in this case, the official code for “Pressure ulcer stage I” within the MSF source is 3025, so the local concept should be mapped SAME-AS MSF:3025.

@lisamuga, if MSF goes through its source and adds a SAME-AS mapping for each concept to its “official” code (ID), this should address the issue. Since the Concept ID on OCL is assumed to be the official concept code for the source, then this means every concept in the MSF source would have a SAME-AS mapping to itself (e.g., MSF 3025 would have a SAME-AS mapping to MSF:3025 (i.e., source=MSF, code=3025).

For example, if you look at PIH’s Leg Pain (20138), there is a SAME-AS mapping to itself (PIH 20138) and OCL recognizes this as a “self mapping” indicated by a little ∞ superscript:

Once these self mappings are in place for the MSF source, any content imported into OpenMRS instances that gets assigned a random concept ID locally will be recognized as equivalent on subsequent imports through the self mapping (SAME-AS to an MSF code).

For any existing concepts already on OpenMRS instances, you would need to add these self mappings manually. In the example in my initial post, this would mean going to the OpenMRS instance where “Pressure ulcer stage I” was randomly assigned to concept ID 1059 and adding a SAME-AS mapping to the “official” MSF code (source=MSF, code=3025).

@lisamuga , let us know if this isn’t clear or if it doesn’t solve your issues. :slight_smile: