| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/uv/ips/StructureDefinition/PractitionerRole-uv-ips' vs 'http://hl7.eu/fhir/base-r5/StructureDefinition/practitionerRole-eu' |
| Error | StructureDefinition.version | Values for version differ: '2.0.0' vs '2.0.0-ballot' |
| Information | StructureDefinition.name | Values for name differ: 'PractitionerRoleUvIps' vs 'PractitionerRoleEu' |
| Information | StructureDefinition.title | Values for title differ: 'PractitionerRole (IPS)' vs 'PractitionerRole (EU base)' |
| Information | StructureDefinition.date | Values for date differ: '2024-06-19T10:50:07-05:00' vs '2025-12-22T08:19:43+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Patient Care' vs 'HL7 Europe' |
| Information | StructureDefinition.jurisdiction | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001' |
| Information | StructureDefinition.jurisdiction | Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '5.0.0' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'Business Identifiers that are specific to a role/location' vs 'Business identifier' |
| Information | StructureDefinition.definition | Values for definition differ: 'Whether this practitioner role record is in active use.' vs ' Whether this practitioner role record is in active use. Some systems may use this property to mark non-active practitioners, such as those that are not currently employed.' |
| Information | StructureDefinition.short | Values for short differ: 'Practitioner that is able to provide the defined services for the organization' vs 'The practitioner providing services for the organization' |
| Information | StructureDefinition.short | Values for short differ: 'Organization where the roles are available' vs 'The organization where the practitioner performs the role' |
| Warning | PractitionerRole.organization | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Roles which this practitioner may perform' vs 'Roles which this practitioner may perform.' |
| Information | PractitionerRole.code | Example/preferred bindings differ at PractitionerRole.code using binding from PractitionerRoleUvIps |
| Information | StructureDefinition.short | Values for short differ: 'Specific specialty of the practitioner' vs 'Specialty of the practitioner' |
| Information | StructureDefinition.definition | Values for definition differ: 'Specific specialty of the practitioner.' vs 'The specialty of a practitioner that describes the functional role they are practicing at a given organization or location.' |
| Information | PractitionerRole.specialty | Example/preferred bindings differ at PractitionerRole.specialty using binding from PractitionerRoleUvIps |
| Information | StructureDefinition.short | Values for short differ: 'The list of healthcare services that this worker provides for this role's Organization/Location(s)' vs 'Healthcare services provided for this role's Organization/Location(s)' |
| Information | StructureDefinition.short | Values for short differ: 'Technical endpoints providing access to services operated for the practitioner with this role' vs 'Endpoints for interacting with the practitioner in this role' |
| Information | StructureDefinition.definition | Values for definition differ: 'Technical endpoints providing access to services operated for the practitioner with this role.' vs ' Technical endpoints providing access to services operated for the practitioner with this role. Commonly used for locating scheduling services, or identifying where to send referrals electronically.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Organizations have multiple systems that provide various services and ,ay also be different for practitioners too.
So the endpoint satisfies the need to be able to define the technical connection details for how to connect to them, and for what purpose.' vs 'Organizations have multiple systems that provide various services and may also be different for practitioners too.
So the endpoint satisfies the need to be able to define the technical connection details for how to connect to them, and for what purpose.' |
abstract
jurisdiction[0]
jurisdiction[1]
PractitionerRole
extension
modifierExtension