Patient Identifier Query

application clients can use the patient identifier query to retrieve previously stored patient identifiers with their cross references from founda's patient identifier cross reference manager profile the patient identifier query interaction with the founda platform is based on the https //profiles ihe net/iti/pixm/ to indicate that the request and response should comply with https //profiles ihe net/iti/pixm/iti 83 html , the base url for an iti 83 operation contains the $ihe pix parameter interaction in order to query for all the patient identifier cross references, the identifier of the source patient identifier system should be passed inside the query parameters this is sent to the patient endpoint with a get request, for example https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient/$ihe pix?sourceidentifier=urn\ oid 1 3 6 1 4 1 21367 13 20 1000|ihered optional add a targetsystem to the query parameters to specify the target system of which you want to query the identifier, for example https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient/$ihe pix?sourceidentifier=urn\ oid 1 3 6 1 4 1 21367 13 20 1000|ihered\&targetsystem=urn\ oid 1 3 6 1 4 1 21367 13 20 2000 depending on the docid\ ncff15xnu1wglst2wnm p you are in example api call curl location 'https //api eu founda com/1/health/organizations/org 4c5739ba994d4ce9b5255d3f84a2d367/fhir/4/patient$ihe pix?sourceidentifier=urn%3aoid%3a1 3 6 1 4 1 21367 13 20 1000%7cihered\&targetsystem=urn%3aoid%3a1 3 6 1 4 1 21367 13 20 2000' \\ \ header 'authorization bearer ory at neeqjt2mknexgsu7qfzsaivhp8is 6c0ycdp wqami0 wmjzb98t0qwtbrmwmhj vhsobmsv9ahcc61bwedtju4'{ "resourcetype" "patient", "active" true, "identifier" \[ { "system" "urn\ oid 1 3 6 1 4 1 21367 13 20 1000", "value" "ihered" }, { "system" "urn\ oid 1 3 6 1 4 1 21367 13 20 2000", "value" "iheblue" }, ] }