Patient Identity Feed

to use the founda platform as a cross reference patient identifier manager, it has to be fed with patient identifiers and their cross references there are four types of operations for the patient identity feed add a new patient identifier revise an existing patient identifier resolve a duplicate patient identifier remove an existing patient identifier this page describes the interactions and provides you with code examples to start using the patient identity feed through the founda platform profile the patient identity feed interactions with the founda platform are based on the ihe pixm profile to indicate that the request and response should comply with iti 104 , the profile parameter should be included in the patient payload that is being send to the endpoint how to include the profile url in the request body { "meta" { "profile" \[ "https //profiles ihe net/iti/pixm/implementationguide/ihe iti pixm" ] } } add/revise a patient identifier a patient identifier can be added/revised by sending a patient resource in a fhir structured json body to the founda platform the body has to be sent with a put request to the patient endpoint, depending on your sandbox testing docid\ ncff15xnu1wglst2wnm p https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient to add/revise the patient identifier of an existing patient, the query parameters of the call to the patient endpoint should contain a valid identifier, for example https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient?identifier=urn\ oid 1 3 6 1 4 1 21367 13 20 1000|ihered the identifier provided in the query parameter is the combination of an identifier domain and a patient identifier, represented as a single string and pipe delimited | { "resourcetype" "patient", "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" } ], "meta" { "profile" \[ "https //profiles ihe net/iti/pixm/implementationguide/ihe iti pixm" ] } } resolve a duplicate patient a duplicate patient identifier can be resolved by replacing the patient identifier and all of its internal references with the patient identifier provided in the replaced by link to do this, a patient resource in a fhir/json body is sent to the patient endpoint with a put request the query parameters of the call should contain the valid identifier of the patient you wish to resolve the duplicate patient for https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient?identifier=urn\ oid 1 3 6 1 4 1 21367 13 20 1000|ihered depending on the sandbox testing docid\ ncff15xnu1wglst2wnm p you are in { "resourcetype" "patient", "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" } ], "link" \[ { "other" { "identifier" { "system" "urn\ oid 1 3 6 1 4 1 21367 13 20 1000", "value" "ihegreen" } } } ], "meta" { "profile" \[ "https //profiles ihe net/iti/pixm/implementationguide/ihe iti pixm" ] } } remove a patient identifier a patient identifier can be removed by initiating a delete request to the patient endpoint the query parameters of the call should contain the valid identifier of the patient you wish to remove https //api \<region> founda com/1/health/organizations/\<org x>/fhir/4/patient?identifier=urn\ oid 1 3 6 1 4 1 21367 13 20 1000|ihered depending on the sandbox testing docid\ ncff15xnu1wglst2wnm p you are in curl location request delete 'https //api eu founda com/1/health/organizations/org 4c5739ba994d4ce9b5255d3f84a2d367/fhir/4/patient?identifier=urn%3aoid%3a1 3 6 1 4 1 21367 13 20 1000%7cihered' \\ \ header 'authorization bearer ory at neeqjt2mknexgsu7qfzsaivhp8is 6c0ycdp wqami0 wmjzb98t0qwtbrmwmhj vhsobmsv9ahcc61bwedtju4'