-
Notifications
You must be signed in to change notification settings - Fork 102
Treat codes consistently across resources #15
Comments
I agree that codes should be parsed consistently, lots of benefits there, but I'm not sure what you mean about by giving the code a property name. The structure currently looks like: {
"name": "CBC WO DIFFERENTIAL",
"code": "43789009",
"code_system": "2.16.840.1.113883.6.96",
"code_system_name": "SNOMED CT", Are you suggesting something more like this? {
"label": "CBC WO DIFFERENTIAL",
"code": {
"code": "43789009",
"code_system": "2.16.840.1.113883.6.96",
"code_system_name": "SNOMED CT",
}, Or would you drop {
"label": "CBC WO DIFFERENTIAL",
"code": "43789009", |
We most certainly need
the idea thought would be in |
I've added this to the list of JSON to review. I'm working on a PR to add a |
For example in Labs, rather than repeating:
You should parse the code in a consistent way (including translations if present), and abstract out that logic. Then you can given the code a property name to attach it to the lab
(For example in SMART we use semantic labels like "labName", so we'd have an individual result and say
result.labName.code
, orresult.labName.label
).The text was updated successfully, but these errors were encountered: