FHIR API Documentation

Compulink Advantage 14
US Core 6.1.0 | USCDI v3 Certified

Table of Contents

1. Introduction

This guide is written for third party developers, including patients, who are developing software applications for accessing Protected Health Information (PHI) based on this public API documentation which allows applications to query secured health information.

US Core 6.1.0 / USCDI v3 Compliance
This API implementation is certified to support US Core Implementation Guide version 6.1.0 and USCDI v3 data elements. It has been tested against FHIR Inferno validation suites to ensure full conformance with ONC Health IT Certification requirements.

Applications wishing to publish such a public-facing API should have their Health IT vendor register as a developer integrator of services at https://www.compulinkadvantage.com/apipartner/.

2. Registration & Authentication

a. Application Access Requests

The API is a read-only RESTful HL7 FHIR® R4 API and follows the syntax described at https://hl7.org/fhir/R4/http.html.

All RESTful data access requests will be in the following format, in which the [base] URL will need to be obtained from the Data Holder, either directly or via directory information:

GET [base]/[resource-specific parameters]

FHIR Bulk Data Access Group export is also supported as described in the Bulk Data Access IG.

b. Connecting to the Server

The server is accessed by clients through an HTTPS connection.

Important Security Requirement
Only TLS 1.2 or higher connections are accepted. All plaintext connections will be refused.

c. Authentication - Registering an Application

Prior to making API requests, the client application must obtain an Access Token from the Compulink FHIR Registration Server. The client software must support OAuth 2.0 authorization code grant. For authorization code flow, a client ID and client secret are required.

If the client application does not have a client ID and client secret for this purpose, the client application may obtain a client ID and client secret by contacting the data owner or by completing the manual registration process at https://www.compulinkadvantage.com/apipartner/.

When an end user is directed to the authorization endpoint, the user will be presented with a login screen where they can enter their credentials. If the correct credentials are supplied and the end user grants access to the client application, an authorization code will be returned to the client that the client application can use to obtain an access token through the token endpoint as described in RFC 6749.

Each healthcare organization has a unique base URL that is used to access its Authorization Server. The required endpoint URLs are of the following form:

Endpoint URL
Base https://fhir.compulinkadvantage.com/[client_unique]/
Authorization https://fhir.compulinkadvantage.com/[client_unique]/authorize
Token https://oauth.compulinkadvantage.com/token

d. Authentication - Refresh Token

Client apps that use the authorization code flow and can securely store refresh tokens may request a refresh token by including the offline_access scope in the initial authorization endpoint request. Note that the end user may remove this scope during the authorization process.

If a refresh token is permitted, it will be returned together with the access token as per RFC 6749, and can be exchanged for a new access token as per RFC 6749. Refresh token lifetime defaults to 90 days (but may be longer or shorter depending on the Data Holder's institutional policies).

e. Authentication - Additional Users/Patient

Once an application is registered the data owner will have the ability to use the Compulink Advantage software to add or remove users and control scopes for each user.

f. Revoking Authentication

Once an application is registered the data owner will have the ability to use the Compulink Advantage software to revoke access to an application or user.

3. API Details

a. FHIR Resources by USCDI v3 Domain

Resources are organized by USCDI v3 data class domains and conform to US Core 6.1.0 profiles for ONC (g)(10) certification.

Quick Reference: Resource Coverage

USCDI v3 Required Resources: Patient, AllergyIntolerance, CarePlan, CareTeam, Condition (Problems & Health Concerns), Condition (Encounter Diagnosis), Coverage, Device, DiagnosticReport, DocumentReference, Encounter, Goal, Immunization, Location, MedicationRequest, Observation (Laboratory, Vital Signs, Smoking Status, Clinical Result, Screening Assessment), Procedure, Provenance, RelatedPerson, ServiceRequest, Specimen

Supporting Resources: Practitioner, PractitionerRole, Organization

USCDI v3 Domain: Patient Demographics

Allergies and Intolerances - US Core AllergyIntolerance Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? AllergyIntolerance resource

Supported Elements:
Resource Data Element Data Type
AllergyIntolerance.clinicalStatusSTRING
AllergyIntolerance.verificationStatusSTRING
AllergyIntolerance.codeRxNorm, SNOMED CT
AllergyIntolerance.patientREFERENCE
AllergyIntolerance.reaction-
AllergyIntolerance.reaction.manifestationSTRING, SNOMED CT
AllergyIntolerance.recordedDateDATE
AllergyIntolerance.onsetDateTimeDATE
AllergyIntolerance.onsetDATE
AllergyIntolerance.noteSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Substance (Drug Class)RxNorm
Substance (Medication)SNOMED CT
ReactionSNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/AllergyIntolerance?patient=[patient_unique]

MedicationRequest - US Core MedicationRequest Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: MedicationRequest | USCDI v3 Domain: Medications

Supported Elements:
Resource Data Element Data Type
MedicationRequest.statusSTRING
MedicationRequest.intentSTRING
MedicationRequest.medication[x]RxNorm
MedicationRequest.subjectREFERENCE
MedicationRequest.authoredOnDATETIME
MedicationRequest.requesterREFERENCE
MedicationRequest.dosageInstruction-
MedicationRequest.dosageInstruction.textSTRING
MedicationRequest.encounterREFERENCE
MedicationRequest.reportedBooleanBOOLEAN
USCDI v3 Element Types:
USCDI Element Supported Type
MedicationsRxNorm
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
intentFilter by intent
statusFilter by status
Example:
https://fhir.compulinkadvantage.com/[client_unique]/MedicationRequest?_revinclude=Provenance:target&intent=proposal&patient=[patient_unique]

USCDI v3 Domain: Care Team & Care Planning

CarePlan - US Core CarePlan Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: CarePlan | USCDI v3 Domain: Assessment and Plan of Treatment

Supported Elements:
Resource Data Element Data Type
CarePlan.category-
CarePlan.category:AssessPlanFIXED
CarePlan.intentSTRING
CarePlan.statusSTRING
CarePlan.subjectREFERENCE
CarePlan.textSTRING
CarePlan.text.statusSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Assessment and Plan of TreatmentN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
categoryFilter by category
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/CarePlan?category=assess-plan&patient=[patient_unique]

CareTeam - US Core CareTeam Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: CareTeam | USCDI v3 Domain: Care Team and Care Coordination

Supported Elements:
Resource Data Element Data Type
CareTeam.participant-
CareTeam.participant.memberSTRING
CareTeam.participant.roleSTRING
CareTeam.statusSTRING
CareTeam.subjectREFERENCE
CareTeam.encounterREFERENCE
USCDI v3 Element Types:
USCDI Element Supported Type
Care Team MembersN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
statusFilter by status
Example:
https://fhir.compulinkadvantage.com/[client_unique]/CareTeam?patient=[patient_unique]&status=proposed

Goal - US Core Goal Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Goal | USCDI v3 Domain: Goals and Preferences

Supported Elements:
Resource Data Element Data Type
Goal.descriptionSTRING
Goal.lifecycleStatusSTRING
Goal.subjectREFERENCE
Goal.target.dueDateDATE
USCDI v3 Element Types:
USCDI Element Supported Type
Patient GoalsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Goal?patient=[patient_unique]

USCDI v3 Domain: Clinical Notes & Documents

DocumentReference - US Core DocumentReference Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: DocumentReference | USCDI v3 Domain: Clinical Notes

Supported Elements:
Resource Data Element Data Type
DocumentReference.authorREFERENCE
DocumentReference.categorySTRING
DocumentReference.content-
DocumentReference.content.attachment-
DocumentReference.content.attachment.contentTypeSTRING
DocumentReference.content.attachment.urlURL
DocumentReference.content.formatSTRING
DocumentReference.context.periodDATE
DocumentReference.custodianREFERENCE
DocumentReference.encounterREFERENCE
DocumentReference.dateDATE
DocumentReference.identifierINTEGER
DocumentReference.statusSTRING
DocumentReference.subjectREFERENCE
DocumentReference.typeLOINC
USCDI v3 Element Types:
USCDI Element Supported Type
Consultation NoteLOINC
Discharge Summary Note
History & Physical
Progress Note
Imaging Narrative
Procedure Note
Laboratory Report Narrative
Pathology Report Narrative
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
typeFilter by type
categoryFilter by category
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/DocumentReference?patient=[patient_unique]

DiagnosticReport (Notes) - US Core DiagnosticReport Profile for Report and Note Exchange

US Core 6.1.0 USCDI v3 Required

FHIR Resource: DiagnosticReport | USCDI v3 Domain: Clinical Notes

Supported Elements:
Resource Data Element Data Type
DiagnosticReport.categoryLOINC
DiagnosticReport.codeLOINC
DiagnosticReport.effectiveDateTimeDATETIME
DiagnosticReport.encounterREFERENCE
DiagnosticReport.issuedDATETIME
DiagnosticReport.performerREFERENCE
DiagnosticReport.presentedForm.URLREFERENCE
DiagnosticReport.statusSTRING
DiagnosticReport.subjectREFERENCE
DiagnosticReport.presentedFormLOINC
USCDI v3 Element Types:
USCDI Element Supported Type
Imaging NarrativeLOINC
Procedure Note
Laboratory Report Narrative
Pathology Report Narrative
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
codeFilter by code
categoryFilter by category
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/DiagnosticReport?_revinclude=Provenance:target&category=LP29684-5&patient=[patient_unique]

USCDI v3 Domain: Laboratory

DiagnosticReport (Laboratory) - US Core DiagnosticReport Profile for Laboratory Results Reporting

US Core 6.1.0 USCDI v3 Required

FHIR Resource: DiagnosticReport | USCDI v3 Domain: Laboratory

Supported Elements:
Resource Data Element Data Type
DiagnosticReport.categoryLOINC
DiagnosticReport.codeLOINC
DiagnosticReport.effectiveDateTimeDATETIME
DiagnosticReport.encounterREFERENCE
DiagnosticReport.issuedDATETIME
DiagnosticReport.performerREFERENCE
DiagnosticReport.statusSTRING
DiagnosticReport.subjectREFERENCE
DiagnosticReport.presentedFormLOINC
DiagnosticReport.resultREFERENCE
USCDI v3 Element Types:
USCDI Element Supported Type
TestsLOINC
ResultsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
codeFilter by code
categoryFilter by category
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/DiagnosticReport?category=LAB&patient=[patient_unique]

Observation (Laboratory) - US Core Laboratory Result Observation Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Observation | USCDI v3 Domain: Laboratory

Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.categoryFIXED (laboratory)
Observation.codeLOINC
Observation.subjectREFERENCE
Observation.effectiveDateTimeDATE
Observation.valueQuantity-
Observation.valueQuantity.valueSTRING
Observation.valueQuantity.unitSTRING
Observation.referenceRange-
Observation.referenceRange.low.valueSTRING
Observation.referenceRange.low.unitSTRING
Observation.referenceRange.high.valueSTRING
Observation.referenceRange.high.unitSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
TestsLOINC
ResultsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?category=laboratory&patient=[patient_unique]

ServiceRequest - US Core ServiceRequest Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: ServiceRequest | USCDI v3 Domain: Laboratory & Diagnostic Imaging Orders

Supported Elements:
Resource Data Element Data Type
ServiceRequest.statusSTRING
ServiceRequest.intentSTRING
ServiceRequest.categoryCodeableConcept (SNOMED CT, LOINC)
ServiceRequest.codeCodeableConcept (SNOMED CT, LOINC, CPT, HCPCS)
ServiceRequest.subjectREFERENCE (Patient)
ServiceRequest.authoredOnDATETIME
ServiceRequest.requesterREFERENCE (Practitioner, Organization)
USCDI v3 Element Types:
USCDI Element Supported Type
Laboratory Service OrdersLOINC
Diagnostic Imaging Service OrdersLOINC, SNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
authoredFilter by authored date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/ServiceRequest?patient=[patient_unique]&category=108252007

Specimen - US Core Specimen Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Specimen | USCDI v3 Domain: Laboratory

Supported Elements:
Resource Data Element Data Type
Specimen.identifierIdentifier
Specimen.accessionIdentifierIdentifier
Specimen.typeCodeableConcept (SNOMED CT)
Specimen.subjectREFERENCE (Patient)
Specimen.collection-
Specimen.collection.collectedDateTimeDATETIME
USCDI v3 Element Types:
USCDI Element Supported Type
Specimen TypeSNOMED CT
Specimen IdentifierN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Specimen?patient=[patient_unique]

USCDI v3 Domain: Vital Signs & Clinical Observations

Goals - US Core Goal Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Goal resource

Supported Elements:
Resource Data Element Data Type
Goal.descriptionSTRING
Goal.lifecycleStatusSTRING
Goal.subjectREFERENCE
Goal.target.dueDateDATE
USCDI v3 Element Types:
USCDI Element Supported Type
Patient GoalsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Goal?patient=[patient_unique]

Health Concerns - US Core Condition Problems and Health Concerns Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Condition resource

Supported Elements:
Resource Data Element Data Type
Condition.categorySTRING, SNOMED CT
Condition.clinicalStatusSTRING
Condition.codeICD-10, SNOMED CT
Condition.subjectREFERENCE
Condition.verificationStatusSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Health ConcernsICD-10, SNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]

Problems - US Core Condition Problems and Health Concerns Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Condition resource

Supported Elements:
Resource Data Element Data Type
Condition.categorySTRING, SNOMED CT
Condition.clinicalStatusSTRING
Condition.codeSNOMED CT
Condition.subjectREFERENCE
Condition.verificationStatusSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
ProblemsSNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]

Immunizations - US Core Immunization Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Immunization resource

Supported Elements:
Resource Data Element Data Type
Immunization.statusSTRING
Immunization.statusReasonSTRING
Immunization.vaccineCodeCVX
Immunization.patientREFERENCE
Immunization.occurrenceStringSTRING, DATETIME
Immunization.primarySourceBOOLEAN
USCDI v3 Element Types:
USCDI Element Supported Type
ImmunizationCVX
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Immunization?patient=[patient_unique]

Medications - US Core MedicationRequest Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? MedicationRequest resource

Supported Elements:
Resource Data Element Data Type
MedicationRequest.statusSTRING
MedicationRequest.intentSTRING
MedicationRequest.medication[x]RxNorm
MedicationRequest.subjectREFERENCE
MedicationRequest.authoredOnDATETIME
MedicationRequest.requesterREFERENCE
MedicationRequest.dosageInstruction-
MedicationRequest.dosageInstruction.textSTRING
MedicationRequest.encounterREFERENCE
MedicationRequest.reportedBooleanBOOLEAN
USCDI v3 Element Types:
USCDI Element Supported Type
MedicationsRxNorm
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
intentFilter by intent
statusFilter by status
Example:
https://fhir.compulinkadvantage.com/[client_unique]/MedicationRequest?_revinclude=Provenance:target&intent=proposal&patient=[patient_unique]

Procedures - US Core Procedure Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Procedure resource

Supported Elements:
Resource Data Element Data Type
Procedure.statusSTRING
Procedure.codeSNOMED CT, CPT, HCPCS
Procedure.subjectREFERENCE
Procedure.performedDateTimeDATE
USCDI v3 Element Types:
USCDI Element Supported Type
ProceduresSNOMED CT, CPT, HCPCS
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Procedure?patient=[patient_unique]

Unique Device Identifier(s) for Patient's Implantable Device(s) - US Core Implantable Device Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Device resource

Supported Elements:
Resource Data Element Data Type
Device.udiCarrierSTRING
Device.udiCarrier.deviceIdentifierSTRING
Device.udiCarrier.carrierAIDC or Device.udiCarrier.carrierHRFSTRING
Device.distinctIdentifierSTRING
Device.manufactureDateDATE
Device.expirationDateDATE
Device.lotNumberINTEGER
Device.serialNumberSTRING
Device.typeSNOMED CT
Device.patientREFERENCE
USCDI v3 Element Types:
USCDI Element Supported Type
Unique Device IdentifierUDI
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Device?_revinclude=Provenance:target&patient=[patient_unique]

Laboratory - US Core Laboratory Result Observation Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Observation resource (may be referenced in DiagnosticReport resource)

Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.categoryFIXED (laboratory)
Observation.codeLOINC
Observation.subjectREFERENCE
Observation.effectiveDateTimeDATE
Observation.valueQuantity-
Observation.valueQuantity.valueSTRING
Observation.valueQuantity.unitSTRING
Observation.referenceRange-
Observation.referenceRange.low.valueSTRING
Observation.referenceRange.low.unitSTRING
Observation.referenceRange.high.valueSTRING
Observation.referenceRange.high.unitSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
TestsLOINC
ResultsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?category=laboratory&patient=[patient_unique]

Smoking Status - US Core Smoking Status Observation Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Observation resource

Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.codeFIXED (72166-2)
Observation.subjectREFERENCE
Observation.issuedDATE
Observation.value[x]:valueCodeableConceptSNOMED CT
USCDI v3 Element Types:
USCDI Element Supported Type
Smoking StatusSNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
codeFilter by code
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?code=72166-2&patient=[patient_unique]

Vital Signs - US Core Vital Signs Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Observation resource

