This fragment is available on en/index.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | appointments.acmehealth.org | telecom : ph: (555) 123-4567(Work), appointments@acmehealth.org , https://appointments.acmehealth.org |
| web | tel:+1-813-555-0100 | telecom : +1-813-555-0100 , contact@openclintech.com |
| web | tel:+1-93-736-544 | telecom : +1-93-736-544 , johnmark@user.com |
| web | ehr.example.org | Booking Deep Link : https://ehr.example.org/booking/slots/123 |
| web | github.com | SMART Scheduling Links, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/smart-scheduling-links/ and changes regularly. See the Directory of published versions |
| web | github.com | Extends base SMART Scheduling Links Spec beyond the original use case to include general patient appointments. |
| web | github.com | Introduced SMART Scheduling Links as a standards-based specification to enable patients to find appointment slots, follow a deep link, and complete a booking for COVID-19 immunizations. |
| web | www.google.com | A directory of published, bookable slots might find itself in a situation where multiple publishers are advertising slots for the same provider or group of providers. Rather than advocating for tiebreaking or proposing a prioritization scheme, there's another analogy we lean on: Reserve with Google . Similar to how a restaurant may participate in multiple food delivery apps, all of which are legitimate pathways to ordering food, a medical practice may participate in online booking via their EHR, their patient engagement software, or online marketplaces. This gives patients seeking care options to not only select the provider with the best fit, but to choose among options for the booking and patient engagement experience. |
| web | raw.githubusercontent.com | Example file showing a manifest for the fictional "SMART Medicine", a regional chain with twenty locations in Massachusetts, a mix of urgent care and primary care practices. |
| web | raw.githubusercontent.com | Example file showing ten practitioner roles for the fictional "SMART Primary Care". Each line provides details about a single PractitionerRole in the MA area. |
| web | raw.githubusercontent.com | Example file showing ten locations for the fictional "SMART Urgent Care". Each line provides details about a single physical location in the MA area. |
| web | raw.githubusercontent.com | Example file showing ten schedules schedules for "SMART Primary Care" and ten schedules for "SMART Urgent Care." Each line provides details about a single schedule. |
| web | raw.githubusercontent.com | Example file showing coarse-grained slots for a single week, across all twenty "SMART Medicine" sites. ( Note: The choice to break down slots into weekly files is arbitrary; the fictional Clinic could instead choose to host a single slot file, or produce location-specific files, or even group slots randomly. ) Slots MAY include only coarse-grained timing (indicating they fall sometime beetween 9a and 6p ET, the clinic's fictional hours of operation). Ideally, Slot Publishers SHOULD provide finer-grained slot information with specific timing. |
| web | developer.mozilla.org |
Slot Publishers
SHOULD include a
Cache-Control: max-age=<seconds> header
as a hint to clients about how long (in seconds) to wait before polling next. For example, Cache-Control: max-age=300
indicates a preferred polling interval of five minutes.
|
| web | raw.githubusercontent.com | Example file |
| web | raw.githubusercontent.com | Example file |
| web | raw.githubusercontent.com | Example file |
| web | raw.githubusercontent.com | Example file |
|
../assets/images/001.svg
|
|
ERDiagram.png
|
|
SchedulingArchitecture.drawio.png
|
|
tree-filter.png
|