Retrieve Diagnostic Report

retrieve findings and interpretations of diagnostic tests from patients access clinical context, atomic results, images, textual and coded interpretations, and diagnostic report formats ideal for accessing a comprehensive view of a patient's diagnostic history to access this clinical data you'll need the patient identifier, obtainable through the retrieve patient docid 8opknnbmtaz47rk5hkdd3 interaction interaction retrieving the list of diagnostic reports can be done by sending a get request the request is sent to the diagnosticreport endpoint https //api \<region> founda com/1/organizations/\<org x>/fhir/4/diagnosticreport?\<parameters> where \<region> should be defined according to the different founda sandbox testing docid\ ncff15xnu1wglst2wnm p and \<org x> should be replaced with the healthcare provider's organization id that you are integrated with the response contains a bundle with 0, 1 or n matching diagnostic reports the full diagnosticreport resource can be retrieved with the identifier of the selected diagnosticreport from the result set profile founda adheres to recognized standards (ihe, hl7 fhir) to ensure compatibility and harmonization among diverse systems if there is a profile available for an interaction, it is recommended and preferred to follow the prescribed transactions the retrieve diagnosticreport interaction with the founda platform is based on the ihe qedm profile to indicate that the request and response should comply with pcc 44, the profile parameter should be included to the search set /diagnosticreport? profile=https //profiles ihe net/iti/qedm parameters in order to comply with the pcc 44 transaction, the interaction should at least support the parameter in the table below additional search parameters, as defined in the fhir diagnosticreport resource, can be used as well parameters combination type required description patient + category reference + token the patient to search data for + the category name of the resource patient + category + code reference + token + token the patient to search data for + the category name of the resource + the code of the resource patient + category + date reference + token + date the patient to search data for + the category name of the resource + the date of creation of the resource patient + category + code + date reference + token + token + date the patient to search data for + the category name of the resource + the code of the resource + the date of creation of the resource at least one of the combinations has to be supported example api call curl location 'https //api eu founda com/1/health/organizations/org 00aade37f8304bbc85d935e5dc8e5930/fhir/4/diagnosticreport?patient=2503\&category=phr& profile=https%3a%2f%2fprofiles ihe net%2fiti%2fqedm%2f' \\ \ header 'authorization bearer ory at fdyaqkzz035jldyspb7xpu3xhxckbyeinuex5zgyyp0 lukepblvfag9koihmpiwk4r94cljr9oaozfnceri jy' \\ \ data ''{ "resourcetype" "bundle", "id" "b6ec32db d4b1 4949 b4a7 80b6d2ee37e4", "meta" { "lastupdated" "2023 11 23t15 54 33 568+00 00" }, "type" "searchset", "total" 1, "link" \[ { "relation" "self", "url" "https //api eu founda com/1/health/organizations/org 00aade37f8304bbc85d935e5dc8e5930/fhir/4/diagnosticreport?patient=2503\&category=phr& profile=https //profiles ihe net/iti/qedm/" } ], "entry" \[ { "fullurl" "https //api eu founda com/1/health/organizations/org 00aade37f8304bbc85d935e5dc8e5930/fhir/4/diagnosticreport/2496", "resource" { "resourcetype" "diagnosticreport", "id" "2496", "meta" { "versionid" "1", "lastupdated" "2023 11 23t15 51 33 330+00 00", "source" "#jagujzrachepyeyf", "tag" \[ { "system" "http //terminology hl7 org/codesystem/v3 actreason", "code" "htest", "display" "test health data" } ] }, "text" { "status" "generated", "div" "\<div xmlns=\\"http //www w3 org/1999/xhtml\\">\<p>\<b>generated narrative with details\</b>\</p>\<p>\<b>id\</b> example pgx\</p>\<p>\<b>basedon\</b> \<a>servicerequest/example pgx\</a>\</p>\<p>\<b>status\</b> final\</p>\<p>\<b>code\</b> pharmacogenetics report \<span>(details {https //system/pgxreport code 'pgxreport' = 'pgxreport', given as 'pharmacogenetics report'})\</span>\</p>\<p>\<b>subject\</b> \<a>bob smith\</a>\</p>\<p>\<b>effective\</b> 15/10/2016 12 34 56 pm\</p>\<p>\<b>issued\</b> 20/10/2016 2 00 05 pm\</p>\<p>\<b>performer\</b> \<a>organization/4829\</a>\</p>\<p>\<b>result\</b> \<a>observation/example phenotype\</a>\</p>\<p>\<b>presentedform\</b> \</p>\</div>" }, "status" "final", "category" \[ { "coding" \[ { "system" "http //terminology hl7 org/codesystem/v2 0074", "code" "phr" } ] } ], "code" { "coding" \[ { "system" "https //system/pgxreport", "code" "pgxreport", "display" "pharmacogenetics report" } ], "text" "pharmacogenetics report" }, "subject" { "reference" "patient/2503", "display" "bob smith" }, "effectivedatetime" "2016 10 15t12 34 56+11 00", "issued" "2016 10 20t14 00 05+11 00", "performer" \[ { "reference" "organization/2452" } ], "result" \[ { "reference" "observation/2494" } ], "presentedform" \[ { "contenttype" "application/pdf", "language" "en", "data" "cgrmsw5cyxnlnjrcaw5hcnk=", "hash" "571ef9c5655840f324e679072ed62b1b95eef8a0", "title" "pharmacogenetics report", "creation" "2016 10 20t20 00 00+11 00" } ] }, "search" { "mode" "match" } } ] }