Available Vital Signs Panel Options:
  • Diastolic Blood Pressure - Blood pressure systolic and diastolic (FHIR Core Profile)
  • Systolic Blood Pressure - Blood pressure systolic and diastolic (FHIR Core Profile)
  • Body Height - Body height (FHIR Core Profile)
  • Body Weight - Body weight (FHIR Core Profile)
  • Heart Rate - Heart rate (FHIR Core Profile)
  • Respiratory Rate - Respiratory rate (FHIR Core Profile)
  • Body Temperature - Body temperature (FHIR Core Profile)
  • Pulse Oximetry - US Core Pulse Oximetry Profile
  • Inhaled Oxygen Concentration - US Core Pulse Oximetry Profile
  • BMI Percentile (2-20 years old) - US Core Pediatric BMI for Age Observation Profile
  • Weight-for-Length Percentile (Birth-36 months) - US Core Pediatric Weight for Height Observation Profile
  • Occipital-frontal Head Circumference Percentile (Birth-36 months) - US Core Pediatric Head Occipital-Frontal Circumference Observation Profile
Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.category-
Observation.category.coding.codeFIXED (vital-signs)
Observation.code.coding.codeLOINC
Observation.subjectREFERENCE
Observation.effectiveDateTimeDATE
Observation.value[x]-
Observation.value[x]:valueQuantitySTRING
Observation.value[x].valueSTRING
Observation.value[x].unitSTRING
Observation.value[x].systemSTRING
Observation.value[x].codeLOINC
USCDI v3 Element Types:
USCDI Element Supported Type
Systolic Blood PressureLOINC
Diastolic Blood Pressure
Heart Rate
Respiratory Rate
Body Temperature
Body Height
Body Weight
Pulse Oximetry
Inhaled Oxygen Concentration
BMI Percentile (2-20 years)
Weight-for-Length Percentile (Birth-36 months)
Head Occipital-Frontal Circumference Percentile (Birth-36 months)
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?category=vital-signs&patient=[patient_unique]

Health Insurance Information - US Core Coverage Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Coverage resource

Supported Elements:
Resource Data Element Data Type
Coverage.statusSTRING
Coverage.typeCodeableConcept
Coverage.subscriberIdSTRING
Coverage.beneficiaryREFERENCE (Patient)
Coverage.relationshipCodeableConcept
Coverage.payorREFERENCE (Organization, Patient, RelatedPerson)
Coverage.class-
Coverage.class:group-
Coverage.class:group.typeCodeableConcept (FIXED: group)
Coverage.class:group.valueSTRING (Group Number)
Coverage.class:plan-
Coverage.class:plan.typeCodeableConcept (FIXED: plan)
Coverage.class:plan.valueSTRING (Plan Number)
USCDI v3 Element Types:
USCDI Element Supported Type
Coverage StatusN/A
Coverage TypeN/A
Relationship to SubscriberN/A
Member IdentifierN/A
Subscriber IdentifierN/A
Group NumberN/A
Plan NumberN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Coverage?patient=[patient_unique]

Related Person - US Core RelatedPerson Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? RelatedPerson resource (may be referenced in Coverage and CareTeam resources)

Supported Elements:
Resource Data Element Data Type
RelatedPerson.activeBOOLEAN
RelatedPerson.patientREFERENCE (Patient)
RelatedPerson.relationshipCodeableConcept
RelatedPerson.name-
RelatedPerson.name.familySTRING
RelatedPerson.name.givenSTRING
RelatedPerson.telecom-
RelatedPerson.telecom.systemSTRING
RelatedPerson.telecom.valueSTRING
RelatedPerson.address-
RelatedPerson.address.lineSTRING
RelatedPerson.address.citySTRING
RelatedPerson.address.stateSTRING
RelatedPerson.address.postalCodeSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Related Person NameN/A
Related Person RelationshipN/A
Related Person ContactN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/RelatedPerson?patient=[patient_unique]

Service Request - US Core ServiceRequest Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? ServiceRequest resource

Supported Elements:
Resource Data Element Data Type
ServiceRequest.statusSTRING
ServiceRequest.intentSTRING
ServiceRequest.categoryCodeableConcept (SNOMED CT, LOINC)
ServiceRequest.codeCodeableConcept (SNOMED CT, LOINC, CPT, HCPCS)
ServiceRequest.subjectREFERENCE (Patient)
ServiceRequest.authoredOnDATETIME
ServiceRequest.requesterREFERENCE (Practitioner, Organization)
USCDI v3 Element Types:
USCDI Element Supported Type
Laboratory Service OrdersLOINC
Diagnostic Imaging Service OrdersLOINC, SNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
authoredFilter by authored date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/ServiceRequest?patient=[patient_unique]&category=108252007

Specimen - US Core Specimen Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Specimen resource (may be referenced in DiagnosticReport and Observation resources)

Supported Elements:
Resource Data Element Data Type
Specimen.identifierIdentifier
Specimen.accessionIdentifierIdentifier
Specimen.typeCodeableConcept (SNOMED CT)
Specimen.subjectREFERENCE (Patient)
Specimen.collection-
Specimen.collection.collectedDateTimeDATETIME
USCDI v3 Element Types:
USCDI Element Supported Type
Specimen TypeSNOMED CT
Specimen IdentifierN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Specimen?patient=[patient_unique]

Encounter Diagnosis - US Core Condition Encounter Diagnosis Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Condition resource

