Retrieve Observation

access patient observation data recorded during healthcare encounters retrieve vital signs, laboratory results, and other clinical measurements useful for monitoring a patient's health status and analyzing trends in their clinical data to access this clinical data you'll need the patient identifier, obtainable through the retrieve patient docid 8opknnbmtaz47rk5hkdd3 interaction interaction retrieving the list of observations can be done by sending a get request the request is sent to the observation endpoint https //api \<region> founda com/1/organizations/\<org x>/fhir/4/observation?\<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 observations the full observation resource can be retrieved with the identifier of the selected observation 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 immunization 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 /observation? 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 observation 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