CodeSystems are now encouraged to have OIDS to enable CDA use. These don't apply as these are examples
The resource CodeSystem/ExampleCodeSystem should have an OID assigned to cater for possible use with OID based terminology systems% (1 uses)
The resource CodeSystem/ExampleCodeSystem2 should have an OID assigned to cater for possible use with OID based terminology systems% (1 uses)
The resource ConceptMap/example-conceptmap could usefully have an OID assigned% (1 uses)
The resource ValueSet/Example2ValueSet should have an OID assigned to cater for possible use with OID based terminology systems% (1 uses)
The resource ValueSet/ExampleValueSet should have an OID assigned to cater for possible use with OID based terminology systems% (1 uses)
IHE valueset that is not yet a real valueset
A definition for CodeSystem 'urn:ihe:event-type-code' could not be found, so the code cannot be validated (31 uses)
No definition could be found for URL value 'urn:ihe:event-type-code' (0 uses)
Keep until new BALP is released
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) (10 uses)
this is a profile that should be ported to BasicAudit, so has no example here
WARNING: StructureDefinition.where(url = 'https://profiles.ihe.net/ITI/SVCM/StructureDefinition/IHE.SVCM.Audit.Operation'): The Implementation Guide contains no examples for this profile (1 uses)
ihe.iti.svcm
hl7.fhir.uv.tools.r4