Healthcare Interoperability: Exploring the Potential of the FHIR VerificationResult Resource

The Fast Healthcare Interoperability Resources (FHIR) VerificationResult resource is a vital component within the FHIR framework designed to facilitate the seamless exchange and interoperability of healthcare information. FHIR itself stands as a modern standard for health data exchange, promoting the efficient sharing of clinical and administrative information among diverse healthcare systems and entities.


The FHIR VerificationResult resource serves as a fundamental tool aimed at ensuring the accuracy, validity, and trustworthiness of data shared between different healthcare stakeholders. In the context of this resource, ‘verification’ pertains to the process of confirming the correctness of a particular piece of information, such as a patient’s medication, an allergy, or other clinical details.

The primary objective of the VerificationResult resource is to provide a standardized format for representing the outcomes of verification processes conducted on various aspects of healthcare data. This may encompass a range of verifications, such as confirming the authenticity of a prescription, verifying the accuracy of a patient’s medical history, or ensuring the proper authorization for sharing sensitive health information.

This resource contains essential metadata and content, including the target data being verified, the specific verification status (such as successful, failed, or unknown), and details about the verifier or the organization responsible for the verification process. Moreover, the resource can encompass additional contextual information, such as timestamps indicating when the verification occurred and the context in which it was conducted.

In practical terms, the FHIR VerificationResult resource serves as a standardized means of communicating verification outcomes, streamlining communication and collaboration across different healthcare systems. It enables various entities, such as electronic health record (EHR) systems, pharmacies, and clinical decision support applications, to assess the reliability and credibility of shared health information, ultimately enhancing patient safety and care quality.

FHIR VerificationResult Resource
FHIR VerificationResult Resource

In essence, the FHIR VerificationResult resource plays a pivotal role in the FHIR ecosystem by providing a structured and standardized format for conveying verification outcomes related to healthcare data. It enhances interoperability by ensuring that different stakeholders can reliably assess the accuracy and trustworthiness of shared information, thereby contributing to more effective and coordinated healthcare delivery.

Structure of FHIR VerificationResult Resource

Here is the structure of the FHIR VerificationResult resource in JSON format along with an explanation of each element. Other format like XML and Turtle is also present, but for simplicity here we will take the example of JSON format. The complete structure details can be found here.

  "resourceType": "VerificationResult",
  "id": "example-verification",
  "status": "completed",
  "target": {
    "reference": "Patient/example",
    "display": "Patient: John Doe"
  "targetLocation": "Patient.medication",
  "verificationDate": "2023-08-15T10:30:00Z",
  "validationType": {
    "coding": [
        "system": "",
        "code": "primary",
        "display": "Primary Validation"
  "validationProcess": [
      "identifier": {
        "system": "",
        "value": "medication-validation"
      "comment": "Validation process for patient medication data"
  "frequency": {
    "timing": {
      "repeat": {
        "frequency": 1,
        "periodUnit": "day"
  "lastPerformed": "2023-08-14T14:00:00Z",
  "nextScheduled": "2023-08-15T14:00:00Z",
  "failureAction": {
    "coding": [
        "system": "",
        "code": "fatal",
        "display": "Fatal"
  "primarySource": [
      "who": {
        "reference": "Practitioner/example",
        "display": "Dr. Jane Smith"
      "communicationMethod": [
          "coding": [
              "system": "",
              "code": "email",
              "display": "Email"
      "validationStatus": {
        "coding": [
            "system": "",
            "code": "successful",
            "display": "Successful"
  "attestation": [
      "mode": "legal",
      "time": "2023-08-15T10:30:00Z",
      "party": {
        "reference": "Organization/example",
        "display": "Community Hospital"

Explanation of the JSON elements:

  • resourceType: The type of FHIR resource, which is “VerificationResult”.
  • id: A unique identifier for the VerificationResult resource instance.
  • status: The status of the verification, which can be “completed”, “in-progress”, etc.
  • target: The reference to the resource being verified, in this case, a patient named John Doe.
  • targetLocation: The specific location within the target resource where the verification is applied, such as “Patient.medication”.
  • verificationDate: The date and time when the verification took place.
  • validationType: The type of validation being performed, with a coding system and display value.
  • validationProcess: Details about the validation process, including an identifier and a comment.
  • frequency: The frequency of verification, expressed as a timing element.
  • lastPerformed: The date and time of the last verification.
  • nextScheduled: The date and time when the next verification is scheduled.
  • failureAction: The action to be taken in case of verification failure, with a coding system and display value.
  • primarySource: Information about the primary sources involved in the verification process, including the source, communication method, and validation status.
  • attestation: Attestation details, including mode (such as “legal”), time, and the party providing the attestation.

Commonly used fields in FHIR VerificationResult Resource

Here are some of the commonly used fields in the FHIR VerificationResult resource, along with explanations for each:

  • status: This field indicates the status of the verification process. It can have values like “completed”, “in-progress”, “suspended”, etc. This status reflects the current state of the verification process.
  • target: This field references the resource being verified. It specifies the resource that has undergone the verification process, ensuring the accuracy and validity of the data within that resource.
  • targetLocation: This field indicates a specific location within the target resource that the verification applies to. It’s particularly useful when the target resource contains multiple pieces of data, and the verification is specific to a certain part.
  • verificationDate: This field captures the date and time when the verification was conducted. It helps in tracking when the verification process occurred.
  • validationType: This field describes the type of validation being performed. It typically uses coding systems to specify the validation type, such as “primary” or “secondary”. The validation type helps in understanding the significance and purpose of the verification.
  • validationProcess: This field provides additional details about the validation process itself. It can include information such as identifiers and comments, helping to characterize the specific method or procedure used for verification.
  • primarySource: This field holds information about the primary sources involved in the verification process. It includes details about the entity (e.g., practitioner, organization) responsible for the verification, the communication method used, and the validation status of the source’s data.
  • attestation: This field captures attestation details regarding the verification. Attestation refers to the act of confirming the accuracy and authenticity of data. It includes information about the mode of attestation (e.g., legal, professional), the time of attestation, and the party providing the attestation.
  • failureAction: This field specifies the action to be taken in case the verification process fails. It helps in defining how the system should respond if the data being verified does not meet the required criteria.
  • frequency: This field defines the frequency at which the verification process should be performed. It can specify a repeating pattern, such as daily, weekly, etc., for regular verification checks.
  • lastPerformed and nextScheduled: These fields provide timestamps indicating when the last verification was conducted and when the next verification is scheduled. These timestamps aid in understanding the verification history and upcoming verification plans.

These commonly used fields collectively offer a comprehensive view of the verification process, its outcomes, the entities involved, and the temporal aspects within the FHIR VerificationResult resource. By providing structured information about verification, FHIR facilitates efficient data exchange and enhances the reliability of healthcare information across different systems and stakeholders.

A use case where FHIR VerificationResult Resource can be utilized

Use Case: Verification of Patient Allergy Information

Description: In healthcare settings, accurate and up-to-date patient allergy information is critical to ensuring patient safety. Allergy information plays a crucial role in treatment decisions, medication prescriptions, and avoiding adverse reactions. However, maintaining accurate and consistent allergy data across different healthcare systems can be challenging, especially when patients receive care from multiple providers or institutions. Discrepancies or outdated information can lead to medical errors and compromised patient care.

Solution: The FHIR VerificationResult resource can be utilized to address this challenge by providing a standardized way to verify and communicate the accuracy of patient allergy information. Here’s how the solution could work:

  1. Verification Process Setup: Healthcare institutions establish a verification process for patient allergy information. This process includes defining validation criteria, methods, and frequency for verifying allergy data.
  2. Data Exchange: When a patient’s allergy information is updated or recorded, the FHIR system initiates a verification process. The updated allergy information is sent as the target resource for verification.
  3. Verification Process Execution: The FHIR system performs the verification process, which might involve comparing the updated allergy data against trusted sources, such as patient history, clinical databases, and known allergies for specific medications.
  4. VerificationResult Resource Creation: The FHIR system creates a VerificationResult resource to capture the outcomes of the verification process. The resource includes fields such as status (completed), target (patient resource), validationType (primary validation), validationProcess (describing the allergy validation process), and the date of verification.
  5. Primary Source Verification: Primary sources, such as healthcare providers, are involved in the verification process. The VerificationResult resource includes details about the primary sources, their validation status, and communication methods (e.g., email, API integration) used for verification.
  6. Attestation and Actions: An attestation record is included in the VerificationResult resource, indicating that the allergy information has been verified as accurate. In case of discrepancies or validation failures, the VerificationResult resource specifies the appropriate actions to be taken, such as contacting the patient or re-verifying the data.
  7. Access and Interoperability: Other healthcare systems and providers can access the VerificationResult resource associated with the patient’s allergy information. They can then assess the verification status and attestation details to confidently incorporate the allergy data into their treatment decisions.


  • Patient Safety: Accurate allergy information improves patient safety by reducing the risk of allergic reactions to medications or treatments.
  • Data Consistency: The FHIR VerificationResult resource ensures that allergy data is consistent and reliable across different healthcare systems.
  • Efficient Collaboration: Healthcare providers can trust the verified allergy data, enabling more efficient and informed collaboration in patient care.
  • Reduced Errors: Verification processes reduce the likelihood of errors stemming from outdated or incorrect allergy information.
  • Interoperability: The standardized VerificationResult resource promotes interoperability, allowing seamless communication of verification outcomes among diverse systems and stakeholders.

By utilizing the FHIR VerificationResult resource, healthcare institutions can enhance patient safety, streamline data exchange, and improve the quality of care provided to patients with allergies.

Here are a few general or interview questions related to the VerificationResult resource, which aims to gauge your knowledge about the resource, its practical application, and your understanding of healthcare interoperability principles.

1. What is the purpose of the FHIR VerificationResult resource?

The FHIR VerificationResult resource serves the purpose of providing a standardized format for communicating the outcomes of verification processes related to healthcare data. It ensures the accuracy, validity, and trustworthiness of data exchanged between different healthcare entities within the FHIR framework. By capturing verification details and attestation records, this resource enhances interoperability, data integrity, and patient safety.

2. Can you explain the key components of a FHIR VerificationResult resource?

An FHIR VerificationResult resource consists of several key components:

  • status: Indicates the status of the verification process (e.g., completed, in-progress).
  • target: References the resource being verified.
  • validationType: Describes the type of validation being performed (e.g., primary, secondary).
  • validationProcess: Contains details about the validation process, including identifiers and comments.
  • primarySource: Provides information about the primary sources involved in verification.
  • attestation: Captures details about the attestation, including mode, time, and the party providing attestation.
  • Other fields like targetLocation, verificationDate, frequency, lastPerformed, nextScheduled, and failureAction further, contextualize the verification process.

3. How does the VerificationResult resource contribute to data integrity and patient safety in healthcare?

The VerificationResult resource plays a crucial role in maintaining data integrity and ensuring patient safety. By confirming the accuracy and reliability of healthcare data, it reduces the risk of medical errors and enhances the quality of patient care. The resource enables healthcare systems to confidently exchange verified information, preventing adverse events that may result from incorrect or outdated data.

4. Describe a real-world scenario where the FHIR VerificationResult resource could be utilized.

Imagine a scenario where a patient’s medication history is shared between two hospitals. The FHIR VerificationResult resource can be used to confirm the accuracy of the medication data before it’s integrated into the receiving hospital’s electronic health record (EHR) system. This verification process helps ensure that the patient’s treatment decisions are based on trustworthy information, minimizing the risk of medication-related complications.

5. What is the role of “primary sources” in the VerificationResult resource, and why are they significant?

Primary sources in the VerificationResult resource are entities responsible for validating the data being verified. These sources, often healthcare providers or organizations, play a crucial role in confirming the accuracy and authenticity of information. Their involvement enhances the credibility of the verified data and builds trust among different healthcare stakeholders, leading to informed and safe patient care decisions.

6. How can FHIR VerificationResult resources facilitate interoperability between different healthcare systems?

FHIR VerificationResult resources provide a standardized way to communicate verification outcomes, ensuring that verified data can be shared and understood across different healthcare systems that support the FHIR standard. This enhances interoperability by enabling seamless data exchange and collaborative care between various providers, clinics, hospitals, and other healthcare entities.

7. What are the potential validation types that can be used in the ValidationResult resource, and how do they differ?

Validation types in the VerificationResult resource, such as “primary” or “secondary,” represent the level or importance of the validation being performed. Primary validation signifies a thorough and authoritative verification, often conducted by a reliable source, while secondary validation might involve less critical data or additional verification steps. These types help categorize and prioritize verification processes based on their significance.

8. How would you handle a situation where a VerificationResult resource indicates a failed verification?

In case of a failed verification, appropriate actions should be taken to rectify the issue. Depending on the nature of the failure, steps could include re-verifying the data with the primary source, notifying the relevant healthcare providers, updating the data with accurate information, and ensuring that patients are informed of the discrepancies to prevent potential medical errors.

9. Describe the information included in the “attestation” section of the VerificationResult resource.

The “attestation” section of the VerificationResult resource contains details about the process of confirming the accuracy and authenticity of the data being verified. It includes the mode of attestation (e.g., legal, professional), the time of attestation, and the party providing the attestation, which could be an organization or individual verifying the data’s correctness.

10. How does the FHIR VerificationResult resource contribute to ensuring compliance with regulatory standards in healthcare data exchange?

The FHIR VerificationResult resource helps healthcare organizations meet regulatory standards by providing a standardized way to document and communicate the verification processes. By ensuring the accuracy and reliability of shared healthcare data, the resource contributes to maintaining data integrity and adhering to regulatory requirements, which ultimately support patient safety and compliance with industry standards.

11. Can you provide an example of how the FHIR VerificationResult resource can be used in the context of medication management?

Imagine a scenario where a physician prescribes a new medication for a patient. Before administering the medication, the healthcare system can utilize the FHIR VerificationResult resource to confirm the patient’s allergies and potential drug interactions. The resource would contain details about the verification process, primary sources verifying the allergy data, and the attestation that the medication is safe for the patient, ensuring accurate and informed treatment decisions.

12. How does the FHIR VerificationResult resource contribute to the overall data quality and reliability in healthcare?

The FHIR VerificationResult resource ensures data quality and reliability by providing a structured mechanism to validate and confirm the accuracy of healthcare information. It promotes standardized verification processes, involves primary sources, captures attestation details, and offers a consistent way to communicate the outcomes. This comprehensive approach enhances the trustworthiness of shared data, reducing errors and improving the overall quality of healthcare information.

13. Explain the concept of “targetLocation” within the FHIR VerificationResult resource.

The “targetLocation” field in the VerificationResult resource specifies a specific location within the target resource where the verification is applied. This is particularly useful when the target resource contains multiple pieces of data. By indicating the precise location, the verification process can focus on verifying a specific data element or attribute, rather than the entire resource.

14. Can you provide examples of potential “failureAction” codes used in the VerificationResult resource and explain their implications?

The “failureAction” codes in the VerificationResult resource indicate the actions to be taken in case of verification failure. Examples include:

  • “fatal”: Indicates that the failure is significant and requires immediate action, possibly leading to treatment adjustments.
  • “warning”: Suggests a less critical failure, prompting a cautionary approach without immediate action.
  • “informational”: Denotes minor or informational failures that may not require immediate intervention but should be noted for future reference.

15. What is the role of the “validationProcess” field in the VerificationResult resource?

The “validationProcess” field in the VerificationResult resource provides additional context about the specific validation method or process used during verification. It includes identifiers and comments that describe the steps taken to validate the data, enhancing the understanding of how the verification was conducted.


In the evolving landscape of healthcare, the FHIR VerificationResult resource emerges as a cornerstone for fostering data accuracy, trust, and interoperability. As healthcare systems grapple with the complexities of sharing and exchanging critical patient information, this resource serves as a robust framework to verify the integrity of data traversing across diverse entities. By encapsulating verification outcomes, attestation records, and contextual details, the VerificationResult resource not only enhances the reliability of healthcare data but also reinforces patient safety through informed decision-making.

In a world where patient care spans multiple providers, institutions, and technological platforms, the FHIR VerificationResult resource stands as a unifying element. It harmonizes the process of validating information, engaging primary sources, and maintaining consistent records of data verification. As healthcare organizations strive to achieve interoperability, comply with regulatory standards, and deliver patient-centered care, the VerificationResult resource emerges as a testament to the power of standardized solutions in revolutionizing the healthcare landscape. Its role in ensuring accurate, verified data reverberates across medical decision-making, promoting precision, minimizing errors, and ultimately contributing to improved patient outcomes.

I hope you find this post helpful. Cheers!!!

[Further Readings: FHIR InventoryReport Resource |  FHIR OrganizationAffiliation Resource | FHIR SupplyDelivery Resource |  FHIR SupplyRequest Resource |  FHIR GuidanceResponse Resource |  FHIR DeviceAssociation Resource | FHIR DeviceDispense Resource  | FHIR DeviceRequest Resource   | FHIR QuestionnaireResponse Resource |  FHIR Questionnaire Resource |  FHIR PlanDefinition Resource |  FHIR Task Resource | FHIR RegulatedAuthorization Resource |  FHIR ManufacturedItemDefinition Resource |  FHIR AdministrableProductDefinition Resource |  FHIR PackagedProductDefinition Resource |  FHIR ClinicalUseDefinition Resource |  FHIR Ingredient Resource |  FHIR MedicinalProductDefinition Resource  | FHIR ExplanationOfBenefit Resource | FHIR PaymentReconciliation Resource |  FHIR PaymentNotice Resource | FHIR ClaimResponse Resource | FHIR Claim Resource |  FHIR EnrollmentResponse Resource | FHIR EnrollmentRequest Resource | FHIR CoverageEligibilityResponse Resource | FHIR CoverageEligibilityRequest Resource |  FHIR Contract Resource | Dependency Injection in WPF ]

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x