Supported Elements:
Resource Data Element Data Type
Condition.categoryCodeableConcept (FIXED: encounter-diagnosis)
Condition.codeCodeableConcept (SNOMED CT, ICD-10-CM)
Condition.subjectREFERENCE (Patient)
Condition.encounterREFERENCE (Encounter)
USCDI v3 Element Types:
USCDI Element Supported Type
Encounter DiagnosisSNOMED CT, ICD-10-CM
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]&category=encounter-diagnosis

Screening and Assessments - US Core Observation Screening Assessment Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Observation resource

US Core 6.1.0 Patch (FHIR-45319)
We support all four codes from the US Core Screening Assessment Observation Category ValueSet:
  • social-history
  • functional-mental-status
  • disability-status
  • cognitive-status
Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.category-
Observation.category:us-coreCodeableConcept
Observation.category:screening-assessmentCodeableConcept (social-history, functional-mental-status, disability-status, cognitive-status)
Observation.codeCodeableConcept (LOINC)
Observation.subjectREFERENCE (Patient)
Observation.effectiveDateTimeDATETIME
Observation.value[x]Multiple types supported
Observation.derivedFromREFERENCE (QuestionnaireResponse, DocumentReference, Observation)
USCDI v3 Element Types:
USCDI Element Supported Type
SDOH AssessmentsLOINC
Functional StatusLOINC
Disability StatusLOINC
Mental/Cognitive StatusLOINC
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?patient=[patient_unique]&category=social-history

Clinical Test Results - US Core Observation Clinical Result Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Observation resource (may be referenced in DiagnosticReport resource)

Supported Elements:
Resource Data Element Data Type
Observation.statusSTRING
Observation.categoryCodeableConcept (clinical-test)
Observation.codeCodeableConcept (LOINC)
Observation.subjectREFERENCE (Patient)
Observation.effectiveDateTimeDATETIME
Observation.value[x]Multiple types supported
USCDI v3 Element Types:
USCDI Element Supported Type
Clinical TestsLOINC
Clinical Test ResultsN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
codeFilter by code
dateFilter by date
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?patient=[patient_unique]&category=clinical-test

Location - US Core Location Profile

US Core 6.1.0

Where is it used? Location resource (may be referenced in Encounter resource)

Supported Elements:
Resource Data Element Data Type
Location.statusSTRING
Location.nameSTRING
Location.telecom-
Location.telecom.systemSTRING
Location.telecom.valueSTRING
Location.address-
Location.address.lineSTRING
Location.address.citySTRING
Location.address.stateSTRING
Location.address.postalCodeSTRING
Location.managingOrganizationREFERENCE (Organization)
Search Methods:
Search Type
idDirect result
_searchSearch results
nameFilter by name
addressFilter by address
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Location/[location_unique]

Practitioner Role - US Core PractitionerRole Profile

US Core 6.1.0

Where is it used? PractitionerRole resource (may be referenced in CareTeam, Encounter resources)

Supported Elements:
Resource Data Element Data Type
PractitionerRole.practitionerREFERENCE (Practitioner)
PractitionerRole.organizationREFERENCE (Organization)
PractitionerRole.codeCodeableConcept
PractitionerRole.specialtyCodeableConcept
PractitionerRole.locationREFERENCE (Location)
PractitionerRole.telecom-
PractitionerRole.telecom.systemSTRING
PractitionerRole.telecom.valueSTRING
PractitionerRole.endpointREFERENCE (Endpoint)
Search Methods:
Search Type
idDirect result
_searchSearch results
specialtyFilter by specialty
practitionerFilter by practitioner
Example:
https://fhir.compulinkadvantage.com/[client_unique]/PractitionerRole/[practitionerrole_unique]

Patient - US Core Patient Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Patient resource (may also be referenced in AllergyIntolerance, CarePlan, CareTeam, Condition, Device, DiagnosticReport, DocumentReference, Goal, Immunization, MedicationRequest, Observation, Procedure, and Encounter resources)

Supported Elements:
Resource Data Element Data Type
Patient.identifierREFERENCE
Patient.name-
Patient.name.familySTRING
Patient.name.givenSTRING
Patient.name.suffixSTRING
Patient.name.period.startDATE
Patient.name.period.endDATE
Patient.birthDateDATE
Patient.genderSTRING
Patient.address-
Patient.address.lineSTRING
Patient.address.citySTRING
Patient.address.stateSTRING
Patient.address.postalCodeSTRING
Patient.address.periodDATE
Patient.telecom-
Patient.telecom.useSTRING
Patient.telecom.valueSTRING
Patient.communication-
Patient.communication.languageSTRING
Patient.extension:raceSTRING
Patient.extension:ethnicitySTRING
Patient.extension:birthsexSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
First NameN/A
Last NameN/A
Middle NameN/A
SuffixN/A
Previous NameN/A
Date of BirthN/A
Sex (Birth)See 45 CFR 170.207(n)
RaceSee 45 CFR 170.207(f)
EthnicitySee 45 CFR 170.207(f)
Preferred LanguageSee 45 CFR 170.207(g)
Current AddressN/A
Previous AddressN/A
Phone NumberSee 45 CFR 170.207(q)(1)
Phone Number TypeN/A
Email AddressN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
birthdateFilter by birth date
nameFilter by name
genderFilter by gender
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Patient?birthdate=1980-12-01&name=SAMPLE

RelatedPerson - US Core RelatedPerson Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: RelatedPerson | USCDI v3 Domain: Patient Demographics

Supported Elements:
Resource Data Element Data Type
RelatedPerson.activeBOOLEAN
RelatedPerson.patientREFERENCE (Patient)
RelatedPerson.relationshipCodeableConcept
RelatedPerson.name-
RelatedPerson.name.familySTRING
RelatedPerson.name.givenSTRING
RelatedPerson.telecom-
RelatedPerson.telecom.systemSTRING
RelatedPerson.telecom.valueSTRING
RelatedPerson.address-
RelatedPerson.address.lineSTRING
RelatedPerson.address.citySTRING
RelatedPerson.address.stateSTRING
RelatedPerson.address.postalCodeSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Related Person NameN/A
Related Person RelationshipN/A
Related Person ContactN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/RelatedPerson?patient=[patient_unique]

USCDI v3 Domain: Health Insurance

Coverage - US Core Coverage Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Coverage | USCDI v3 Domain: Health Insurance Information

Supported Elements:
Resource Data Element Data Type
Coverage.statusSTRING
Coverage.typeCodeableConcept
Coverage.subscriberIdSTRING
Coverage.beneficiaryREFERENCE (Patient)
Coverage.relationshipCodeableConcept
Coverage.payorREFERENCE (Organization, Patient, RelatedPerson)
Coverage.class-
Coverage.class:group-
Coverage.class:group.typeCodeableConcept (FIXED: group)
Coverage.class:group.valueSTRING (Group Number)
Coverage.class:plan-
Coverage.class:plan.typeCodeableConcept (FIXED: plan)
Coverage.class:plan.valueSTRING (Plan Number)
USCDI v3 Element Types:
USCDI Element Supported Type
Coverage StatusN/A
Coverage TypeN/A
Relationship to SubscriberN/A
Member IdentifierN/A
Subscriber IdentifierN/A
Group NumberN/A
Plan NumberN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Coverage?patient=[patient_unique]

USCDI v3 Domain: Problems & Health Concerns

Condition (Health Concerns) - US Core Condition Problems and Health Concerns Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Condition | USCDI v3 Domain: Problems & Health Concerns

Supported Elements:
Resource Data Element Data Type
Condition.categorySTRING, SNOMED CT (health-concern)
Condition.clinicalStatusSTRING
Condition.codeICD-10, SNOMED CT
Condition.subjectREFERENCE
Condition.verificationStatusSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Health ConcernsICD-10, SNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]&category=health-concern

Condition (Problems) - US Core Condition Problems and Health Concerns Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Condition | USCDI v3 Domain: Problems & Health Concerns

Supported Elements:
Resource Data Element Data Type
Condition.categorySTRING, SNOMED CT (problem-list-item)
Condition.clinicalStatusSTRING
Condition.codeSNOMED CT
Condition.subjectREFERENCE
Condition.verificationStatusSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
ProblemsSNOMED CT
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]&category=problem-list-item

Condition (Encounter Diagnosis) - US Core Condition Encounter Diagnosis Profile

US Core 6.1.0 USCDI v3 Required

FHIR Resource: Condition | USCDI v3 Domain: Problems & Health Concerns

Supported Elements:
Resource Data Element Data Type
Condition.categoryCodeableConcept (FIXED: encounter-diagnosis)
Condition.codeCodeableConcept (SNOMED CT, ICD-10-CM)
Condition.subjectREFERENCE (Patient)
Condition.encounterREFERENCE (Encounter)
USCDI v3 Element Types:
USCDI Element Supported Type
Encounter DiagnosisSNOMED CT, ICD-10-CM
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
categoryFilter by category
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Condition?patient=[patient_unique]&category=encounter-diagnosis

USCDI v3 Domain: Medications & Allergies

c. Additional Categories

These requests are available but may not be specific to a patient.

Encounter - US Core Encounter Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Encounter resource (may also be referenced in CareTeam, Condition, DiagnosticReport, DocumentReference, and MedicationRequest resources)

