-
Notifications
You must be signed in to change notification settings - Fork 177
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
J#46293 Removed orphaned/incomplete binding on Goal.target.detail #3156
base: master
Are you sure you want to change the base?
J#46293 Removed orphaned/incomplete binding on Goal.target.detail #3156
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should there not be at least a binding description?
The vote was to remove the entire binding, including the description. |
I think there's a methodology requirement that if you have a coded element you need to at least have a binding description if you don't have a binding - there needs to be some sort of guidance as to what the content should/might be. Can you start a discussion on Zulip? |
Patient Care is willing to update the element description to include "A CodeableConcept value could be Positive, Negative, Abnormal, Normal, Present, Absent, Yes, No." |
That would work. Though we have codes that actually cover those concepts, so why not an example binding to point people to the existing codes if that's what they want? (Example bindings aren't intended to be comprehensive, just a set of codes that could theoretically be used.) |
When this was discussed in the past, the concern was that the values are so broad that any example value set is only a small fraction of possibilities and not very representative. |
Description
J#46293 Removed orphaned/incomplete binding on Goal.target.detail (intentionally unbound)