Workflow or API calls:
Reminder: If this is a client domain—not the public sandbox—do not include API request data.
We are querying the Millenium FHIR R4 endpoint for Memorial Hermann Health System.
For all FHIR search queries for USCDI V1 scopes against this server (for example "AllergyIntolerance?patient=[patientId]") the server response is:
{
"fhirData": {
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "invalid",
"details": {
"text": "at least one of _id and patient must be provided"
}
}
]
}
}
Even though we include the patient FHIR id in the query we get this response, and it's the same for all of the USCDI v1 scopes. The response details.text might differ slightly (for example when querying the Condition resource ("Condition?patient=[patientId]) the details.text is "at least one of patient, subject, or _id must be provided").
We are able to succesfully query the ‘Patient’ resource directly (i.e. Patient/[patientFhirId]) but all search queries fail as described above.
Expected Result:
The server should see that the patient query param is being included and return the corresponding data for FHIR search queries involving the patient param.
Actual Result:
We just ran the following three queries against the production Memorial Hermann FHIR server around 10:48-10:49AM Pacific Monday August 7 2023:
-
Patient/[patientFhirId] - worked successfully - 'x-request-id': [ 'c34046c3-bcaa-40b7-ab0a-71a56d210883+4Zvd_iUTb' ]
-
AllergyIntolerance?patient=[patientFhirId] - does not work - 'x-request-id': [ '160095be-b03c-4e99-8e20-0de7ee044621+MAqR_i1DN' ]
-
Condition?patient=[patientFhirId] - does not work - 'x-request-id': [ 'e1015a53-81e2-48ff-af17-e4983a326efe+tmNo_2PHC' ]
Thank you. This is a high priority issue and we hope to resolve this quickly.