Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Da Vinci PDex (FHIR)
-
current
-
Financial Mgmt
-
Payer-to-Payer Exchange [deprecated]
-
5.2.6
-
-
Bob Dieterle / MaryKay McDaniel: 8-0-0
-
Clarification
-
Non-compatible
-
2.0.0-ballot
Description
Hi.
This was raised during the workgroup conference call on November 11, 2022.
PDex defines a discrete patient-everything-pdex OperationDefinition with its own canonical URL, which allows clients to distinguish between it and the base specification's Patient-everything operation.
We need to do the same for the FHIR Bulk Data Access Patient Level Export operation. Presently, PDex simply refers to the existing definition. Since PDex expects $export to behave differently (e.g. constraining the payload to certain profiles), there's justification for a discrete OperationDefinition with its own canonical URL (e.g. patient-export-pdex).
Additionally, if the intent is that patient-export-pdex will only ever be scoped to a single Patient, a discrete OperationDefinition can support this. Either include a required input parameter identifying the member (i.e. the Member ID) or make this an instance-level operation that includes the Patient resource ID in the request URL.
Note we previously corrected the request URL pattern in FHIR-38650. All signs point to the need for a discrete OperationDefinition.
Thanks!