Error fetching package-list from https://trxhub.mediservice.ch/fhir: (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Unable to compare with previous version: Unable to find version history at https://trxhub.mediservice.ch/fhir (Problem #1 with package-list.json at https://trxhub.mediservice.ch/fhir: (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
The page has more than one top level heading: <h2> 'Overview' (id=overview) is at the same level as the first heading on the page (<h2> 'Resource Profile: TRxHub MedicationDispense' (id=root)). A page must have exactly one top level heading, with every other heading beneath it (WCAG compliance test)HTML_HEADING_MULTIPLE_ROOTS
The heading <h1> '🦖 TRxHub Implementation Guide' (id=-trxhub-implementation-guide) is at a higher level than the first heading on the page (<h2> 'Home'). The first heading on a page must be its top level heading (WCAG compliance test)HTML_HEADING_ABOVE_ROOT
output/searchform.html
warning
The html source is not well formed: Found "</a>" expecting "</img>" at line 34 column 177HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 79 column 10HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 80 column 9HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 109 column 8HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 111 column 12HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 112 column 20HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 113 column 16HTML_NOT_WELL_FORMED
output/searchform.html
warning
The html source is not well formed: Found "</div>" expecting "</body>" at line 115 column 12HTML_NOT_WELL_FORMED
1
warning
The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
2
warning
An HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide
3
warning
An HTML fragment from the set [dependency-table.xhtml, dependency-table-short.xhtml, dependency-table-nontech.xhtml] is not included anywhere in the produced implementation guide
4
warning
The HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide
The resource CodeSystem/trxhub-coverage-payor-role should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-coverage-type should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-medication-dispense-status-reason should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-medication-dispense-type should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-message-header-event should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-service-request-category should 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/ig-guidance/oids.html)
The resource CodeSystem/trxhub-service-request-code should 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/ig-guidance/oids.html)
Constraint failed: opd-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation (name.matches('[A-Z]([A-Za-z0-9_]){0,254}'))'http://hl7.org/fhir/StructureDefinition/OperationDefinition#opd-0
The resource OperationDefinition/trxhub-send-eprescription-custom could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
Constraint failed: opd-0: 'Name should be usable as an identifier for the module by machine processing applications such as code generation (name.matches('[A-Z]([A-Za-z0-9_]){0,254}'))'http://hl7.org/fhir/StructureDefinition/OperationDefinition#opd-0
The resource OperationDefinition/trxhub-service-request-update-status could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
This element does not match any known slice defined in the profile https://trxhub.mediservice.ch/fhir/StructureDefinition/trxhub-practitioner|0.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)Show Reasoning
This element does not match any known slice Defined in the profile https://trxhub.mediservice.ch/fhir/StructureDefinition/trxhub-practitioner|0.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
Practitioner.telecom[1]: discriminator = true and system.where(value = 'email').exists()
The resource StructureDefinition/trxhub-eprescription-document-reference could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
The resource StructureDefinition/trxhub-medication-substitution-preference could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
The resource StructureDefinition/trxhub-message-bundle could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
The resource StructureDefinition/trxhub-message-header could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html)
The resource ValueSet/trxhub-coverage-payor-role-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-coverage-status-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-coverage-type-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-medication-dispense-status-reason-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-medication-dispense-status-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-medication-dispense-type-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-message-header-event-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-patient-communication-languages-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-service-request-category-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-service-request-code-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-service-request-status-vs should 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/ig-guidance/oids.html)
The resource ValueSet/trxhub-service-request-update-status-vs should 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/ig-guidance/oids.html)
This element does not match any known slice defined in the profile https://trxhub.mediservice.ch/fhir/StructureDefinition/trxhub-practitioner|0.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'
The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk
trxhub.mediservice.ch
hl7.terminology.r4
