FAQs

We support extensions for all FHIR resources. You can test the conformance of any resource on each resource page, such as the Patient DSTU2 resource or using the API.

For example see this patient resource with the extension that you can paste into the validator.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
{    
    "id": "1", 
    "name": [
        {
            "given":["Scott"]
            }
        ], 
    "extension":[
        {
            "valueString":"abc", 
            "url":"http://domain.com/ext"
            }
    ]
}

Yes. All of the FHIR endpoints are implemented. For example, the Subscription endpoint (/dev/doc/fhir-subscription) is supported.

There are some parameters or esoteric access patterns which are not currently included.

Most health systems support the following resources in the FHIR format.

DSTU2 is the supported FHIR version for most systems.

• Patient

• Practitioner

• AllergyIntolerance

• MedicationOrder

• MedicationStatement

• Condition

• Observation

• FamilyMemberHistory

• DiagnosticReport

• Immunization

• Encounter

• CarePlan

• Goal

• Procedure

• Device

• DocumentReference

• Binary

• Appointment

Medicare patients receive data for claims from which we can extract clinical information.

STU3 is the supported version for Medicare.

The following resources are available:

• Patient

• ExplanationOfBenefit

• ReferralRequest

• Coverage

Yes. OAuth is required for testing. To get started you can select one of these options.

• Perform the OAuth step manually once, and store the token on your machine for future tests.

• Use a browserless webdriver (such as Selenium) to complete the OAuth workflow using the test credentials.

Yes. We support all FHIR R4 Resources.

This is important if you are a payer to meet the Cures Act interoperability mandates.

• Patient

• Practitioner

• PractitionerRole

• RelatedPerson

• Person

• Group

• Organization

• OrganizationAffiliation

• HeathcareService

• Endpoint

• Location

• Substance

• BiologicallyDerivedProduct

• Device

• DeviceMetric

• Task

• Appointment

• AppointmentResponse

• Schedule

• Slot

• VerificationResult

• AllergyIntolerance

• Encounter

• EpisodeOfCare

• Flag

• List

• Library

• AllergyIntolerance

• AdverseEvent

• Condition

• Procedure

• FamilyMemberHistory

• ClinicalImpression

• DetectedIssue

• Observation

• Media

• DiagnosticReport

• Specimen

• BodyStructure

• ImagingStudy

• QuestionnaireResponse

• MolecularSequence

• MedicationRequest

• MedicationAdministration

• MedicationDispense

• MedicationStatement

• Medication

• MedicationKnowledge

• Immunization

• ImmunizationEvaluation

• ImmunizationRecommendation

• CarePlan

• CareTeam

• Goal

• ServiceRequest

• NutritionOrder

• VisionPrescription

• RiskAssessment

• RequestGroup

• Communication

• CommunicationRequest

• DeviceRequest

• DeviceUseStatement

• GuidanceResponse

• SupplyRequest

• SupplyDelivery

• Coverage

• CoverageEligibilityRequest

• CoverageEligibilityResponse

• EnrollmentRequest

• EnrollmentResponse

• Claim

• ClaimResponse

• Invoice

• PaymentNotice

• PaymentReconciliation

• Account

• ChargeItem

• ChargeItemDefinition

• Contract

• ExplanationOfBenefit

• InsurancePlan

• HealthCareService

• Endpoint

• Network

Yes. 1upHealth supports all FHIR STU3 Resources.

You can query any newly imported or created resource using a URL with the following format, which includes the target and the full resource URL:

https://api.1up.health/fhir/dstu2/Provenance?target=Patient/${patientId}/_history/${versionId}

For STU3, use a URL with the following format:

  https://api.1up.health/fhir/stu3/Provenance?target=Patient/${patientId}/_history/${versionId}

You can make changes to externally linked data that is pulled in using the Connect API without source providers overwriting your data. Because data from source systems such as EHRs and wearable devices is synced at least every five minutes, any updates made by your app might be overwritten by the background sync from 1upHealth.

To modify or save changes to data from source systems, you must create a new unique resource and change the data in that resource. The new resource you create will not be linked to the back-end data sync. If there are multiple provider systems, your application logic can use data from multiple systems and apply changes to the new unique resource.

1upHealth offers demo patient records from multiple EHR vendors with data to test extracting data through the FHIR API.

You can use the 1up FHIR test credentials to connect to the test records.

You can integrate data from any of the 1upHealth supported health systems with FHIR data in just a few minutes. Because 1upHealth uses patient authorization, you don’t need any prior relationship with the healths systems we support.

All data is transmitted and linked through RESTful APIs, which means you don’t have to understand specialized healthcare technologies. All data is stored on the 1upHealth platform, so you don’t need to build your own HIPAA-compliant database.

After a patient connects to a health care system or device using the 1upHealth connect API, the user's access token provides access to data almost immediately, with no more than a few second delay.

A server-side process updates the data every five minutes.

Access Tokens, Refresh Tokens, and Access Codes expire after 7200 seconds. You can get only one refresh token for an accessToken. You can get a new pair of access and refresh token anytime before the two-hour expiration period.

For instructions to get new tokens, see Get Access to User Data.

A user can be many things depending on the situation. A user can be a patient, a provider, or a back-end service. Because of this complexity, there are separate entities for the PaitentResourceId and the OneupUserId.

You can use the User API to create separate users for each patient. You can also create users with the 1upHealth User Management API.

An  app_user_id  is generated when you create a new user on 1upHealth.

For more information about 1upHealth users and how to them, see User Management APIs.

FLAT FHIR, FHIR Bulk Data, and Bulk FHIR are all the same. The official HL7 standard refer to FHIR Bulk Data, which is synonymous with FLAT FHIR and Bulk FHIR.

For more information about FHIR Bulk Data, FLAT FHIR, and Bulk FHIR, see Bulk Data Export (Multi Tenant).

You can run a query to get all data associated to an individual patient. You can also use query parameters to search for specific data associated with a patient.

1
2
curl -X GET 'https://api.1up.health/fhir/dstu2/Patient/{patient_id}/$everything' \ 
    -H "Authorization: Bearer accesstokenaccesstoken"

For more information, see Get Patient Data.