-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for Drug Reference Maps #219
Comments
Thanks @mogoodrich - I will let others comment in more details but if this is
then we are welcoming this suggested improvement. Depending on the timing this would make it in 2.5.0 or 2.6.0. |
This seems like an excellent addition to me! |
Yes, @mks-d all three of those things will be true, thanks! |
I ran into a bit of a snag here. See https://issues.openmrs.org/browse/TRUNK-6164. Will need to discuss how to work around this in Initializer. @ibacher FYI |
I have a solution for this ready for review @ibacher . Unfortunately the PR is failing in Github Actions because it depends on the latest 2.3.x build, and OpenMRS CI is failing to build 2.3.x due to Bamboo issues. Once we resolve that, things should turn green. |
Drugs in OpenMRS can be mapped to reference terms in the same manner as Concepts (see Drug Reference Map in orders)
We should support this in Iniz as follows:
In the Drugs domain, support specifying mapping in the same was we do for concepts as described here:
https://github.com/mekomsolutions/openmrs-module-initializer/blob/master/readme/concepts.md (see "Mapping Headers" section... we will support the new recommended format "Mappings|SAME-AS" aod "Mappings|SAME-AS|Source" format)
@mks-d @ibacher @mseaton @rbuisson fyi... any thoughts? At PIH we need this and can likely build this out in the coming weeks.
The text was updated successfully, but these errors were encountered: