-
**Section Number**
Section 5.2
**Issue**
Consider the next sentences:
>The Patient Demographics Query for Mobile (PDQm) Profile is functionally the same as PDQ but leverages the FHIR standar…
-
**Section Number**
Section 5.4
**Issue**
Consider the next sentence:
>In this way the PCP office can discover the ...
What does a PCP office have to do with PMIR, or is this just an examp…
-
Einige Instanzen von https://hitontology.eu/ontology/Interoperability haben zuwenig Informationen, z.B. https://hitontology.eu/ontology/CCAM hat nur das Label. Es sollte immer sowohl der abgekürzte al…
-
Should XCPD variations be discussed? record location, cross-reference, demographics, etc.
Ask of @jlamy to review and offer insights on XCPD variations that should be highlighted. This is not a tec…
-
- [x] @maghalandari Send list of interoperability standards to @KonradHoeffner
- [x] @maghalandari Send detailed list of interoperability standards to @KonradHoeffner
- [x] check DBpedia for these i…
-
3.71.6.3
IUA: "the role value SHOULD be patient if the current user is a patient, or user for healthcare professionals."
Introducing scope definitions that conflict with SMART will cause confusion…
-
Section 34.6, Line 461 in IUA.b, Rev.1.2 from September 21, 2019:
_The XUA profile provides equivalent functionality for SOAP based transactions. In addition, the SAML token option in IUA enables an…
-
PDQm has a test case that recommends a 404. Do we mean it must do 404 and only 404? Or do we allow a 200 with zero results like the access control appendix allows? Would 200 with zero results be a goo…
-
So far, the FHIR component is bound to DSTU2, including the IHE profiles MHD, PIXm, PDQm, and Restful ATNA query. These profiles have been migrated to FHIR STU3 (see http://wiki.ihe.net/index.php/ITI_…
-
After FHIR DSTU2 has released and a couple of IHE profile offer FHIR equivalents to legacy transactions, we should start thinking about providing some support, and how...
Most of the stuff in http://…