Write To EHR
1upHealth makes writing back to multiple EHRs easy with a single end point.
Use 1upHealth FHIR API's to write to the EHR - just add an extension!

EHR Write Back Options:

SMART Health App
Directly to the EHR
Standalone App (not recommended)
Method
Application that launches within the EHR and uses the provider’s login & context
Data is written directly into the EHR via HL7 or EHR APIs
Separate application that is externally accessible via the web
Benefits
    Control the full UI/UX
    Any data is supported - No extra login
    Embedded within the EHR
    Data shows up in the EHR
    The provider has consistent data everywhere they navigate, CDS Hook support
    No dependence on IT to approve or launch the app
    Supports any data, full UX/UI control
Limitations
    Data may not show up within other screens in the EHR
    Only supported on limited set of EHRs
    Cannot control the UX/UI
    Limited to data supported by the EHR
    May require extra political hurdles
    Requires extra login - Data does not show up within the EHR
    Not easily discoverable

To get started

    1.
    Add a standard FHIR extension attribute to the FHIR resource
    2.
    The valueString is the 1upHealth id for the health system which you can get via our Connect API
    3.
    The url must always be https://1up.health/dev/concept/doc/1uphealth-system-write-identifier for us to write data back
1
"extension": [
2
{
3
"url": "https://1up.health/dev/concept/doc/1uphealth-system-write-identifier",
4
"valueString": "1234"
5
}
6
]
Copied!
Services under the hood at 1up identify the health system's EHR and invoke the service specific transformation for that EHR and health system to write data back. Behind the scenes, we ensure that your application has the proper BAA relationship with the health system before any data is written back (and read for the matter). Below, is a full curl command to post a DocumentReference resource (STU3 version) to 1upHealth.
1
curl -XPOST 'https://api.1up.health/stu3/DocumentReference' \
2
-H 'Authorization: Bearer oneup_access_token' \
3
-H 'Content-Type: application/json' \
4
-d '{... json fhir resource object}'
Copied!
An example format for the JSON FHIR resource would look like this. Note: the addition of the extension attribute.
1
{
2
"resourceType": "DocumentReference",
3
"extension": [
4
{
5
"url": "https://1up.health/dev/concept/doc/1uphealth-system-write-identifier",
6
"valueString": "1234"
7
}
8
],
9
"subject": {
10
"reference": "Patient/4gsdbvjhv"
11
},
12
"content": [
13
{
14
"attachment": {
15
"contentType": "application/html",
16
"url": "https://api.1up.health/stu3/Binary/ed16c91be4d2"
17
},
18
"format": {
19
"display": "History and Physical Specification"
20
}
21
}
22
],
23
"id": "12345",
24
"indexed": "2018-02-20T03:58:05.410Z",
25
"status": "current",
26
}
Copied!

Questions?

Reach out to our engineering team at: [email protected]
Last modified 8mo ago