The Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications.
Remove the "HTTP GET” text from Figure 3.78.4-1 since we can now use GET or POST for the query. Removing that from the figure effectively defers to details in message semantics
In the “identifier” row, the following two sentences can be deleted from the end of Col 2 because they appear at the beginning of the definition: “...The identifier specified in this parameter is expressed using the token search parameter type. Please see ITI TF-2:Appendix Z.2.2 for use of the token data type for patient identifiers.”
The information response provided by the Patient Demographics Supplier to the Patient Demographics Consumer is a list…
Case 1: The Patient Demographics Supplier finds in its information source at least one patient record sent as HTTP query search parameters.
…then do a global replace of "query parameters" with "search parameters" (there are more, at least in Case 2)
Case 4: … There are two different acceptable responses return results. ...
Just checking that you want “should” and not “shall” in the following: The Patient Resource(s) contained within the Query Patient Resource Response message should conform to Patient Profile for PDQm.
Case 1: The Patient Demographics Supplier finds in its information source the patient demographics record matching the resourceId sent in the HTTP request.
...
Case 2: The Patient Demographics Supplier fails to find in its information source the patient demographics record
The Patient Demographics Supplier’s response to a successful Retrieve Patient Resource message shall be an HTTP 200 (OK) Status code with a Patient Resource as defined in Patient Profile for PDQm, or an appropriate error code. as defined in Patient Profile for PDQm.
Observations on PDQm Vol 2, all editorial in nature:
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#23784-messages
Remove the "HTTP GET” text from Figure 3.78.4-1 since we can now use GET or POST for the query. Removing that from the figure effectively defers to details in message semantics
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#23784121-search-parameters
In the “identifier” row, the following two sentences can be deleted from the end of Col 2 because they appear at the beginning of the definition: “...The identifier specified in this parameter is expressed using the token search parameter type. Please see ITI TF-2:Appendix Z.2.2 for use of the token data type for patient identifiers.”
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#23784122-parameter-modifiers
Change “query parameters” to “search parameters”
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#23784123-populating-which-domains-are-returned--
Is the comma correct in this example: &identifier=urn:oid:1.2.3|,urn:oid:4.5.6|
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#2378413-expected-actions
The information response provided by the Patient Demographics Supplier to the Patient Demographics Consumer is a list… Case 1: The Patient Demographics Supplier finds in its information source at least one patient record sent as HTTP query search parameters. …then do a global replace of "query parameters" with "search parameters" (there are more, at least in Case 2) Case 4: … There are two different acceptable responses return results. ...
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#23784221-patient-resource-definition-in-the-context-of-query-patient-resource-response
Just checking that you want “should” and not “shall” in the following: The Patient Resource(s) contained within the Query Patient Resource Response message should conform to Patient Profile for PDQm.
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#2378433-expected-actions
Case 1: The Patient Demographics Supplier finds in its information source the patient demographics record matching the resourceId sent in the HTTP request.
...
Case 2: The Patient Demographics Supplier fails to find in its information source the patient demographics record
https://build.fhir.org/ig/IHE/ITI.PDQm/branches/main/ITI-78.html#237844-retrieve-patient-resource-response-message
The Patient Demographics Supplier’s response to a successful Retrieve Patient Resource message shall be an HTTP 200 (OK) Status code with a Patient Resource as defined in Patient Profile for PDQm, or an appropriate error code. as defined in Patient Profile for PDQm.