Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Da Vinci HRex (FHIR)
-
1.0.0
-
Clinical Interoperability Council
-
HRex Consent Profile
-
-
Lloyd McKenzie/Jimmy Tcheng: 9-0-0
-
Correction
-
Compatible, substantive
Description
The policy element uses the HRex Consent Policy ValueSet (required). This has two values of regular or sensitive.
The cardinality of the slice should be constrained to 1..1
This will avoid confusion for implementers since the policy element has a 1.* cardinality which could lead to both codes being inserted.
Additional narrative to explain the use of the codes could also be useful. For example:
"One of the codes should be used to express the member's preference for the data being transferred. The sensitive code includes regular data. The regular code excludes sensitive data."
Attachments
Issue Links
- mentioned in
-
Page Loading...