HealthRecordCommunity
FHIRHL7SNOMED CT🌏 InternationalEnriched

FHIR Appointment Resource Structure Definition: Example based on Argonaut Scheduling Guidelines

Appointment/Appointment-proposed-appt1.json - FHIRsmith: npm.fhir.org

August 13, 2026

Summary

This document presents a concrete data structure for the FHIR 'Appointment' resource. The example confirms that a specific appointment (Office Call) is set in the Dermatology specialty, defining multiple participants and an associated period.

Details

This page provides a concrete implementation example of the FHIR 'Appointment' resource. A key technical point is its adherence to the Argonaut Scheduling guidelines (`http://fhir.org/guides/argonaut-scheduling/StructureDefinition/argo-appt`). The data shown, with ID 'proposed-appt1', has a status of 'proposed'. The service type specifies an Office Call in the Dermatology specialty using SNOMED CT code '394582007', and the appointment type is set as Routine. Furthermore, the resource defines multiple participants (Participant). One is a Practitioner named 'Dr Y', and the other is 'Napa Office'. Both have a status of 'needs-action', indicating that action is required to confirm the booking. The resource also confirms that the appointment is set over a specific period (requestedPeriod). Using FHIR standards allows complex scheduling information, such as specialties and participant roles, to be exchanged in a standardized format between medical institutions. This significantly contributes to improving interoperability in Japan's electronic health record systems and regional care networks. This example serves as useful reference material for practical data structure implementation.

πŸ“°
Read Original Article
packages2.fhir.org
β†’

Original content copyright by respective publishers