Unable to compare with previous version: Unable to find version history at https://www.medizininformatik-initiative.de/fhir/ext/mii-interface-module-pseudonymization (Problem #1 with package-list.json at https://www.medizininformatik-initiative.de/fhir/ext/mii-interface-module-pseudonymization: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Unable to find ImplementationGuide.definition.resource.description for the resource Parameters/0ee863aa-1fe7-4d5f-6666-8f5edc7981d9. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
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 parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/anonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
Profile reference 'https://fhir.example.com/StructureDefinition/anonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/de-pseudonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/de-pseudonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
--
Bundle.meta.profile[0] (l1/c2)
warning
Profile reference 'https://fhir.example.com/StructureDefinition/delete-pseudonym-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
Profile reference 'https://fhir.example.com/StructureDefinition/delete-pseudonym-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
--
Bundle.meta.profile[0] (l1/c2)
warning
Profile reference 'https://fhir.example.com/StructureDefinition/get-pseudonym-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/get-pseudonym-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-multiple-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-multiple-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profilesVALIDATION_VAL_PROFILE_UNKNOWN_NOT_POLICY
A definition could not be found for Canonical URL 'http://fhir.org/packages/de.basisprofil.r4/ImplementationGuide/de.basisprofil.r4'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_RESOLVE
The canonical URL http://fhir.org/packages/de.basisprofil.r4/ImplementationGuide/de.basisprofil.r4 doesn't point to an actual ImplementationGuide resourceIG_DEPENDENCY_INVALID_URL
--
Resource
information
The resource ImplementationGuide/PseudonymizationIG 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)
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/AnonymizeOriginal 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)
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/DePseudonymize 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)
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/DeletePseudonym 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)
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/GetPseudonym 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 OperationDefinition/Pseudonymize 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)
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/PseudonymizeMultiple 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 parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correctPARAMETERS_STD_WRONG_TYPE
The canonical URL http://fhir.org/packages/de.basisprofil.r4/ImplementationGuide/de.basisprofil.r4 doesn't point to an actual ImplementationGuide resource
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
The parameter 'context' has the same name as a parameter for at least one operation in the core specification. In the base specification, the parameter has a type of uri, but this parameter instead has a value of type Identifier. Check that this is correct
Profile reference 'https://fhir.example.com/StructureDefinition/anonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/anonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/de-pseudonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/de-pseudonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/delete-pseudonym-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/delete-pseudonym-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/get-pseudonym-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/get-pseudonym-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-multiple-batch-request' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
Profile reference 'https://fhir.example.com/StructureDefinition/pseudonymize-multiple-batch-response' has not been checked because it could not be found, and the validator is set to not fetch unknown profiles
PseudonymizationIG
hl7.terminology.r4
