The First Medical Patient Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for Fuse members to access their data using Third-party client applications supporting those standards. The Patient Access API implements the FHIR Patient resource conforming to the CARIN Coverage Profile specified in the CARIN Blue Button Implementation Guide (v0.1.0). The Patient Access API follows the User token security model. The Patient resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Patient.

The First Medical Patient Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access their data using Third-party client applications supporting those standards. The Patient Access API implements the FHIR Patient resource conforming to the CARIN Coverage Profile specified in the CARIN Blue Button Implementation Guide (v0.1.0). The Patient Access API follows the User token security model. The Patient resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Patient.

The First Medical ExplanationOfBenefit Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access their data using Third-party client applications supporting those standards. The API supports the FHIR ExplanationOfBenefit resource and conforms to the CARIN ExplanationOfBenefit Profile specified in the CARIN Blue Button Implementation Guide (v0.1.0). This API currently follows User token security. The ExplanationOfBenefit resource supports: Launch Coverage by calling the [FHIR Base]/Explanation Of Benefit.

The First Medical Organization Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access their data using Third-party client applications supporting those standards. The Organization Access API implements the FHIR Organization resource conforming to the CARIN Organization Profile specified in the CARIN Blue Button Implementation Guide (v0.1.0). The Organization Access API follows the User token security model. The Organization resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Organization.

The First Medical Practitioner Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access their data using Third-party client applications supporting those standards. The Practitioner Access API implements the FHIR Practitioner resource conforming to the US Core Practitioner Profile standards specified in the US Core Implementation Guide (v3.1.1: STU 3). The Practitioner Access API follows the User token security model. The Practitioner resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Practitioner.

The First Medical Practitioner Access API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access their data using Third-party client applications supporting those standards. The Practitioner Access API implements the FHIR Practitioner resource conforming to the US Core Practitioner Profile standards specified in the US Core Implementation Guide (v3.1.1: STU 3). The Practitioner Access API follows the User token security model. The Practitioner resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Practitioner.

The First Medical AllergyIntolerance API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the AllergyIntolerance resource for the minimal set of data to query and retrieve allergy information. The AllergyIntolerance API implements the FHIR AllergyIntolerance resource conforming to the US Core AllergyIntolerance Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The AllergyIntolerance API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ AllergyIntolerance.

The First Medical CarePlan API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the CarePlan resource for the minimal set of data to query and retrieve a patients Care Plan. The CarePlan API implements the FHIR CarePlan resource conforming to the US Core CarePlan Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The CarePlan API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ CarePlan.

The First Medical DiagnosticReport API is an enterprise API that implements the HL7 FHIR standard and provides set of information that is typically provided by a diagnostic service when investigations are complete. The information includes a mix of atomic results, text reports, images, and codes. The DiagnosticReport API implements the FHIR DiagnosticReport resource conforming to the US Core DiagnosticReport Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The DiagnosticReport API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ DiagnosticReport.

The First Medical Encounter API is an enterprise API that implements the HL7 FHIR standard and provides interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. The Encounter API implements the FHIR Encounter resource conforming to the US Core Encounter Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Encounter API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Encounter.

The First Medical Goal API is an enterprise API that implements the HL7 FHIR standard and provides the intended objective(s) for a patient, group or organization care, for example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc. The Goal API implements the FHIR Goal resource conforming to the US Core Goal Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Goal API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Goal.

The First Medical Location API is an enterprise API that implements the HL7 FHIR standard and provides details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated. The Location API implements the FHIR Location resource conforming to the US Core Location Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Location API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Location.

The First Medical Medication API is an enterprise API that implements the HL7 FHIR standard and provides the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use. The Medication API implements the FHIR Medication resource conforming to the US Core Medication Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Medication API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Medication.

The First Medical MedicationRequest API is an enterprise API that implements the HL7 FHIR standard and provides order or request for both supply of the medication and the instructions for administration of the medication to a patient. The MedicationRequest API implements the FHIR MedicationRequest resource conforming to the US Core MedicationRequest Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The MedicationRequest API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ MedicationRequest.

The First Medical Observation API is an enterprise API that implements the HL7 FHIR standard and provides measurements and simple assertions made about a patient, device or other subject. The Observation API implements the FHIR Observation resource conforming to the US Core Observation Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Observation API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Observation.

The First Medical Procedure API is an enterprise API that implements the HL7 FHIR standard and provides an action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counselling, or hypnotherapy. The Procedure API implements the FHIR Procedure resource conforming to the US Core Procedure Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Procedure API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Procedure.

The First Medical USCDI Organization API is an enterprise API that implements the HL7 FHIR standard and provides the ability for Endlink members to access their data using Third-party client applications supporting those standards. The USCDI Organization API implements the FHIR Organization resource conforming to the US Core Organization Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The USCDI Organization API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ USCDI Organization.

The First Medical Appointment API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the Appointment resource for the minimal set of data to query and retrieve Appointment information. The Appointment API implements the FHIR Appointment resource conforming to the US Core Appointment Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Appointment API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Appointment.

The First Medical CareTeam API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the CareTeam resource for the minimal set of data to query and retrieve a patients CareTeam data . The CareTeam API implements the FHIR CareTeam resource conforming to the US Core CareTeam Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The CareTeam API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ CareTeam.

The First Medical Immunization API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the Immunization resource for the minimal set of data to query and retrieve Immunization information a patient has taken. The Immunization API implements the FHIR Immunization resource conforming to the US Core Immunization Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Immunization API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Immunization.

The First Medical Condition API is an enterprise API that implements the HL7 FHIR standard and provides constraints and extensions on the Condition resource for the minimal set of data to query and retrieve information about Patient's Condition. The Condition API implements the FHIR Condition resource conforming to the US Core Condition Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The Condition API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ Condition.

The First Medical MedicationStatement API is an enterprise API that implements the HL7 FHIR standard and provides a record of a medication that is being consumed by a patient and a MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The MedicationStatement API implements the FHIR MedicationStatement resource conforming to the US Core MedicationStatement Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The MedicationStatement API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ MedicationStatement.

The First Medical RelatedPerson API is an enterprise API that implements the HL7 FHIR standard and provides a record of the Person related to the Patient and this profile sets minimum expectations for the RelatedPerson resource to record, search, and fetch basic administrative information about persons with a legal or familial relationship to a patient. The RelatedPerson API implements the FHIR RelatedPerson resource conforming to the US Core RelatedPerson Profile standards specified in the US Core Implementation Guide (v4.0.1: R4 - Mixed Normative and STU). The RelatedPerson API follows the User token security model. The Patient resource supports the below operations: Read the current state of the resource using the Logical (unique) ID [FHIR Base]/ RelatedPerson.

The First Medical Claim Access API is an enterprise API that implements the HL7 FHIR standard and provides access to providers and payers, insurers, to exchange the financial information, and supporting clinical information, regarding the provision of health care services with payers and for reporting to regulatory bodies and firms which provide data analytics. The primary uses of this resource is to support eClaims, the exchange of information relating to the proposed or actual provision of healthcare-related goods and services for patients to their benefit payers, insurers and national health programs, for treatment payment planning and reimbursement.. The Claim Access API implements the FHIR Claim resource conforming to the US Core Claim Profile standards specified in the US Core Implementation Guide (v3.1.1: STU 3). The Patient resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/Claim.

The First Medical FamilyHistory API is an enterprise API that implements the HL7 FHIR standard and provides the ability for First Medical members to access the records of significant health conditions for a particular individual related to the subject. This information can be known to different levels of accuracy. Sometimes the exact condition ('asthma') is known, and sometimes it is less precise ('some sort of cancer'). Equally, sometimes the person can be identified ('my aunt Agatha') and sometimes all that is known is that the person was an uncle. This resource represents a simple structure used to capture an 'elementary' family history for a particular family member. However, it can also be the basis for capturing a more rigorous history useful for genetic and other analysis. TheFamilyHistory API implements the FHIR FamilyHistory resource conforming to the US Core Coverage Profile standards specified in the US Core Implementation Guide (v3.1.1: STU 3). The FamilyHistory API follows the User token security model. The Patient resource supports the following operations: 1. Read the current state of the resource using the Logical (unique) ID [FHIR Base]/FamilyHistory.

ListResource