J#46293 Removed orphaned/incomplete binding on Goal.target.detail

[michelle-m-miller]

Description

J#46293 Removed orphaned/incomplete binding on Goal.target.detail (intentionally unbound)

[lmckenzi]

Should there not be at least a binding description?

[michelle-m-miller]

@lmckenzi

Should there not be at least a binding description?

The vote was to remove the entire binding, including the description.

[lmckenzi]

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?

[michelle-m-miller]

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."

[lmckenzi]

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.)

[michelle-m-miller]

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.