Profile Comparison between http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitioner vs https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitioner

Left:IPA-Practitioner (http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitioner)
Right:BePractitioner (https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitioner)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitioner' vs 'https://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitioner'
ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '2.1.2'
InformationStructureDefinition.nameValues for name differ: 'IPAPractitioner' vs 'BePractitioner'
InformationStructureDefinition.titleValues for title differ: 'IPA-Practitioner' vs 'BePractitioner'
InformationStructureDefinition.dateValues for date differ: '2022-08-02' vs '2024-08-30T17:14:57+02:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Patient Care Work Group' vs 'eHealth Platform'
InformationStructureDefinition.jurisdictionRemoved the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#BE'
InformationStructureDefinition.definitionValues for definition differ: 'An identifier that applies to this person in this role.' vs 'An identifier that applies to this person in this role. Typically, a NIHDI value and/or a SSIN value are given. Other systems remain allowed. Flows in organizations will most likely want to also include a local identifier, using its own system. A type can be added if needed. When it is given, a consumer SHALL NOT ignore it.'
WarningPractitioner.identifierElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.definitionValues for definition differ: 'Whether this practitioner's record is in active use.' vs 'Whether this practitioner's record is in active use. It is RECOMMENDED to keep the value ‘true’ as long as the practitioner is still being treated by the provider of the data.'
InformationStructureDefinition.definitionValues for definition differ: 'The name(s) associated with the practitioner.' vs 'The name(s) associated with the practitioner. Typically RECOMMENDED to include one familyname and at least one given name and to define this use as ‘official’.'
InformationStructureDefinition.commentValues for comment differ: 'In some contexts, the real name of the practitioner is obscured. However this is handled, the resource must include at least some useable name for the practitioner in the name.text element' vs 'The selection of the use property should ensure that there is a single usual name specified, and others use the nickname (alias), old, or other values as appropriate. In general, select the value to be used in the ResourceReference.display based on this: 1. There is more than 1 name 2. Use = usual 3. Period is current to the date of the usage 4. Use = official 5. Other order as decided by internal business rules.'
WarningPractitioner.nameElements differ in definition for mustSupport: 'true' vs 'false'
InformationStructureDefinition.definitionValues for definition differ: 'A contact detail for the practitioner, e.g. a telephone number or an email address.' vs 'A contact detail for the practitioner, e.g. a telephone number or an email address. It is RECOMMENDED to at least add one phone or email address.'
InformationStructureDefinition.shortValues for short differ: 'Address(es) of the practitioner that are not role specific (typically home address)' vs 'An address expressed using postal conventions (as opposed to GPS or other location definition formats)'
InformationStructureDefinition.definitionValues for definition differ: 'Address(es) of the practitioner that are not role specific (typically home address). Work addresses are not typically entered in this property as they are usually role dependent.' vs 'An address expressed using postal conventions (as opposed to GPS or other location definition formats). This data type may be used to convey addresses for use in delivering mail as well as for visiting locations which might not be valid for mail delivery. There are a variety of postal address formats defined around the world.'
InformationStructureDefinition.commentValues for comment differ: 'The PractitionerRole does not have an address value on it, as it is expected that the location property be used for this purpose (which has an address).' vs 'Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the [Location](location.html#) resource). Special remarks for KMEHR users: Note when .use and .type are used they SHALL use the FHIR defined valuesets as per their required binding level in the FHIR specification. In a KMEHR address, the use was defined by CD-ADDRESS but those values can be found in the FHIR valueset. KMEHR values 'careadress', 'other' and 'vacation' are not directly present in the FHIR address-use table but can be mapped to the value 'temp' in FHIR. In those cases, it is RECOMMENDED to also add a .period. In KMEHR, an address might be expressed using free text or a totally structured approach where the streetname and housenumber are put in separate fields. FHIR prefers a more pragmatic approach where the ‘text’ element is used to print on labels. Also, streetname and number are not separate fields as in KMEHR but in a structural approach are given as one or moren ‘line’ elements. It is however RECOMMENDED to use the Streetname, Housenumber and Postbox extensions to express them seperately. Note the FHIR address also allows to optionally define whether the address is a physical, postal or ‘both’ address using the .type field.'
InformationStructureDefinition.definitionValues for definition differ: 'A language the practitioner can use in patient communication.' vs 'A language the practitioner can use in patient communication. It is RECOMMENDED to include this when available'
InformationStructureDefinition.commentValues for comment differ: 'The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.' vs 'The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type. Special remarks for KMEHR users: The 'usuallanguage' element in a KMEHR message only refers to the use of W3C language codes. As such, the language codes as proposed in the FHIR standard should not present any interoperability issue. Note the KMEHR element implies it is the language usally used by the practitioner. As such, when this element from KMEHR would be mapped to a FHIR resource, the communication.preferred Boolean SHOULD be used.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Practitioner
      .copyrightUsed by permission of HL7 International all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International all rights reserved Creative Commons License'
      .date2022-08-022024-08-30T17:14:57+02:00
      • Values Differ
      .descriptionMinimum expectations for a Practitioner resource when accessed via a International Patient Access APIBelgian federal profile for a practitioner. Initially based on the functional description of the NIHDI.
      • Values Differ
      .experimentalfalse
      • Removed the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]http://unstats.un.org/unsd/methods/m49/m49.htm#001
          • Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001'
          ..jurisdiction[1]urn:iso:std:iso:3166#BE
          • Added the item 'urn:iso:std:iso:3166#BE'
          .kindresource
            .nameIPAPractitionerBePractitioner
            • Values Differ
            .publisherHL7 International - Patient Care Work GroupeHealth Platform
            • Values Differ
            .purpose
              .statusactive
                .titleIPA-PractitionerBePractitioner
                • Values Differ
                .typePractitioner
                  .urlhttp://hl7.org/fhir/uv/ipa/StructureDefinition/ipa-practitionerhttps://www.ehealth.fgov.be/standards/fhir/core/StructureDefinition/be-practitioner
                  • Values Differ
                  .version1.0.02.1.2
                  • Values Differ

                  Structure

                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                  .. Practitioner 0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
                  		0..*PractitionerA person with a formal responsibility in the provisioning of healthcare or related services
                    ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                      ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                        ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                          ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                            ... contained 0..*ResourceContained, inline Resources
                            		0..*ResourceContained, inline Resources
                              ... extension 0..*ExtensionAdditional content defined by implementations
                              		0..*ExtensionAdditional content defined by implementations
                                ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                		?!0..*ExtensionExtensions that cannot be ignored
                                  ... identifier Σ0..*IdentifierAn identifier for the person as this agent
                                  		SΣC0..*IdentifierAn identifier for the person as this agent
                                  Slice: Unordered, Open by value:system
                                  be-inv-NIHDI: NIHDI contains 11 or 8 (deprecated) digits without interpunction
                                  be-inv-SSIN: SINN contains 11 digits without interpunction
                                  be-inv-CBE: CBE contains 10 digits without interpunction, the first one is 0 or 1
                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                  ... active Σ0..1booleanWhether this practitioner's record is in active useΣ0..1booleanWhether this practitioner's record is in active use
                                    ... name SΣC1..*HumanNameThe name(s) associated with the practitioner
                                    ipa-pract-1: To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present.
                                    		Σ1..*HumanNameThe name(s) associated with the practitioner
                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                    ... telecom Σ0..*ContactPointA contact detail for the practitioner (that apply to all roles)
                                    		Σ0..*ContactPointA contact detail for the practitioner (that apply to all roles)
                                      ... address Σ0..*AddressAddress(es) of the practitioner that are not role specific (typically home address)
                                      		0..*??An address expressed using postal conventions (as opposed to GPS or other location definition formats)
                                        ... gender Σ0..1codemale | female | other | unknown
                                        Binding: ?? (required): The gender of a person used for administrative purposes.

                                        		Σ0..1codemale | female | other | unknown
                                        Binding: ?? (required): The gender of a person used for administrative purposes.

                                          ... birthDate Σ0..1dateThe date on which the practitioner was bornΣ0..1dateThe date on which the practitioner was born
                                            ... photo 0..*AttachmentImage of the person
                                            		0..*AttachmentImage of the person
                                              ... qualification 0..*BackboneElementCertification, licenses, or training pertaining to the provision of care
                                              		0..*BackboneElementCertification, licenses, or training pertaining to the provision of care
                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                  		0..*ExtensionAdditional content defined by implementations
                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                    		?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                      .... identifier 0..*IdentifierAn identifier for this qualification for the practitioner
                                                      		0..*IdentifierAn identifier for this qualification for the practitioner
                                                        .... code 1..1CodeableConceptCoded representation of the qualification
                                                        Binding: ?? (example): Specific qualification the practitioner has to provide a service.

                                                        		1..1CodeableConceptCoded representation of the qualification
                                                        Binding: ?? (example): Specific qualification the practitioner has to provide a service.

                                                          .... period 0..1PeriodPeriod during which the qualification is valid0..1PeriodPeriod during which the qualification is valid
                                                            .... issuer 0..1Reference(Organization)Organization that regulates and issues the qualification0..1Reference(Organization)Organization that regulates and issues the qualification
                                                              ... communication 0..*CodeableConceptA language the practitioner can use in patient communication
                                                              Binding: ?? (preferred): A human language.

                                                              Additional BindingsPurpose
                                                              ??Max Binding

                                                              		0..*CodeableConceptA language the practitioner can use in patient communication
                                                              Binding: ?? (preferred): A human language.

                                                              Additional BindingsPurpose
                                                              ??Max Binding


                                                                doco Documentation for this format