-
Notifications
You must be signed in to change notification settings - Fork 2
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
Categories #24
Comments
From @davidmiller on October 6, 2014 16:51 For pre-populating fields in a GUI rule builder ? |
From @davidmiller on October 18, 2014 13:46 This is one of the reasons you use standardised taxonomies... |
From @davidmiller on January 20, 2015 17:54 So, this has come up elsewhere - the format for having a "version" of a taxonomy list somewhere and know what version you're using, and "release" a new version. This is a problem syncing various lists with e.g. elCID. Also - what you'll want is to start from a version of a base list, and then apply local patches - additions, removals etc. |
Should this be a glossolalialossia ticket? |
From @davidmiller on January 21, 2015 14:56 I'm not sure you'd want to go across the network for it... ? The data is currently stored in flies like https://github.com/openhealthcare/elcid/blob/master/data/lookuplists/lookuplists.json OPAL has management commands to load them I think that what you want is a versioned packaging format for the json and the ability for clinical experts to raise issues, add, remove from taxonomies. I have flirted with the idea of making the format friendlier ( ?Yaml) and splitting them into separate repositories e.g. one for elCID. Or something - am mostly braindumping. Would love to have a better way to manage these. |
From @rossjones on September 30, 2014 14:50
It should be possible to pull categories from an external source.
Use-case:
OPAL has a list of ID specific medication, it would be handy if D3 had access to those fields. We could probably get them from elsewhere, but per-installation we don't want to show irrelevant data as options for rules.
Copied from original issue: openhealthcare/ddd#7
The text was updated successfully, but these errors were encountered: