Unable to find ImplementationGuide.definition.resource.description for the resource PractitionerRole/doc-smith-role. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
warning
The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' If a PractitionerRole is associated with organization-specific identifiers (such as role-specific employee numbers, provider numbers, or location-specific identifiers), 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/practitioner-role-directory", "value": "ROLE-123"}) 'CONFORMANCE_STATEMENT_WORD
en/index.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Slot data discovered by a Slot Discovery Client may not reflect current availability by the time a user reaches the Provider Booking Portal. Staleness between publication cycles is one source of invalidity, but others exist — for example, eligibility requirements, referral prerequisites, provider schedule changes, or concurrent bookings. Slot Publishers SHOULD provide data with appropriate freshness (see Cache-Control guidance). Slot Discovery Clients and Slot Aggregators MAY enrich slot data with additional attributes to improve provider-and-slot matching for their users. Because the full range of validity considerations is broad and context-dependent, this specification intentionally leaves much of the handling to implementers — with the key backstop being that the Provider Booking Portal is the closest system to the source of truth. Provider Booking Portals SHOULD handle slot invalidity gracefully, preserving as much of the user's original intent as possible (see Graceful Handling of Slot Invalidity in the specification).'CONFORMANCE_STATEMENT_WORD
en/specification.html
information
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. Slot profile 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. 'CONFORMANCE_STATEMENT_WORD
ImplementationGuide/hl7.fhir.uv.smart-scheduling-links: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide.dependsOn[2] (l1/c2747)
warning
The ImplementationGuide uses package hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2 released on 2025-09-13, but the most recent appropriate version is 0.1.0. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
--
Resource
information
The resource ImplementationGuide/hl7.fhir.uv.smart-scheduling-links could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/booking-deep-link could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/booking-phone could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/schedule-specialty could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'MSG_DEPENDS_ON_DEPRECATED_NOTE
The resource StructureDefinition/smart-scheduling-healthcare-service could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#6.5.0), 3.0.0 (from hl7.terminology.r4#7.3.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
The resource StructureDefinition/smart-scheduling-location could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/smart-scheduling-practitioner could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/smart-scheduling-practitionerRole could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/smart-scheduling-schedule could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/smart-scheduling-slot could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Pinned the version of http://terminology.hl7.org/CodeSystem/v2-0276 to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#6.5.0), 2.1.0 (hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2), 3.0.0 (hl7.terminology.r4#7.3.0)PIN_VERSION
--
Resource
error
The resource ValueSet/appointment-type-and-reasons-vs must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (0 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. ' (0 uses)
The ImplementationGuide uses package hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2 released on 2025-09-13, but the most recent appropriate version is 0.1.0. This reference is getting old and the more recent version should be considered
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'
Pinned the version of http://terminology.hl7.org/CodeSystem/v2-0276 to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#6.5.0), 2.1.0 (hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2), 3.0.0 (hl7.terminology.r4#7.3.0)
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#6.5.0), 3.0.0 (from hl7.terminology.r4#7.3.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0'
hl7.fhir.uv.smart-scheduling-links
hl7.terminology.r4
