Validation Results for SmartSchedulingLinks

Generated Wed Apr 22 16:24:22 UTC 2026, FHIR version 4.0.1 for hl7.fhir.uv.smart-scheduling-links#1.0.0-ballot (canonical = http://hl7.org/fhir/uv/smart-scheduling-links (history)). See Full QA Report & IP

Quality Checks
Publisher Version:	IG Publisher Version: v2.2.6
Publication Code:	smart-scheduling-links . PackageId = hl7.fhir.uv.smart-scheduling-links, Canonical = http://hl7.org/fhir/uv/smart-scheduling-links
Realm Check for UV:	n/a
Language Info:	Stated Languages: n/a. IG Resource Lang: en. 10 of 19 (52%) of resources have a language. Population Policy: NONE
Publication Request:	RelatedIgs (None Found) Version 1.0.0-ballot has already been published This is not the first publication, so first must not be true Publication Request is for version v1.0.0-ballot which is already published
Supressed Messages:	4 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.uv.smart-scheduling-links 1.0.0-ballot R4 http://hl7.org/fhir/uv/smart-scheduling-links hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.tools.r4 1.1.2 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/1.1.2 Internal Dependency Templates: hl7.smart.template#0.0.1 -> hl7.fhir.template#current -> hl7.base.template#current -> fhir2.base.template#current
Related IGs:	n/a
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:	no Non-HL7 references found
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (16 uses), HealthcareService (2 uses), CommonLanguages (8 uses), Organization (5 uses), ServiceCategory (3 uses), ServiceType (3 uses), Location (4 uses), ServiceProvisionConditions (1 uses), Program (1 uses), ReferralMethod (1 uses), Endpoint (3 uses), LocationStatus (1 uses), LocationMode (1 uses), LocationType (1 uses), Practitioner (2 uses), PractitionerRole (2 uses), PractitionerRole (1 uses), Schedule (2 uses), RelatedPerson (1 uses), Device (1 uses), Slot (1 uses), SlotStatus (1 uses) hl7.fhir.uv.extensions.r4#5.2.0: SDStatusDerivation (18 uses)
Modifier Extensions:	(none)
Previous Version Comparison:
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary:	errors = 0, warn = 0, info = 0, broken links = 0, pinned = n/a. Show Message Ids

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

Suppress per FMG QA Review on 3/24/26

• The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)

Suppress per FMG QA Review on 3/24/26. Need to address later.

• INFORMATION: en/StructureDefinition-smart-scheduling-location.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'If a PractitionerRole or Location is associated with organization-specific identifiers (such as facility numbers, site codes, or store numbers), publishers SHOULD include these. The system should be a URL that identifies the identifier system, preferably a page on the publisher's web site (e.g. {"system": "https://healthsystem.example.com/facility-directory", "value": "FAC-123"})' (1 uses)
• INFORMATION: en/StructureDefinition-smart-scheduling-slot.html: The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' Each line of the Slot File is a minified JSON object that conveys information about an appointment slot. Publishers are encouraged to represent slots with fine-grained timing details (e.g. representing appointments at specific times of the day), but MAY represent slots with coarse grained timing (e.g., "between 9 a.m. and 5 p.m." or "between noon and five p.m."). ' (1 uses)
• INFORMATION: en/specification.html: The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Slot Files. Each line contains a minified JSON object representing an appointment slot (busy or free) for a healthcare service at a specific location. Details on JSON structure 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. ' (1 uses)

Errors sorted by type