# OnyeOne Documentation ## Docs - [Overview](https://onyeone.apidog.io/overview-768240m0.md): - [OnyeOne Use Cases](https://onyeone.apidog.io/onyeone-use-cases-768235m0.md): - [Authentication](https://onyeone.apidog.io/authentication-768228m0.md): - Guides [OnyeOne Request Flow](https://onyeone.apidog.io/onyeone-request-flow-778439m0.md): - [Core EHR/EMR FHIR R4 APIs](https://onyeone.apidog.io/core-ehr-apis.md): Overview ## API Docs - Core EHR/EMR FHIR R4 APIs > Administration > Patients [Create Patient Resource](https://onyeone.apidog.io/create-patient-resource-12406793e0.md): - Core EHR/EMR FHIR R4 APIs > Administration > Patients [Update Patient Resource](https://onyeone.apidog.io/update-patient-resource-12606783e0.md): This endpoint updates an existing *Patient* resource. Note that this operation replaces the section in the resource as specified in the body of the request. - Core EHR/EMR FHIR R4 APIs > Administration > Practitioners [Create Practitioner Resource](https://onyeone.apidog.io/create-practitioner-resource-12434941e0.md): This endpoint allows for the creation of a Practitioner resource in FHIR R4 format. It enables the representation of individual healthcare providers, including their identifiers, qualifications, contact details, and roles within a healthcare organization. - Core EHR/EMR FHIR R4 APIs > Administration > Practitioners [Update Practitioner Resource](https://onyeone.apidog.io/update-practitioner-resource-12589635e0.md): This endpoint updates an existing *Practitioner* resource. Note that this operation replaces the section in the resource as specified in the body of the request. - Core EHR/EMR FHIR R4 APIs > Administration > Practitioners [Create Practitioner Role](https://onyeone.apidog.io/create-practitioner-role-12484327e0.md): This API creates a PractitionerRole resource, which defines the role of a practitioner within an organization. It links to a Practitioner resource (representing the individual), an Organization resource (the organization they work for), and includes details such as their role, specialty, active status, availability and the period during which the role is valid. - Core EHR/EMR FHIR R4 APIs > Administration > Practitioners [Update PractitionerRole Resource](https://onyeone.apidog.io/update-practitionerrole-resource-12531626e0.md): This endpoint updates an existing *PractitionerRole* resource. Note that this operation replaces the section in the resource as specified in the body of the request. - Core EHR/EMR FHIR R4 APIs > Administration > Locations [Create a Location Resource](https://onyeone.apidog.io/create-a-location-resource-12532545e0.md): This API creates a Location resource, which represents a physical place where healthcare services are provided. It can include details such as the name, address, type of location, managing organization, and its operational status. - Core EHR/EMR FHIR R4 APIs > Administration > Locations [Update Location Resource](https://onyeone.apidog.io/update-location-resource-12542416e0.md): This endpoint updates an existing *Location* resource. Note that this operation replaces the section in the resource as specified in the body of the request. - Core EHR/EMR FHIR R4 APIs > Administration > Health Service [Create Health Service Resource](https://onyeone.apidog.io/create-health-service-resource-12630006e0.md): The *HealthcareService* resource is used to describe a single healthcare service or category of services that are provided by an organization at a location. - Core EHR/EMR FHIR R4 APIs > Administration > Health Service [Update Health Service Resource](https://onyeone.apidog.io/update-health-service-resource-12633043e0.md): This endpoint updates an existing *HealthcareService* resource. Note that this operation replaces the section in the resource as specified in the body of the request. - Core EHR/EMR FHIR R4 APIs > Administration > Encounters [Create Encounter Resource](https://onyeone.apidog.io/create-encounter-resource-12634966e0.md): An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. - Core EHR/EMR FHIR R4 APIs > Administration > Encounters [Update Encounter Resource](https://onyeone.apidog.io/update-encounter-resource-12710164e0.md): An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. - Core EHR/EMR FHIR R4 APIs > Administration > Appointments [Create Appointment Resource](https://onyeone.apidog.io/create-appointment-resource-12718891e0.md): A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). - Core EHR/EMR FHIR R4 APIs > Administration > Appointments [Update Appointment Resource](https://onyeone.apidog.io/update-appointment-resource-12829121e0.md): A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s). - Core EHR/EMR FHIR R4 APIs > Diagnostics > Observation [Create Observation Resource](https://onyeone.apidog.io/create-observation-resource-12829511e0.md): Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics. Most observations are simple name/value pair assertions with some metadata, but some observations group other observations together logically, or even are multi-component observations. Note that the DiagnosticReport resource provides a clinical or workflow context for a set of observations and the Observation resource is referenced by DiagnosticReport to represent laboratory, imaging, and other clinical and diagnostic data to form a complete report. - Health Data Transformation [Transfrom HL7v2 to FHIR R4](https://onyeone.apidog.io/transfrom-hl7v2-to-fhir-r4-12241417e0.md): This API converts HL7v2 messages into FHIR R4 resources, allowing seamless mapping and transformation of clinical data. It supports essential mappings, validation, and structuring to comply with FHIR R4 standards, enabling accurate and consistent data representation across healthcare applications. - Health Data Transformation [Transform CCDA to FHIR R4](https://onyeone.apidog.io/transform-ccda-to-fhir-r4-12241474e0.md): This API converts CCDA documents into FHIR R4 resources, enabling the structured mapping and transformation of clinical data. It supports essential mappings, validation, and formatting to ensure compliance with FHIR R4 standards for accurate and consistent data representation in healthcare systems. - Health Data Transformation [Transform HL7v2 to FHIR R4 and Store in Backend Database](https://onyeone.apidog.io/transform-hl7v2-to-fhir-r4-and-store-in-backend-database-12242890e0.md): This API transforms HL7v2 messages into FHIR R4 resources and stores the resulting data in the backend database. It performs structured mapping, validation, and transformation of clinical data to comply with FHIR R4 standards, ensuring accurate representation and persistent storage for future use in healthcare applications. - Health Data Transformation [Track API Request](https://onyeone.apidog.io/track-api-request-12271507e0.md): - Health Interoperabilty System [Create a Subscription](https://onyeone.apidog.io/create-a-subscription-12243225e0.md): This API allows providers to subscribe to health resources across multiple healthcare systems and receive real-time notifications on any changes or events related to those resources or groups of resources. By subscribing, providers stay informed of updates, ensuring timely access to critical health data and facilitating seamless interoperability between disparate healthcare systems. - [Get Resource.](https://onyeone.apidog.io/get-resource-12237337e0.md): This API retrieves FHIR resources created by the provider based on specified query parameters, ensuring access to relevant clinical data in the FHIR R4 format.