FHIR

at founda, we've made a strategic choice by embracing fhir (version r4) as our cornerstone for healthcare interoperability, and that's not just because it's the industry standard it's because we see the profound benefits it brings to the entire healthcare landscape why we choose fhir hl7's fast healthcare interoperability resources fhir 🔥 is the language of global healthcare nearly all healthcare systems worldwide operate (to some degree) using fhir this means seamless communication with healthcare organizations across the globe a critical element in today's interconnected world furthermore, fhir's web based api suite offers a game changing advantage it acts as a bridge, bringing together a multitude of digital health solutions, regardless of whether they have a legion of developers at their disposal this means no more building one off connections every time you need to interact with the legacy systems that dominate the healthcare market fhir empowers innovation, scalability, and a brighter future for healthcare integration but what is fhir? fhir a standard for digital data exchange in healthcare the base fhir specification describes a set of base resources, frameworks and apis that are used in many different contexts in healthcare below we explain the basics of fhir that you'll need to understand everything in our documentation portal however, if you're looking for other means to understand fhir in a simplified manner, you might find the following websites helpful hl7's fhir overview the official hl7 fhir website offers a "fhir overview" section that provides a high level introduction to fhir, its key concepts and why it's important in healthcare visit hl7 fhir overview onc fhir fact sheets the office of the national coordinator for health information technology offers fhir fact sheets that were created together with hl7 to educate about fhir visit fhir fact sheets youtube video tutorials search for fhir introductory video tutorials on youtube there are several video creators who provide step by step explanations on fhir concepts and use cases fhir is a technical standard, but these resources aim to simplify it for a broader audience starting with these beginner friendly materials can be a great way to grasp the fundamentals of fhir before diving into more technical documentation so let's dive into some of the basics the core of the fhir standard is its fhir resources, which refer to standardized data representations of healthcare concepts or entities resources are the building blocks of fhir and they provide a structured way to exchange and share healthcare information in a standardized format each resource corresponds to a specific healthcare concept or piece of data, and they are used to represent various aspects of healthcare for example, some of the most common resources patient resource represents a patient's demographic and clinical information, including their name, gender, date of birth, and other relevant details practitioner resource represents healthcare providers, such as doctors and nurses, and includes information about their credentials and contact details medication resource contains information about medications, including their names, dosages, and administration instructions observation resource represents clinical observations or measurements, such as blood pressure readings, lab results, or vital signs condition resource represents a patient's medical conditions or diagnoses, including information about the condition's status and onset appointment resource contains information about appointments, including dates, times and participants (e g , patient and provider) take a look at the resource list on hl7's fhir website for a complete overview of all available fhir resources each resource comprises metadata, a narrative, extensions, and a body that encapsulates the elements and data types of these attributes the resource's identity consists of an endpoint, the resource type and a logical id of the resource within fhir it's possible to group resources together into what's known as a fhir bundle a resource in itself this bundle serves as a container for multiple resources, making it convenient to transmit or manage related healthcare data as a cohesive unit let's take the "patient" resource as an example to explain it's structure in fhir patient resource structure resource type each fhir resource has a specific type, and for the patient resource, it's represented as "patient " this type is used to identify the resource when it's exchanged or queried id and meta every resource typically has an "id" attribute to uniquely identify it within a system, and "meta" may contain metadata about the resource, including version history text the "text" element contains a human readable representation of the resource, which can be useful for displaying information to users identifier this section includes identifiers associated with the patient, such as a driver's license number, national identification number, or healthcare provider's patient id active indicates whether the patient record is currently active or not name contains the patient's name, which may include given names, family names, prefixes, and suffixes telecom includes contact information like phone numbers and email addresses gender represents the patient's gender as male, female, other, or unknown birthdate specifies the patient's date of birth address contains the patient's address, including postal code, city, state, and country maritalstatus describes the patient's marital status, such as single, married, divorced, etc multiple birth indicates whether the patient is part of a multiple birth (e g , twins) deceased specifies whether the patient is deceased and includes the date of death if applicable communication lists the patient's preferred language and other languages they can communicate in contact contains information about individuals or organizations that can be contacted in relation to the patient managing organization identifies the organization responsible for managing the patient's healthcare link allows linking to other resources, such as a related patient or another record these are some of the key elements you might find within a patient resource in fhir each element is defined with specific data types and cardinality, ensuring that data is structured consistently and can be easily exchanged and understood by different healthcare systems and applications fhir resources are designed to be both human readable and machine readable, making them highly interoperable in the healthcare domain if you are interested in reading more about why founda is standards based and what communication standards are used, take look at these pages