IG quality review report

Generated Friday 06 February 2026 (14:33), FHIR version 4.0.1 for ihe.iti.mhd#4.2.3

Quality review summary

Domain Checks (✅/❌)
Pages and organization
5
0
Writing and narrative
5
2
Artifacts
2
0

Quality checks

Inspired by IG Best Practices described in Guidance for FHIR IG Creation and FHIR IG Publishing requirements

Domain Criteria Check Proof
Pages and organizationPresence of page: index Page: index.html
Pages and organizationPresence of page: toc Page: toc.html
Pages and organizationPresence of page: artifacts Page: artifacts.html
Pages and organizationPresence of FHIR version in all pages:
Pages and organizationPresence of IG version in all pages:
Writing and narrative Presence of a section that explains key information that needs to be understood prior to reading the IG:
Writing and narrative Presence of an explanation of what 'mustSupport' means for different types of implementations of the IG:Extract per page:
  • index.html: MHD defines Must Support in StructureDefinition profiles as the element, when the minimal cardinality is zero, is R2 Required if Known, as found in Appendix Z. Must Support when the element minimal cardinality is not zero means R.
Writing and narrative Presence of information on how to engage with the community: Extract per page:
  • ITI-106.html: The Document Recipient may impose specific constraints on the input document, such as conforming to International Patient Summary (IPS) or Consolidated Clinical Document Architecture (C-CDA) 2.1. These constraints may be further refined within the Community.
Writing and narrative Presence of an explanation of the relationship of the IG to any other guides:
Writing and narrative Presence of a reference to the IG registry as a location to find more IGs of interest: Extract per page:
  • 31_xds.html: 3:4.2.4.1 RegistryError Element
Writing and narrative Presence of background information providing context and motivation for the IG: Extract per page:
  • 1334_overview.html: The MHD Profile enables sharing of patient documents to, or from, mobile or constrained devices. Other IHE profiles, chiefly Cross-Enterprise Document Sharing (XDS), describe sharing of patient document in less constrained environments, and many of the concepts from those profiles are applicable to the MHD environment. For more information on IHE Document Sharing, see Health Information Exchange: Enabling Document Sharing Using IHE Profiles White Paper.
Writing and narrative Presence of information on how to access downloadable artifacts and resources: Extract per page:
  • index.html: Test Plan Download and Analysis
  • 1331_actors_and_transactions.html: MHD Home ... Downloaded Version 4.2.3 See the Directory of published versions
  • 1332_actor_options.html: Download
  • 1333_required_grouping.html, 1334_overview.html, 1335_security_considerations.html, 1336_cross_profile_considerations.html, ITI-65.html, ITI-67.html, ITI-68.html, ITI-105.html, ITI-106.html, artifacts.html: Mobile access to Health Documents (MHD) - Downloaded Version 4.2.3 See the Directory of published versions
  • ITI-66.html: Mobile access to Health Documents (MHD) - Downloaded Version 4.2.3
  • 31_xds.html: MHD - Downloaded Version 4.2.3
  • 32_fhir_maps.html: 3:4.5 FHIR Maps Mobile access to Health Documents (MHD) - Downloaded Version 4.2.3 See the Directory of published versions 3:4.5 FHIR Maps Artifact Index Test Plan Download
  • testplan.html: MHD is an API between four actors. The transactions between actors specify semantics of the data exchanged. The MHD test plan focuses on these semantics and on the expected actions on the server-side actors (Document Recipient and Document Responder).
  • download.html: You can download: this entire guide, the definition resources in json, xml, ttl, or csv format, or the example resources in json, xml or ttl format.
  • toc.html: Download and Analysis
  • a_issues.html: This version of MHD supports Replace operations.
Artifacts Presence of element text in all artifacts:
Artifacts Presence of elements publisher, contact in artifacts of type ImplementationGuide: