Each Immunization resource identifies an immunization performed on a patient. A bundle of these resources together can be used to represent the immunization history of the patient. Example API requests for immunization records are shown below: Retrieve all immunizations related to a patient.

The API response will consist of a Bundle of Immunization resources. The following data elements will be included if available:

• Status [status]
• Administered Date [date]
• Vaccine Code (CVX) [vaccineCode.coding]
• Given Indicator [wasNotGiven]
• Reported Indicator [reported]

Each Vital signs resource identifies as Pulse Oximetry (Vital Signs) on a patient. A bundle of these resources together can be used to represent the Pulse Oximetry (Vital Signs) history of the patient. Example API requests for Pulse Oximetry (Vital Signs) records are shown below: Retrieve all Pulse Oximetry (Vital Signs) related to a patient.

Find through code+ patient ,patient + categoty , patient +category+date

Each Observation Body Height (Vital Signs) resource identifies an Observation Body Height (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Observation Body Height (Vital Signs) history of the patient. Example API requests for Observation Body Height (Vital Signs) records are shown below: Retrieve all Observation Body Height (Vital Signs) related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

patient + code,patient + category + date,patient + category

Each Diagnostic Report For Report And Note Exchange resource identifies an Diagnostic Report For Report And Note Exchange performed on a patient. A bundle of these resources together can be used to represent the Diagnostic Report For Report And Note Exchange history of the patient. Example API requests for Diagnostic Report For Report And Note Exchange records are shown below: Retrieve all Diagnostic Report For Report And Note Exchange related to a patient.

The API response for each of these data categories will consist of a Bundle of DiagnosticReport resources.

• Patient [subject.reference]
• Status [status]
• Test Code (LOINC) [code.coding]
• Measured Time [effectiveDateTime]

The following Lab Result data elements will be included if available:

• Patient [contained.subject.reference]
• Status [contained.status]
• Result Code (LOINC) [contained.code.coding]
• Result Value [contained.valueString]
• Reference Range [contained.referenceRange.text]
• Result Time [contained.effectiveDateTime]

patient+category

Each Encounter resource identifies an Encounter performed on a patient. A bundle of these resources together can be used to represent the Encounter history of the patient. Example API requests for Encounter records are shown below: Retrieve all Encounter related to a patient.

Encounter will first perform each required search associated with this resource. Perform searches with the following parameters:

patient,_id,patient+category

Each Goal resource identifies an Goal performed on a patient. A bundle of these resources together can be used to represent the Goal history of the patient. Example API requests for Goal records are shown below: Retrieve all Goal related to a patient.

The API response will consist of a Bundle of Goal resources. The following data elements will be included if available:

• Patient [subject.reference]
• Status [status]
• Text [description]

Patient

Each Care team resource identifies an Care team performed on a patient. A bundle of these resources together can be used to represent the Care team history of the patient. Example API requests for Care team records are shown below: Retrieve all Care team related to a patient.

The API response will consist of a Bundle of Care team resources. The following data elements will be included if available:

• Patient [subject]
• Status [status]
• Participant [participant]
• ParticipantRole [participant.role]
• ParticipantMember [participant.member]

This API is able to satisfy requests for data related to the USCDI Care Team Member(s) Class.

Patient+status

Each Observation Body Temperature (Vital Signs) resource identifies an Observation Body Temperature performed on a patient. A bundle of these resources together can be used to represent the Observation Body Temperature history of the patient. Example API requests for Observation Body Temperature records are shown below: Retrieve all Observation Body Temperature related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

patient + code,patient + category + date,patient + category

Each Diagnostic Report For Laboratory Results Reporting resource identifies an Diagnostic Report For Laboratory Results Reporting performed on a patient. A bundle of these resources together can be used to represent the Diagnostic Report For Laboratory Results Reporting history of the patient. Example API requests for Diagnostic Report For Laboratory Results Reporting records are shown below: Retrieve all Diagnostic Report For Laboratory Results Reporting related to a patient.

The API response for each of these data categories will consist of a Bundle of DiagnosticReport resources.

• Patient [subject.reference]
• Status [status]
• Test Code (LOINC) [code.coding]
• Measured Time [effectiveDateTime]

The following Lab Result data elements will be included if available:

• Patient [contained.subject.reference]
• Status [contained.status]
• Result Code (LOINC) [contained.code.coding]
• Result Value [contained.valueString]
• Reference Range [contained.referenceRange.text]
• Result Time [contained.effectiveDateTime]

patient + category, patient + category + date,patient + code,

Each Procedure resource identifies an Procedure performed on a patient. A bundle of these resources together can be used to represent the Procedure history of the patient. Example API requests for Procedure records are shown below: Retrieve all Procedure related to a patient.

The API response will consist of a Bundle of Procedure resources. The following data elements will be included if available:

• Patient [subject.reference]
• Status [status]
• Code (SNOMED-CT) [code.coding]
• Performed Date [performedDateTime]

Patient, Patient+date

A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.

Resource type inclusion in this list does not guarantee that such a resource exists in the server, only that it could accept them.

Each Condition Condition resource identifies an Condition performed on a patient. A bundle of these resources together can be used to represent the Condition history of the patient. Example API requests for Condition records are shown below: Retrieve all Condition related to a patient.

The API response will consist of a Bundle of Condition resources. The following Problem data elements will be included if available:

• Patient [patient.reference]
• Status [clinicalStatus]
• Verification Status [verificationStatus]
• Verification Status [verificationStatus]
• Category (problem) [category.coding]
• Code (SNOMED-CT) [code.coding]

The following Health Concern data elements will be included if available:

• Patient [patient.reference]
• Status [clinicalStatus]
• Verification Status [verificationStatus]
• Category (health-concern) [category.coding] Text [code.text]

Get conditions associated with a specific patient

Each Implantable Device / Medical Device resource identifies an Implantable Device / Medical Device performed on a patient. A bundle of these resources together can be used to represent the Implantable Device / Medical Device history of the patient. Example API requests for Implantable Device / Medical Device records are shown below: Retrieve all Implantable Device / Medical Device related to a patient.

The API response will consist of a Bundle of Implantable Device / Medical Device resources. The following data elements will be included if available:

• Patient [patient.reference]
• UDI [udiCarrier]
• Type (SNOMED) [type]

This API is able to satisfy requests for data related to the USCDI Unique Device Identifier(s) for a Patient’s Implantable Device(s) Class.

Each Observation Body Weight (Vital Signs) (Vital Signs) resource identifies an Observation Body Weight (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Observation Body Weight (Vital Signs) history of the patient. Example API requests for Observation Body Weight (Vital Signs) records are shown below: Retrieve all Observation Body Weight (Vital Signs) related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

Code+Patient , patient + category + date ,patient + category

Each Document Reference resource identifies an Document Reference performed on a patient. A bundle of these resources together can be used to represent the Document Reference history of the patient. Example API requests for Document Reference records are shown below: Retrieve all Document Reference related to a patient.

Patient, _id ,Patient +type,Patient + category+date,Patient + category

Each Pediatric BMI For Age Observation (Vital Signs) resource identifies an Pediatric BMI For Age Observation (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Pediatric BMI For Age Observation (Vital Signs) history of the patient. Example API requests for Pediatric BMI For Age Observation (Vital Signs) records are shown below: Retrieve all Pediatric BMI For Age Observation (Vital Signs)related to a patient.

Patient + code,Patient +category+date,Patient + category

Each Care Plan resource identifies an Care plan performed on a patient. A bundle of these resources together can be used to represent the Care plan history of the patient. Example API requests for Care plan records are shown below: Retrieve all Care plan related to a patient.

The API response will consist of a Bundle of Care Plan resources. The following data elements will be included if available:

• Patient [subject]
• Text [text]
• Intent [intent]
• Category [category]

Find care plan from category

Each Medication request resource identifies an Medication request performed on a patient. A bundle of these resources together can be used to represent the Medication request history of the patient. Example API requests for Medication request records are shown below: Retrieve all Medication request related to a patient.

The MedicationRequest resource covers medication orders for a patient. This includes both inpatient and outpatient orders related to medications. This is not intended for diet prescriptions or for non-medication items (such as sunglasses, supplies, etc.)

The API response will consist of a Bundle of Medication request resources. The following data elements will be included if available:

• Date [dateWritten]
• Status [status]
• Prescriber [prescriber]
• Medication (RXNORM) [medicationCodeableConcept.coding]

Patient+intent+status

Each Observation Body Rate (Vital Signs) resource identifies an Observation Respiratory Rate (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Observation Respiratory Rate (Vital Signs) history of the patient. Example API requests for Observation Respiratory Rate (Vital Signs) records are shown below: Retrieve all Observation Respiratory Rate (Vital Signs) related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

Code+Patient,patient + category + date,patient + category

Each Laboratory Result Observation (Laboratory) resource identifies an Laboratory Result Observation (Laboratory) performed on a patient. A bundle of these resources together can be used to represent the Laboratory Result Observation (Laboratory) history of the patient. Example API requests for Laboratory Result Observation (Laboratory) records are shown below: Retrieve all Laboratory Result Observation (Laboratory) related to a patient.

Patient +category, Patient +category +date ,Patient +code

Each Pediatric Weight For Height Observation (Vital Signs) resource identifies an Pediatric Weight For Height Observation (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Pediatric Weight For Height Observation (Vital Signs) history of the patient. Example API requests for Pediatric Weight For Height Observation (Vital Signs) records are shown below: Retrieve all Pediatric Weight For Height Observation (Vital Signs) related to a patient.

patient + category, patient + category + date,patient + code,

Each Allergy intolerance resource identifies an Allergy intolerance performed on a patient. A bundle of these resources together can be used to represent the Allergy intolerance history of the patient. Example API requests for Allergy intolerance records are shown below: Retrieve all Allergy intolerance related to a patient.

The AllergyIntolerance resource provides a bundle of allergies for a given patient resource. An example of retrieving AllergyIntolerance records is included below.

The API response will consist of a Bundle of Allergy intolerance resources. The following data elements will be included if available:

• Patient [patient.reference]
• Status [status]
• Substance Code (RXNORM) [substance.coding]
• Reaction Code (SNOMED-CT) [reaction.manifestation.coding]
• Severity [reaction.severity]

Get allergy intolerances associated with a specific patient

The server support Organization sequence verifies that the system is able to provide Organization queries. These queries contain resources conforming to the US Core Organization Profile as specified in the US Core v3.1.1 Implementation Guide.

Each Observation Heart Rate (Vital Signs) resource identifies an Observation Heart Rate (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Observation Heart Rate (Vital Signs) history of the patient. Example API requests for Observation Heart Rate (Vital Signs) records are shown below: Retrieve all Observation Heart Rate (Vital Signs) related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

Code+Patient, patient + category + date,patient + category

Each Pediatric Head Occipital-frontal Circumference Percentile (Vital Signs) resource identifies an Pediatric Head Occipital-frontal Circumference Percentile (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Pediatric Head Occipital-frontal Circumference Percentile (Vital Signs) history of the patient. Example API requests for Pediatric Head Occipital-frontal Circumference Percentile (Vital Signs) records are shown below: Retrieve all Pediatric Head Occipital-frontal Circumference Percentile (Vital Signs) related to a patient.

Patient + code,Patient + category+date ,Patient + category

Each Patient resource identifies an Patient performed on a patient. A bundle of these resources together can be used to represent the Patient history of the patient. Example API requests for Patient records are shown below: Retrieve all Patient related to a patient.

The Patient resource type provides demographic and contact details about the patient in One Medical’s EHR. This resource covers the “who” about the patient, including name, date of birth, birth sex, gender, and address. Example requests for patient data are shown below:

The API response will consist of a Bundle of Patient resources. The following data elements will be included if available:

• Identifiers (Local, SSN) [identifier]
• Name [name]
• Gender [gender]
• Date of Birth [birthDate]
• Phone [telecom]
• Email [telecom]
• Address [address]
• Marital Status [maritalStatus]
• Race [extension]
• Ethnicity [extension]
• Preferred Language [extension]

Get patient by resource ID

Name (first and last name; birthdate YYYY-MM-DD and gender may be added). Name searches return a summary of each patient (name, birth date, gender, MRN, phone, email); read the patient by resource ID for the full record.

MRN

Each Smoking Status Observation (Smoking Status) resource identifies an Smoking Status Observation (Smoking Status) performed on a patient. A bundle of these resources together can be used to represent the Smoking Status Observation (Smoking Status) history of the patient. Example API requests for Smoking Status Observation (Smoking Status) records are shown below: Retrieve all Smoking Status Observation (Smoking Status) related to a patient.

patient+code

Each Observation Blood Pressure (Vital Signs) resource identifies an Observation Blood Pressure (Vital Signs) performed on a patient. A bundle of these resources together can be used to represent the Observation Blood Pressure (Vital Signs) history of the patient. Example API requests for Observation Blood Pressure (Vital Signs) records are shown below: Retrieve all Observation Blood Pressure (Vital Signs) related to a patient.

The Observation Resource is used to provide responses to requests for Lab Results , Smoking Status , and Vital Signs. The API response for each of these data categories will consist of a Bundle of Observationresources.

Lab Results

• Patient [subject.reference]
• Status [status]
• Result Code (LOINC) [code.coding]
• Result Value [valueString]
• Reference Range [referenceRange.text]
• Result Time [effectiveDateTime]

Smoking Status

• Patient [subject.reference]
• Status [status]
• Recorded Date [issued]
• Value code [valueCodeableConcept.coding]

Code+Patient, patient + category + date,patient + category

Server support that system is able to provide correct responses for Provenance queries. These queries contain resources conforming to the US Core Provenance Profile as specified in the US Core v3.1.1 Implementation Guide.

The Provenance resource is derived from the US Core Provenance Profile.

The API response will consist of a Provenance resource.

This API is able to satisfy requests for data related to the USCDI Provenance Class.

Provenance ID

Server Support Clinical Notes Sequence tests DiagnosticReport and DocumentReference resources associated with the provided patient. The resources returned will be checked for consistency against the US Core Clinical Notes Guidance

Document Reference & Diagnostic Report

Patient

Each Appointment resource represents a scheduled visit for a patient. A search requires a patient or a date. Dates use day precision with the prefixes eq, ge, gt, le and lt; a range may span at most 2 years, and when no date is given the search covers 90 days before and after today.

The API response will consist of a Bundle of Appointment resources. The following data elements will be included if available:

• Status [status]
• Start / End [start, end]
• Created [created]
• Chief complaint [description]
• Comments [comment]
• Patient instructions [patientInstruction]
• Cancellation reason [cancelationReason]
• Patient and Location [participant]

Patient

Patient and date range

Location

Get appointment by resource ID

Each Practitioner resource identifies a provider of the practice. The practitioner references returned in clinical resources (for example MedicationRequest.requester or Condition.asserter) can be read by ID, and the fhirUser claim of a provider sign-in points to the same resource.

The API response will consist of a Bundle of Practitioner resources. The following data elements will be included if available:

• NPI [identifier]
• Name [name]
• Phone [telecom]

Get practitioner by resource ID

NPI

Each PractitionerRole resource describes the role of a practice provider, including the provider's specialty.

The API response will consist of a Bundle of PractitionerRole resources. The following data elements will be included if available:

• Practitioner [practitioner]
• Specialty [specialty]
• Phone [telecom]

Practitioner

Get practitioner role by resource ID