Quality review summary

Generated Fri Mar 28 13:27:41 CET 2025, FHIR version 4.0.1 for ihe.iti.mcsd#4.0.0-comment (https://profiles.ihe.net/ITI/mCSD)

IG Publisher Q/A summaryerrors = 0, warn = 0, info = 0, broken links = 0. Show Message Ids
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 24
interactions 174
search parameters 218

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: ITI-91.html, ITI-90.html, ITI-130.html
Pages and organization Separate display of non-normative content True Pages: other.html, index.html, download.html, testplan.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 False
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): The Mobile Care Services Discovery (mCSD) Profile supports RESTful queries across related care services resources. The loosely coupled design and flexible querying capability of the mCSD Profile means it can be deployed within a variety of eHealth architectures and support a wide array of care workflows.
  • Extract (page volume-1.html): The Mobile Care Services Discovery (mCSD) Profile supports creating, updating, deleting and discovery of care services resources using a RESTful interface in interrelated, federated environments.
  • Extract (page ITI-130.html): Access controls should be considered to ensure only allowed users and/or systems are able to update data. This may include resource or element level controls as well as Provenance for documenting the data source. These access controls could be addressed by the client or the server as dictated by the implementation.
Writing and narrative Presence an explanation of what "mustSupport" means for different types of implementations of the IG True
  • Extract (page index.html): RequiredSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor SHALL populate the elements marked with RequiredSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit.
Writing and narrative Presence of information on how to engage with the community True
  • Extract (page testplan.html): Comments are welcome.
Writing and narrative Presence of an explanation of the relationship of the IG to any other guides True
  • Extract (page volume-1.html): The mCSD Profile may be employed to support, for example, the Provider Queries listed by the US Office of the National Coordinator as part of the Standards and Interoperability Framework. In addition, mCSD can enable connectivity by providing service endpoint lookup, such as 'What is the FHIR server for this organization?'. The mCSD Profile provides a way to query that list of practitioners for the Mobile Alert Communication Management (mACM) Profile.
  • Extract (page ITI-91.html): See ITI TF-2: Appendix W for informative implementation material for this transaction.
  • Extract (page artifacts.html): Changes to Other IHE Specifications
  • Extract (page other.html): This section contains modifications to other IHE publications and profiles and is not a part of the mCSD Profile. The content here will be incorporated into the target narrative at a future time, usually when mCSD goes final text.
  • Extract (page download.html): Cross Version Analysis: This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.iti.mcsd.r4) and R4B (ihe.iti.mcsd.r4b) are available.
Security and privacy considerationsPresence of a section focused on security or privacy True
  • Extract (page index.html): Security Considerations
  • Extract (page volume-1.html): Actors are expected to follow the recommendations and requirements found in ITI TF-2: Appendix Z.8 “Mobile Security Considerations”. The resources exchanged in this profile may contain information which pose a privacy risk, or in some cases, a safety risk, to providers and other personnel, as well as patients. For example, practitioner phone numbers and home addresses may be conveyed. Implementers should determine what data will be exposed by the system and what level of public access there will be if any.
  • Extract (page ITI-90.html): 2:3.90.5 Security Considerations See ITI TF-1: 46.5 for security considerations for the mCSD Profile. See ITI TF-2: Appendix Z.8 for common mobile security considerations. 2:3.90.5.1 Security Audit Considerations Note that when grouped with ATNA Secure Node or Secure Application Actor, the same audit message is recorded by both Directory and Query Client. The difference being the Audit Source element. Both sides record to show consistency between the message sent by the Directory and the action taken at the Query Client.
  • Extract (page ITI-91.html): 2:3.91.5 Security Considerations See ITI TF-1: 46.5 for security considerations for the mCSD Profile. See ITI TF-2: Appendix Z.8 for common mobile security considerations.
  • Extract (page ITI-130.html): Access controls should be considered to ensure only allowed users and/or systems are able to update data. This may include resource or element level controls as well as Provenance for documenting the data source. These access controls could be addressed by the client or the server as dictated by the implementation. It is recommended to use IUA for authorization.
  • Extract (page artifacts.html): Overview Security Considerations
  • Extract (page other.html): Security Considerations
  • Extract (page download.html): This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log.
  • Extract (page testplan.html): Overview Security Considerations
  • Extract (page toc.html): Security Considerations

Comparison capability statements / narrative

IHE_mCSD_Directory_Location_Distance_Option