Supported Elements:
Resource Data Element Data Type
Encounter.statusSTRING
Encounter.class-
Encounter.typeSTRING
Encounter.subjectREFERENCE
Encounter.participant-
Encounter.participant.typeSTRING
Encounter.participant.periodDATE
Encounter.participant.individualREFERENCE
Encounter.periodDATE
Encounter.reasonCodeSTRING
Encounter.hospitalizationSTRING
Encounter.hospitalization.dischargeDispositionSTRING
Encounter.location-
Encounter.location.locationREFERENCE
Search Methods:
Search Type
idDirect result
_searchSearch results
patientPatient results
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Encounter/[encounter_unique]

Practitioner - US Core Practitioner Profile

US Core 6.1.0

Where is it used? Practitioner resource (may also be referenced in CareTeam, DiagnosticReport, DocumentReference, MedicationRequest, and Encounter resources)

Supported Elements:
Resource Data Element Data Type
Practitioner.identifier-
Practitioner.identifier.valueNPI
Practitioner.name-
Practitioner.name.familySTRING
Practitioner.name.givenSTRING
Practitioner.name.prefixSTRING
Practitioner.name.suffixSTRING
Practitioner.telecom-
Practitioner.telecom.useSTRING
Practitioner.telecom.valueSTRING
Practitioner.address-
Practitioner.address.lineSTRING
Practitioner.address.citySTRING
Practitioner.address.stateSTRING
Practitioner.address.postalCodeSTRING
Search Methods:
Search Type
idDirect result
_searchSearch results
nameFilter by name
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Practitioner/[practitioner_unique]

Organization - US Core Organization Profile

US Core 6.1.0

Where is it used? Organization resource (may also be referenced in Encounter and Provenance resources)

Supported Elements:
Resource Data Element Data Type
Organization.activeBOOLEAN
Organization.identifierNPI
Organization.nameSTRING
Organization.telecom-
Organization.telecom.systemSTRING
Organization.telecom.valueSTRING
Organization.address-
Organization.address.lineSTRING
Organization.address.citySTRING
Organization.address.stateSTRING
Organization.address.postalCodeSTRING
Organization.address.countrySTRING
Search Methods:
Search Type
idDirect result
_searchSearch results
nameFilter by name
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Organization/[organization_unique]

Provenance - US Core Provenance Profile

US Core 6.1.0 USCDI v3 Required

Where is it used? Provenance resource (may be referenced with any clinical resource to track authorship and data origin)

Supported Elements:
Resource Data Element Data Type
Provenance.targetREFERENCE
Provenance.recordedDATETIME
Provenance.agent-
Provenance.agent.typeSTRING
Provenance.agent.type.coding.codeSTRING
Provenance.agent.whoREFERENCE
Provenance.agent.onBehalfOfREFERENCE
Provenance.agent:ProvenanceAuthorSTRING
Provenance.agent:ProvenanceTransmitterSTRING
USCDI v3 Element Types:
USCDI Element Supported Type
Author Time StampN/A
Author OrganizationN/A
Search Methods:
Search Type
idDirect result
_searchSearch results
_revinclude=Provenance:targetInclude in other resources
Example:
https://fhir.compulinkadvantage.com/[client_unique]/Observation?_revinclude=Provenance:target&category=laboratory&patient=[patient_unique]

4. Usage Terms

a. Fees and Limitations

Usage of our standard API as listed above does not contain any additional fees. Data owner (such as medical office) must retain an active Advantage Partnership Support Service agreement.

Costs and Limitations are publicly available at: Disclosure-Analysis-Costs-and-Limitations

b. Restrictions and Obligations

Any user shall be restricted to the data and scopes made available to that user. That usage shall be in the context of the information provided in registration.

Compulink or the data owner (such as the medical organization) reserve the right to remove or restrict access to users. Other reasons for removal include, but are not limited to:

  1. Sublicense or share any protected connectivity content from the API for use by a non-registered application.
  2. Perform an action with the intent of introducing the interface to any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature.
  3. Defame, abuse, harass, stalk, or threaten others.
  4. Interfere with or disrupt the APIs or the servers or networks providing the APIs.
  5. Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable law.
  6. Collecting data outside the agreed upon context of usage.

You may not use the APIs and may not accept the Terms if you are a person barred from using or receiving the APIs under the applicable laws of the United States or other countries including the country in which you are resident or from which you use the APIs.

c. Contact

For any developer related question or clarifications regarding Compulink FHIR API please contact:

Compulink Customer Care
Phone: 805.716.8677
Fax: 805.497.4983
Email: [email protected]