You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that the HCS vocabulary would tend to have a community assigned policy, should there be an extension on Concept datatype that can point at the policy / Permission?
For example:
Given an PurposeOfUse Treat, what is the definition of the policy allowed by a Permit on PurposeOfUse of Treat?
Question: Is there already a mechanism used to bind a lab procedure to a LOINC code?
Note that Medication (definition) goes the other way, in that it indicates the NDC codes it represents. So, should Permission have an optional element for the use-case of a Permission describing the rules for that code?
The text was updated successfully, but these errors were encountered:
One solution is to define new codes everytime there is a need for a distinct code. The drawback of this is that it is not treating codes as concepts, but rather treating codes as policy identifiers. But lacking a need, this might be the best solution available right now.
Given that the HCS vocabulary would tend to have a community assigned policy, should there be an extension on Concept datatype that can point at the policy / Permission?
For example:
Given an PurposeOfUse Treat, what is the definition of the policy allowed by a Permit on PurposeOfUse of Treat?
Question: Is there already a mechanism used to bind a lab procedure to a LOINC code?
Note that Medication (definition) goes the other way, in that it indicates the NDC codes it represents. So, should Permission have an optional element for the use-case of a Permission describing the rules for that code?
The text was updated successfully, but these errors were encountered: