Write to EHRs

1upHealth makes writing back to multiple EHRs easy with a single end point. You simply add a standar FHIR extension attribute to the FHIR resource. The valueString is the 1upHealth id for the health system which you can get via our Connect API. The url must always be https://1up.health/dev/concept/doc/1uphealth-system-write-identifier for us to write data back.

  
  "extension": [
    {
      "url": "https://1up.health/dev/concept/doc/1uphealth-system-write-identifier",
      "valueString": "1234"
    }
  ],
  

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.

  
  curl -XPOST 'https://api.1up.health/fhir/stu3/DocumentReference' \
    -H 'Authorization: Bearer oneup_access_token' \
    -H 'Content-Type: application/json' \
    -d '{... json fhir resource object}'  
  

An example format for the JSON FHIR resource would look like this. Note: the addition of the extension attribute.

  
  {
    "resourceType": "DocumentReference",
    "extension": [
      {
        "url": "https://1up.health/dev/concept/doc/1uphealth-system-write-identifier",
        "valueString": "1234"
      }
    ],
    "subject": {
      "reference": "Patient/4gsdbvjhv"
    },
    "content": [
      {
        "attachment": {
          "contentType": "application/html",
          "url": "https://api.1up.health/fhir/stu3/Binary/ed16c91be4d2"
        },
        "format": {
          "display": "History and Physical Specification"
        }
      }
    ],
    "id": "12345",
    "indexed": "2018-02-20T03:58:05.410Z",
    "status": "current",
  }