Resource Resource difference Interactions differences Search parameters differences
HealthcareService Not in CS
Practitioner Not in CS
Organization Not in CS
OrganizationAffiliationNot in CS
Endpoint Not in CS
Facility Not in CS
PractitionerRole Not in CS
Location
  • Not in CS: organization, _id, identifier, name, _lastUpdated, type, status

IHE_mCSD_Directory_Update

Resource Resource difference Interactions differences Search parameters differences
Jurisdiction Not in CS
Facility Not in CS
HealthcareService
  • Not in CS: location, organization, identifier, name, active, service-type
Practitioner
  • Not in CS: given, identifier, name, active, family
Organization
  • Not in CS: identifier, name, type, active
OrganizationAffiliation
  • Not in CS: role, date, identifier, active, participating-organization, primary-organization
Endpoint
  • Not in CS: organization, identifier, status
Location
  • Not in CS: type, status, organization, identifier, name
PractitionerRole
  • Not in CS: location, role, specialty, organization, practitioner, active, service

IHE_mCSD_Directory_Feed

Resource Resource difference Interactions differences Search parameters differences
HealthcareService
  • Not in CS: location, _lastUpdated, organization, _id, identifier, name, active, service-type
Practitioner
  • Not in CS: _id, identifier, name, active, _lastUpdated, family, given
Organization
  • Not in CS: _id, identifier, name, active, _lastUpdated, type
OrganizationAffiliation
  • Not in CS: role, _lastUpdated, date, _id, identifier, active, participating-organization, primary-organization
Endpoint
  • Not in CS: organization, _id, identifier, _lastUpdated, status
Location
  • Not in CS: organization, _id, identifier, name, _lastUpdated, type, status
PractitionerRole
  • Not in CS: location, role, _lastUpdated, specialty, organization, _id, practitioner, active, service

IHE_mCSD_Update_Client

Resource Resource difference Interactions differences Search parameters differences
Jurisdiction Not in CS
Facility Not in CS
HealthcareService
  • Not in CS: location, organization, identifier, name, active, service-type
Practitioner
  • Not in CS: given, identifier, name, active, family
Organization
  • Not in CS: identifier, name, type, active
OrganizationAffiliation
  • Not in CS: role, date, identifier, active, participating-organization, primary-organization
Endpoint
  • Not in CS: organization, identifier, status
Location
  • Not in CS: type, status, organization, identifier, name
PractitionerRole
  • Not in CS: location, role, specialty, organization, practitioner, active, service

IHE_mCSD_Query_Client_Location_Distance_Option

Resource Resource difference Interactions differences Search parameters differences
Jurisdiction Not in CS
HealthcareService Not in CS
Practitioner Not in CS
Organization Not in CS
OrganizationAffiliationNot in CS
Endpoint Not in CS
Facility Not in CS
PractitionerRole Not in CS
Location
  • Not in CS: organization, identifier, name, type, status

IHE_mCSD_Directory

Resource Resource difference Interactions differences Search parameters differences
Jurisdiction Not in CS
Facility Not in CS
HealthcareService
  • Not in narrative: _id, _lastUpdated
Practitioner
  • Not in narrative: _id, _lastUpdated
Organization
  • Not in narrative: _id, partof, _lastUpdated
OrganizationAffiliation
  • Not in narrative: _id, _lastUpdated
Endpoint
  • Not in narrative: _id, _lastUpdated
Location
  • Not in narrative: _id, partof, _lastUpdated
PractitionerRole
  • Not in CS: practitioner

IHE_mCSD_Query_Client

Resource Resource difference Interactions differences Search parameters differences
Facility Not in CS
HealthcareService
  • Not in narrative: _id, _lastUpdated
Practitioner
  • Not in narrative: _id, _lastUpdated
Organization
  • Not in narrative: _id, partof, _lastUpdated
OrganizationAffiliation
  • Not in narrative: _id, _lastUpdated
Endpoint
  • Not in narrative: _id, _lastUpdated
Location
  • Not in narrative: _id, partof, _lastUpdated
PractitionerRole
  • Not in CS: practitioner

IHE_mCSD_Data_Source

Resource Resource difference Interactions differences Search parameters differences
Jurisdiction Not in CS
Facility Not in CS
HealthcareService
  • Not in CS: organization, identifier, location, name, active, service-type
Practitioner
  • Not in CS: identifier, name, active, family, given
Organization
  • Not in CS: identifier, name, type, active
OrganizationAffiliation
  • Not in CS: date, identifier, active, role, participating-organization, primary-organization
Endpoint
  • Not in CS: organization, identifier, status
Location
  • Not in CS: organization, identifier, name, type, status
PractitionerRole
  • Not in CS: organization, practitioner, location, active, role, specialty, service