Quality review summary

Generated Wed Jul 02 14:52:13 CEST 2025, FHIR version 4.0.1 for ans.fhir.fr.gap#3.0.0

Quality checks summary
Domain Check=True Check=False
Pages and organization 7 0
Writing and narrative 4 1
Security and privacy considerations 1 0
Comparison capability statements / narrative summary
item Number of differences
resources 23
interactions 71
search parameters 113

Quality checks

Inspired by IG Best Practices described in Guidance for FHIR IG Creation

domain criteria check proof
Pages and organization Separate display of normative content True Pages: specifications_techniques.html
Pages and organization Separate display of non-normative content True Pages: downloads.html, index.html, construction_des_flux.html, toc.html
Pages and organization Presence of index page True Page: index.html
Pages and organization Presence of toc page True Page: toc.html
Pages and organization Presence of artifacts page True Page: artifacts.html
Pages and organization Presence of background page True Page: background.html
Pages and organization Presence of downloads page True Page: downloads.html
Writing and narrative Index page starts with a patient-friendly explanation of the purpose of the IG True Extract (page index.html): The purpose of this implementation guide is to allow the management of resources (people, places or objects), the management of the availability of these resources, the consultation and synchronization of calendars and the making of appointments.
Writing and narrative Presence of a section that explains key information that needs to be understood prior to reading the IGTrue
  • Extract (page index.html): Cette spécification technique s’appuie sur le standard HL7 FHIR et son API REST. L’hypothèse est faite que le lecteur est familier de ces concepts.
  • Extract (page mapping.html): Cette page a pour objectif de mettre en correspondance les ressources FHIR avec les objets métiers du MOS et avec iCalendar.
  • Extract (page securite.html): Les données véhiculées à travers ces flux sont des données à caractère personnel contenant notamment les noms des patients et des professionnels de santé.
Writing and narrative Presence an explanation of what "mustSupport" means for different types of implementations of the IG False
Writing and narrative Presence of information on how to engage with the community True
  • Extract (page flux-gestion-agenda.html): Pour plus d’information sur les profils, consultez les dépendances et les guides d’implémentations associés.
Writing and narrative Presence of an explanation of the relationship of the IG to any other guides True
  • Extract (page index.html): Dépendances IGPackageFHIRComment Gestion d'Agendas Partagés (GAP) ans.fhir.fr.gap#3.0.0R4
  • Extract (page construction_des_flux.html): Une mise en correspondance est faite entre : Les objets métier identifiés à l’issue des spécifications fonctionnelles du volet Gestion d’agendas partagés... Et les ressources et éléments du standard HL7 FHIR.
  • Extract (page flux-gestion-ressources.html): Pour plus d’information sur les profils, consultez les dépendances et les guides d’implémentations associés.
  • Extract (page flux-gestion-agenda.html): Pour plus d’information sur les profils, consultez les dépendances et les guides d’implémentations associés.
  • Extract (page mapping.html): Cette annexe met en correspondance les composants et les propriétés iCalendar avec les ressources et les éléments FHIR de ce volet. Ceci est proposé dans le but de faciliter l’intégration de certains éléments dans les agendas personnels des utilisateurs.
Security and privacy considerationsPresence of a section focused on security or privacy True
  • Extract (page index.html): Il est à noter que les contraintes de sécurité concernant les flux échangés ne sont pas traitées dans ce document. Celles-ci sont du ressort de chaque responsable de l’implémentation du mécanisme qui est dans l’obligation de se conformer au cadre juridique en la matière.
  • Extract (page construction_des_flux.html): Sécurité
  • Extract (page flux-gestion-ressources.html): Sécurité Téléchargements et usage
  • Extract (page flux-gestion-agenda.html): Sécurité
  • Extract (page flux-gestion-dispo.html): Sécurité
  • Extract (page flux-demande-consultation.html): Sécurité
  • Extract (page flux-gestion-rdv.html): Sécurité
  • Extract (page specifications_fonctionnelles.html): Sécurité
  • Extract (page artifacts.html): Sécurité
  • Extract (page mapping.html): Sécurité
  • Extract (page securite.html): Les données véhiculées à travers ces flux sont des données à caractère personnel contenant notamment les noms des patients et des professionnels de santé. Cette section présente les éventuelles recommandations de sécurité qui s’appliquent au volet Gestion d’Agendas Partagés.
  • Extract (page downloads.html): Sécurité
  • Extract (page toc.html): 4.2 Sécurité
  • Extract (page specifications_techniques.html): Sécurité

Comparison capability statements / narrative

GAP_Declarant

Resource Resource difference Interactions differences Search parameters differences
Slot Not in capability statement
Appointment Not in capability statement
RelatedPerson
  • Not in capability statement: read
Practitioner
  • Not in capability statement: read
Device
  • Not in capability statement: read
PractitionerRole
  • Not in capability statement: read
Organization
  • Not in capability statement: read
Schedule
  • Not in capability statement: read
HealthcareService
  • Not in capability statement: read
Location
  • Not in capability statement: read
Patient
  • Not in capability statement: read

GAP_consommateur

Resource Resource difference Interactions differences Search parameters differences
RelatedPerson
  • Not in narrative: telecom, identifier, address, name
Practitioner
  • Not in narrative: identifier, given, family
Device
  • Not in narrative: model, identifier, device-name, type
PractitionerRole
  • Not in narrative: telecom, specialty, location, role
Appointment
  • Not in capability statement: actor:Location.identifier, actor:Practitioner.identifier, actor:Device.identifier, created, description, actor:HealthcareService.identifier, actor:Patient.identifier, priority, actor:RelatedPerson.identifier
Organization
  • Not in narrative: identifier, address, name
Schedule
  • Not in narrative: actor
HealthcareService
  • Not in narrative: identifier, service-type, organization, name
Location
  • Not in narrative: identifier, address, name
Slot
  • Not in capability statement: schedule.actor:Location.address, schedule.actor:PractitionerRole.role, schedule.actor:PractitionerRole.telecom, schedule.actor:PractitionerRole.name, schedule.actor:PractitionerRole.specialty, schedule.actor:HealthcareService.service-type, schedule.actor:Practitioner.identifier, schedule.actor:RelatedPerson.telecom, schedule.actor:HealthcareService.organization.identifier, schedule.actor:Device.identifier, schedule.actor:Device.device-name, schedule.actor:Location.name, schedule.actor:HealthcareService.name, schedule.actor:HealthcareService.identifier, schedule.actor:PractitionerRole.location.address, schedule.actor:HealthcareService.organization.name, schedule.actor:Patient.given, schedule.actor:Device.model, schedule.actor:Patient.identifier, schedule.actor:RelatedPerson.identifier, schedule.actor:Device.type, schedule.actor:HealthcareService.organization.address, schedule.actor:Patient.family, schedule.actor:RelatedPerson.address, schedule.actor:RelatedPerson.name, schedule.actor:Location.identifier, start
Patient
  • Not in narrative: identifier, given, family

GAP_DeclarantRDV

Resource Resource difference Interactions differences Search parameters differences
RelatedPerson Not in capability statement
Practitioner Not in capability statement
PractitionerRole Not in capability statement
Device Not in capability statement
Organization Not in capability statement
Schedule Not in capability statement
HealthcareServiceNot in capability statement
Location Not in capability statement
Slot Not in capability statement
Patient Not in capability statement
Appointment
  • Not in capability statement: actor:Location.identifier, actor:Practitioner.identifier, actor:Device.identifier, status, created, date, description, actor:HealthcareService.identifier, actor:Patient.identifier, priority, identifier, service-type, actor:RelatedPerson.identifier, supporting-info

GAP_GestionnaireAgenda

Resource Resource difference Interactions differences Search parameters differences
RelatedPerson Not in capability statement
Practitioner Not in capability statement
Device Not in capability statement
PractitionerRole Not in capability statement
Organization Not in capability statement
Location Not in capability statement
HealthCareServiceNot in capability statement
Patient Not in capability statement
Schedule
  • Not in capability statement: vread, read
Slot
  • Not in capability statement: schedule.actor:PractitionerRole.name, schedule.actor:Practitioner.identifier, schedule.actor:Device.identifier, schedule.actor:Patient.identifier, schedule.actor:RelatedPerson.identifier, schedule.actor:HealthcareService.identifier, schedule.actor:Location.identifier, start
Appointment
  • Not in capability statement: actor:Location.identifier, actor:Practitioner.identifier, actor:Device.identifier, actor:HealthcareService.identifier, actor:Patient.identifier, actor:RelatedPerson.identifier

GAP_GestionnaireRessources

Resource Resource difference Interactions differences Search parameters differences
Schedule Not in capability statement
Slot Not in capability statement
Appointment Not in capability statement
RelatedPerson
  • Not in capability statement: read
Practitioner
  • Not in capability statement: read
Device
  • Not in capability statement: read
PractitionerRole
  • Not in capability statement: read
Organization
  • Not in capability statement: read
HealthcareService
  • Not in capability statement: read
Location
  • Not in capability statement: read
Patient
  • Not in capability statement: read