redirect_uri
. 1upHealth syncs data from that system into that user's FHIRยฎ resources via a backend process every 2 minutes.clinical
for clinical data from 1upHealth supported health systems.4894
in this case for future requests.redirect_uri
(associated with the client_id
). And we will begin collecting data and making it available to your application.access_token
for that user. Additionally, apps can modify their query to adjust which source metric or they want data from. Here are a few examples. Each of these queries will have to be accompanied by the Authorization header containing the user's bearer auth token.steps
(66334-4
).4706
code
to get an access_token
via 1upHealth's OAuth2 token endpoint.fhirjason
/ epicepic1
, and authorize your app. After authorization, the user will be sent back to your app.access_token
to query their demographics.4706
and direct your user to the following urlclient_state_param
until redirected to the callback url.