...
Patients can search for measurements by:
$search-measurementmeasurements
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
Searching measurements with $search-measurementmeasurementsPOST $search-measurement request body: Parameters available:
Combinations allow for:
Response: The response is a bundle of nested bundles that each contain a full set of related resources (Observation, Media, QuestionnaireResponse and Provenance) for a found measurement. If a QuestionnaireResponse is part of a bundle the Questionnaire it answers is also included in the bundle. Related resources are the set of resources created by a single invocation of the submit-measurement operation.
Examples:Below example is from here: http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/POST_search-measurements.html#post-search-measurements Unlike a regular search operation which would be a GET request, the $search-measurement is a POST request to the URL:
The search parameters are sent by including them in the request body (below is a JSON example of a body):
The response will then contain a bundle of bundles with the found resources (Below is a JSON example of a return bundle):
|
Search on Observation$search-measurements-bundle-limit
Info |
---|
Introduced in 2024.3 |
Expand | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Description | |||||||||||||||||||||||||||||
| the tag of a resource | |||||||||||||||||||||||||||||
| The ID of the resource | |||||||||||||||||||||||||||||
| Search the contents of the resource's narrative using a fulltext search | |||||||||||||||||||||||||||||
| Episode associated with observation | |||||||||||||||||||||||||||||
| Reference to the serviceRequest | |||||||||||||||||||||||||||||
| The unique id for a particular observation | |||||||||||||||||||||||||||||
| The patient that the observation is about | |||||||||||||||||||||||||||||
| The serviceRequestVersionID held in the Resolved Timing | |||||||||||||||||||||||||||||
| Resolved Timing start | |||||||||||||||||||||||||||||
| Resolved Timing end |
| Resolved Timing type
|
| ||||||||||||||||||||||||||
Searching measurements with $search-measurements-bundle-limitPOST $search-measurement request body: Parameters available:
Combinations allow for:
Response: The response is a bundle of nested bundles that each contain a full set of related resources (Observation, Media, QuestionnaireResponse and Provenance) for a found measurement. If a QuestionnaireResponse is part of a bundle the Questionnaire it answers is also included in the bundle. Related resources are the set of resources created by a single invocation of the submit-measurement operation. The amount of nested bundles is limited by the given count parameter.
Examples:Below example is from here: http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/POST_search-measurements.html#post-search-measurements Like the $search-measurements operation, the $search-measurements-bundle-limit operation is also a POST request to the URL:
The search parameters are sent by including them in the request body (below is a JSON example of a body):
The response will then contain a bundle of bundles with the found resources (Below is a JSON example of a return bundle):
|
Search on Observation
Expand | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
Searching for ObservationBelow is a list of some of the common search parameters. An exhaustive list can be found in implementation guide at http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/measurement.openapi.json.
Response:
Examples:Searching on Observations are done by use of a traditional GET request:
As an example one could perform searches like the following examples:
An example of a response on for a search could be:
|
...
Expand | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
Searching on MediaSome Below is a list of some of the possible common search parameters. An exhaustive list can be found in implementation guide at http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/measurement.openapi.json.
Response:
Examples:Searching on Medias are done by use of a traditional GET request:
As an example one could perform searches like the following examples:
An example of a response on for a search could be:
|
...
Expand | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||
Searching for QuestionnaireResponseSome Below is a list of some of the possible common search parameters. An exhaustive list can be found in implementation guide at http://ehealth-documentation.s3-website-eu-west-1.amazonaws.com/latest/ig/measurement.openapi.json.
Response:
Examples:Searching on QuestionnaireResponses are done by use of a traditional GET request:
As an example one could perform searches like the following examples:
An example of a response on for a search could be:
|
...
Practitioners can search for measurements by the same methods as PatientPatients, but restrictions apply:
Practitioner The practitioner must be logged in using a CareTeam that, in generic terms, ”plays a role in the corresponding EpisodeOfCare or CarePlan”
...