-
According to the change proposal for EHSEPDBEP-245, the PersonalRelationship should not be used in context of the EPR.
PIXm and PDQm have to be consistent with the PIXV3 Feed and PDQV3 Query.
-
The PDQm $match output parameters profile (input/fsh/PDQmMatch.fsh) has a parent of Bundle, but I believe it should be a Parameters resource with this Bundle being set as the type for the "out" parame…
-
-
When you have a custom search parameter in a capability statement, the rendering puts in a link to the top level search section of the main resource instead of to that specific search parameter.
Fo…
-
-
Currently the expected actions for ITI-78 and ITI-119 require that all Patient Resources returned by the Patient Demographics Supplier conform to the [PDQm Patient Profile](StructureDefinition-IHE.PDQ…
-
We found the `pqdm` library is the thing swallowing all the error messages. `pqdm` has an `exception_behavior` option, which defaults to `"ignore"`, surprisingly. The other two settings, `"deferred"` …
-
There is a published implementation guide for MHD and PDQm:
* https://simplifier.net/IHEPatientDemographi?fhirVersion=STU3
* https://simplifier.net/IHEPDQmimplementatio?fhirVersion=STU3
and a 3rd…
-
Make an IG covering the RESTful ATNA supplement
Where the FHIR feed and query would have structureDefinition and CapabilityStatement profiling
-
@costateixeira has noted that the new wording in PDQm (and MHD) that has servers "shall" support both GET and POST searches does not seem to allow regions or organizations to write refining Implementa…