Profil: Arzt (Practitioner)
Fachlicher Kontext
Fordert eine Praxis / medizinische Einrichtung über das Praxisverwaltungssystem einen Vermittlungscode für eine Überweisung (Muster06) oder ein PTV11 an, so wird zum Zwecke der Nachverfolgbarkeit auch die Information gespeichert, welcher Arzt die Überweisung ausstellt, also den Vermittlungscode angefordert hat. Dazu werden folgende Daten des überweisenden Arztes benötigt:
- LANR
- Name
Dies ist v.a. dann sinnvoll, wenn der überweisende Arzt in einer Gemeinschaftspraxen oder größeren medizinischen Einrichtungen arbeitet, bei der verschiedene Ärzte angestellt sind. Hat der behandelnde Arzt (zu dem ein Patient überwiesen wurde) Rückfragen zu der Überweisung, weiß er dadurch direkt, welcher Arzt (und nicht nur welche Praxis / medizinische Einrichtung) die Überweisung ausgestellt hat.
FHIR-Profil
Name | KBV_PR_116117_TERMINSERVICE_VCA_Practitioner |
---|---|
Type | Practitioner |
Base Definition | https://fhir.kbv.de/StructureDefinition/KBV_PR_Base_Practitioner|1.6.0 (Version: 1.6.0) |
Canonical URL | https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner |
KBV_PR_116117_TERMINSERVICE_VCA_Practitioner (Practitioner) | I | KBV_PR_Base_Practitioner | |
id | Σ | 0..1 | string |
meta | Σ | 1..1 | Meta |
id | 0..1 | string | |
extension | I | 0..* | Extension |
versionId | Σ | 0..0 | id |
lastUpdated | Σ | 0..0 | instant |
source | Σ | 0..0 | uri |
profile | Σ | 1..* | canonical(StructureDefinition) |
kvdigitalProfil | Σ | 1..1 | canonical(StructureDefinition)Pattern |
security | Σ | 0..0 | CodingBinding |
tag | Σ | 0..0 | Coding |
implicitRules | Σ ?! | 0..0 | uri |
language | 0..0 | codeBinding | |
text | S | 0..1 | Narrative |
id | 0..1 | string | |
extension | I | 0..* | Extension |
status | S | 1..1 | codeBindingFixed Value |
div | S I | 1..1 | xhtml |
contained | 0..0 | Resource | |
extension | I | 0..0 | Extension |
modifierExtension | ?! I | 0..0 | Extension |
identifier | S Σ | 1..* | Identifier |
ANR | S Σ | 1..* | IdentifierLanr |
id | 0..1 | string | |
extension | I | 0..* | Extension |
use | Σ ?! | 0..0 | codeBindingFixed Value |
type | S Σ | 1..1 | CodeableConceptBindingPattern |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | S Σ | 1..1 | CodingPattern |
id | S | 0..1 | string |
extension | I | 0..* | Extension |
system | S Σ | 1..1 | uriFixed ValuePattern |
version | S Σ | 0..1 | string |
code | S Σ | 1..1 | codeFixed ValuePattern |
display | S Σ | 1..1 | stringPattern |
userSelected | Σ | 0..0 | boolean |
text | Σ | 0..0 | string |
system | Σ | 1..1 | uriFixed Value |
value | S Σ I | 1..1 | string |
period | Σ | 0..0 | Period |
assigner | Σ | 0..0 | Reference(Organization) |
EFN | Σ | 0..0 | IdentifierEfn |
ZANR | Σ | 0..0 | IdentifierZanr |
Telematik-ID | Σ | 0..0 | IdentifierTelematikId |
active | Σ | 0..0 | boolean |
name | S Σ | 1..1 | HumanName |
name | S Σ I | 1..1 | KBV_PR_Base_Datatype_Name |
id | 0..1 | string | |
extension | I | 0..* | Extension |
use | Σ ?! | 1..1 | codeBindingPattern |
text | Σ | 0..0 | string |
family | S Σ | 1..1 | string |
id | 0..1 | string | |
extension | I | 0..0 | Extension |
value | 0..1 | System.String | |
given | S Σ | 1..1 | string |
prefix | Σ | 0..0 | string |
suffix | Σ | 0..0 | string |
period | Σ | 0..0 | Period |
geburtsname | Σ I | 0..0 | KBV_PR_Base_Datatype_Maiden_Name |
telecom | Σ I | 0..0 | KBV_PR_Base_Datatype_Contactpoint |
address | Σ | 0..0 | Address |
gender | Σ | 0..0 | codeBinding |
birthDate | Σ | 0..0 | date |
photo | 0..0 | Attachment | |
qualification | 0..0 | BackboneElement | |
communication | 0..0 | CodeableConceptBinding |
Practitioner | |
Definition | Dieses Element beschreibt die behandelnde Person. Diese kann einen ärztlichen, aber auch nicht ärztlichen Hintergrund besitzen. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Practitioner.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
Practitioner.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. |
Cardinality | 1...1 |
Type | Meta |
Summary | True |
Invariants |
|
Practitioner.meta.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.meta.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.meta.versionId | |
Definition | The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. |
Cardinality | 0...0 |
Type | id |
Summary | True |
Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. |
Invariants |
|
Practitioner.meta.lastUpdated | |
Definition | When the resource last changed - e.g. when the version changed. |
Cardinality | 0...0 |
Type | instant |
Summary | True |
Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction. |
Invariants |
|
Practitioner.meta.source | |
Definition | A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. |
Cardinality | 0...0 |
Type | uri |
Summary | True |
Comments | In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL. |
Invariants |
|
Practitioner.meta.profile | |
Definition | A list of profiles (references to [StructureDefinition](structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](structuredefinition-definitions.html#StructureDefinition.url). |
Cardinality | 1...* |
Type | canonical(StructureDefinition) |
Summary | True |
Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. |
Slicing | Unordered, Open, by $this(Value) |
Invariants |
|
Practitioner.meta.profile:kvdigitalProfil | |
Definition | A list of profiles (references to [StructureDefinition](structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](structuredefinition-definitions.html#StructureDefinition.url). |
Cardinality | 1...1 |
Type | canonical(StructureDefinition) |
Summary | True |
Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. |
Invariants |
|
Pattern | https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner|1.1.0 |
Practitioner.meta.security | |
Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. |
Cardinality | 0...0 |
Type | Coding |
Binding | Security Labels from the Healthcare Privacy and Security Classification System. |
Summary | True |
Comments | The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Practitioner.meta.tag | |
Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. |
Cardinality | 0...0 |
Type | Coding |
Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". |
Summary | True |
Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. |
Invariants |
|
Practitioner.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Cardinality | 0...0 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
Practitioner.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...0 |
Type | code |
Binding | A human language. |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Invariants |
|
Practitioner.text | |
Definition | In diesem Element können die in der Instanz enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind. |
Cardinality | 0...1 |
Type | Narrative |
Must Support | True |
Alias | narrative, html, xhtml, display |
Comments | 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. |
Invariants |
|
Mappings |
|
Practitioner.text.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.text.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.text.status | |
Definition | The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. |
Cardinality | 1...1 |
Type | code |
Binding | The status of a resource narrative. |
Must Support | True |
Invariants |
|
Fixed Value | extensions |
Mappings |
|
Practitioner.text.div | |
Definition | The actual narrative content, a stripped down version of XHTML. |
Cardinality | 1...1 |
Type | xhtml |
Must Support | True |
Comments | The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. |
Invariants |
|
Mappings |
|
Practitioner.contained | |
Definition | 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. |
Cardinality | 0...0 |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
Practitioner.extension | |
Definition | 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. |
Cardinality | 0...0 |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.extension:ergaenzende_Angaben | |
Definition | In diesem Element können als Freitext ergänzende Angaben zur Person gemacht werden, wie beispielsweise Zusatzqualifikationen. |
Cardinality | 0...0 |
Type | Extension(string) |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Practitioner.modifierExtension | |
Definition | 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). |
Cardinality | 0...0 |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Practitioner.identifier | |
Definition | In diesem Element wird der Identifier (Identifikator) für diese behandelnde Person definiert. Der Identifikator kann aus diversen Quellen stammen. |
Cardinality | 1...* |
Type | Identifier |
Must Support | True |
Summary | True |
Requirements | Often, specific identities are assigned for the agent. |
Slicing | Unordered, Open, by type(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR | |
Definition | In diesem Element wird die Arztnummer (umgangssprachlich auch Lebenslange Arztnummer „LANR“ genannt) nach § 108 SGB V abgebildet. |
Cardinality | 1...* |
Type | IdentifierLanr |
Must Support | True |
Summary | True |
Requirements | Often, specific identities are assigned for the agent. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ANR.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...0 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Fixed Value | official |
Mappings |
|
Practitioner.identifier:ANR.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Must Support | True |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Pattern | { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "LANR" } ] } |
Mappings |
|
Practitioner.identifier:ANR.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ANR.type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Must Support | True |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Pattern | { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "LANR" } |
Mappings |
|
Practitioner.identifier:ANR.type.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Mappings |
|
Practitioner.identifier:ANR.type.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.type.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Must Support | True |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Fixed Value | http://terminology.hl7.org/CodeSystem/v2-0203 |
Mappings |
|
Practitioner.identifier:ANR.type.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.type.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Must Support | True |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Invariants |
|
Fixed Value | LANR |
Mappings |
|
Practitioner.identifier:ANR.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Pattern | Lifelong physician number |
Mappings |
|
Practitioner.identifier:ANR.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...0 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.type.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | https://fhir.kbv.de/NamingSystem/KBV_NS_Base_ANR |
Mappings |
|
Practitioner.identifier:ANR.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:ANR.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...0 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...0 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ANR.assigner.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | http://fhir.de/sid/arge-ik/iknr |
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.identifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ANR.assigner.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN | |
Definition | In diesem Element wird die einheitliche Fortbildungsnummer (EFN) abgebildet. |
Cardinality | 0...0 |
Type | IdentifierEfn |
Summary | True |
Requirements | Often, specific identities are assigned for the agent. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:EFN.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Fixed Value | official |
Mappings |
|
Practitioner.identifier:EFN.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Pattern | { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "DN" } ] } |
Mappings |
|
Practitioner.identifier:EFN.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:EFN.type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Pattern | { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "DN" } |
Mappings |
|
Practitioner.identifier:EFN.type.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:EFN.type.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.type.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Pattern | http://terminology.hl7.org/CodeSystem/v2-0203 |
Mappings |
|
Practitioner.identifier:EFN.type.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.type.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Invariants |
|
Pattern | DN |
Mappings |
|
Practitioner.identifier:EFN.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Pattern | Doctor number |
Mappings |
|
Practitioner.identifier:EFN.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.type.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | http://fhir.de/sid/bundesaerztekammer/efn |
Mappings |
|
Practitioner.identifier:EFN.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:EFN.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:EFN.assigner.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | http://fhir.de/sid/arge-ik/iknr |
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.identifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:EFN.assigner.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR | |
Definition | In diesem Element wird die Zahnarztnummer analog zur ANR abgebildet. |
Cardinality | 0...0 |
Type | IdentifierZanr |
Summary | True |
Requirements | Often, specific identities are assigned for the agent. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ZANR.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Fixed Value | official |
Mappings |
|
Practitioner.identifier:ZANR.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Pattern | { "coding": [ { "system": "http://fhir.de/CodeSystem/identifier-type-de-basis", "code": "ZANR" } ] } |
Mappings |
|
Practitioner.identifier:ZANR.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ZANR.type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Pattern | { "system": "http://fhir.de/CodeSystem/identifier-type-de-basis", "code": "ZANR" } |
Mappings |
|
Practitioner.identifier:ZANR.type.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ZANR.type.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.type.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Pattern | http://fhir.de/CodeSystem/identifier-type-de-basis |
Mappings |
|
Practitioner.identifier:ZANR.type.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.type.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Invariants |
|
Pattern | ZANR |
Mappings |
|
Practitioner.identifier:ZANR.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Pattern | Zahnarztnummer |
Mappings |
|
Practitioner.identifier:ZANR.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.type.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | http://fhir.de/sid/kzbv/zahnarztnummer |
Mappings |
|
Practitioner.identifier:ZANR.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:ZANR.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ZANR.assigner.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | http://fhir.de/sid/arge-ik/iknr |
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.identifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.identifier:ZANR.assigner.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID | |
Definition | Bei der Telematik-ID handelt es sich um eine eindeutige elektronische Identität von Leistungserbringenden und medizinischen Institutionen in der Telematik-Infrastruktur. |
Cardinality | 0...0 |
Type | IdentifierTelematikId |
Summary | True |
Requirements | Often, specific identities are assigned for the agent. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:Telematik-ID.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Pattern | { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "PRN" } ] } |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 1...1 |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. |
Invariants |
|
Pattern | { "system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "PRN" } |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. |
Invariants |
|
Pattern | http://terminology.hl7.org/CodeSystem/v2-0203 |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 1...1 |
Type | code |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Invariants |
|
Pattern | PRN |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Pattern | Provider number |
Mappings |
|
Practitioner.identifier:Telematik-ID.type.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.type.text | |
Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 1...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Fixed Value | https://gematik.de/fhir/sid/telematik-id |
Mappings |
|
Practitioner.identifier:Telematik-ID.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 1...1 |
Type | string |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
Practitioner.identifier:Telematik-ID.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.identifier:Telematik-ID.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
Practitioner.active | |
Definition | Whether this practitioner's record is in active use. |
Cardinality | 0...0 |
Type | boolean |
Summary | True |
Requirements | Need to be able to mark a practitioner record as not to be used because it was created in error. |
Comments | If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role. |
Invariants |
|
Mappings |
|
Practitioner.name | |
Definition | The name(s) associated with the practitioner. |
Cardinality | 1...1 |
Type | HumanName |
Must Support | True |
Summary | True |
Requirements | The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display. |
Comments | 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:
|
Slicing | Unordered, Open, by use(Value) |
Invariants |
|
Mappings |
|
Practitioner.name:name | |
Definition | Dieses Element beschreibt diverse Namensbestandteile einer Person. |
Cardinality | 1...1 |
Type | KBV_PR_Base_Datatype_Name |
Must Support | True |
Summary | True |
Requirements | The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display. |
Comments | Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. |
Invariants |
|
Mappings |
|
Practitioner.name:name.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.name:name.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.name:name.use | |
Definition | Identifies the purpose for this name. |
Cardinality | 1...1 |
Type | code |
Binding | The use of a human name. |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate name for a particular context of use to be selected from among a set of names. |
Comments | Applications can assume that a name is current unless it explicitly says that it is temporary or old. |
Invariants |
|
Pattern | official |
Mappings |
|
Practitioner.name:name.text | |
Definition | Vollständiger Name mit Vornamen und allen Vorsatzwörtern und Namenszusätzen. Der vollständige Name soll alle Namensteile in ihrer korrekten Reihenfolge abbilden. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Requirements | A renderable, unencoded form. |
Comments | Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part. |
Invariants |
|
Mappings |
|
Practitioner.name:name.family | |
Definition | Der vollständige Familienname, einschließlich aller Vorsatz- und Zusatzwörter, mit Leerzeichen getrennt. |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
Alias | surname |
Comments | Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures). |
Invariants |
|
Mappings |
|
Practitioner.name:name.family.id | |
Definition | unique id for the element within a resource (for internal references) |
Cardinality | 0...1 |
Type | string |
Practitioner.name:name.family.extension | |
Definition | 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. |
Cardinality | 0...0 |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Practitioner.name:name.family.extension:namenszusatz | |
Definition | Namenszusatz als Bestandteil das Nachnamens, wie in VSDM (Versichertenstammdatenmanagement, "eGK") definiert. Beispiele: Gräfin, Prinz oder Fürst |
Cardinality | 0...0 |
Type | Extension(string) |
Alias | extensions, user content |
Comments | Die Extension wurde erstellt aufgrund der Anforderung, die auf der eGK vorhandenen Patientenstammdaten in FHIR abbilden zu können. Auf der eGK werden die Namensbestandteile "Namenszusatz" und "Vorsatzwort" getrennt vom Nachnamen gespeichert. Anhand der Liste der zulässigen Namenszusätze ist deutlich erkennbar, dass es sich hierbei sinngemäß um Adelstitel handelt. Das Vorsatzwort kann durch die Core-Extension own-prefix (Canonical: http://hl7.org/fhir/StructureDefinition/humanname-own-prefix) abgebildet werden, für den Namenszusatz ergibt sich jedoch die Notwendikeit einer nationalen Extension, da in andern Ländern Adelstitel entweder gar nicht oder als reguläres Namenspräfix erfasst werden. |
Invariants |
|
Mappings |
|
Practitioner.name:name.family.extension:nachname | |
Definition | Nachname ohne Vor- und Zusätze. Dient z.B. der alphabetischen Einordnung des Namens. |
Cardinality | 0...0 |
Type | Extension(string) |
Alias | extensions, user content |
Comments | If the person's surname has legally changed to become (or incorporate) the surname of the person's partner or spouse, this is the person's surname immediately prior to such change. Often this is the person's "maiden name". |
Invariants |
|
Mappings |
|
Practitioner.name:name.family.extension:vorsatzwort | |
Definition | Vorsatzwort wie z.B.: von, van, zu Vgl. auch VSDM-Spezifikation der Gematik (Versichertenstammdatenmanagement, "eGK") |
Cardinality | 0...0 |
Type | Extension(string) |
Alias | extensions, user content |
Comments | An example of a voorvoegsel is the "van" in "Ludwig van Beethoven". Since the voorvoegsel doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component. |
Invariants |
|
Mappings |
|
Practitioner.name:name.family.value | |
Definition | The actual value |
Cardinality | 0...1 |
Type | System.String |
Practitioner.name:name.given | |
Definition | Vorname der Person |
Cardinality | 1...1 |
Type | string |
Must Support | True |
Summary | True |
Alias | first name, middle name |
Comments | If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first. |
Invariants |
|
Mappings |
|
Practitioner.name:name.prefix | |
Definition | Namensteile vor dem Vornamen, z.B. akademischer Titel. |
Cardinality | 0...0 |
Type | string |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.name:name.prefix.id | |
Definition | unique id for the element within a resource (for internal references) |
Cardinality | 0...1 |
Type | string |
Practitioner.name:name.prefix.extension | |
Definition | 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. |
Cardinality | 1...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Practitioner.name:name.prefix.extension:prefix-qualifier | |
Definition | Spezialisierung der Art des Präfixes, z.B. "AC" für Akademische Titel |
Cardinality | 1...1 |
Type | Extension(code) |
Alias | extensions, user content |
Comments | Used to indicate additional information about the name part and how it should be used. |
Invariants |
|
Mappings |
|
Practitioner.name:name.prefix.extension:prefix-qualifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.name:name.prefix.extension:prefix-qualifier.extension | |
Definition | An Extension |
Cardinality | 0...0 |
Type | Extension |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Practitioner.name:name.prefix.extension:prefix-qualifier.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier |
Mappings |
|
Practitioner.name:name.prefix.extension:prefix-qualifier.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/extensibility.html) for a list). |
Cardinality | 1...1 |
Type | code |
Binding | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. |
Slicing | Unordered, Open, by $this(Type) |
Invariants |
|
Mappings |
|
Practitioner.name:name.prefix.extension:prefix-qualifier.value[x]:valueCode | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/extensibility.html) for a list). |
Cardinality | 0...1 |
Type | code |
Binding | A set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. |
Invariants |
|
Fixed Value | AC |
Mappings |
|
Practitioner.name:name.prefix.value | |
Definition | The actual value |
Cardinality | 0...1 |
Type | System.String |
Practitioner.name:name.suffix | |
Definition | Namensteile nach dem Nachnamen |
Cardinality | 0...0 |
Type | string |
Summary | True |
Invariants |
|
Mappings |
|
Practitioner.name:name.period | |
Definition | Indicates the period of time when this name was valid for the named person. |
Cardinality | 0...0 |
Type | Period |
Summary | True |
Requirements | Allows names to be placed in historical context. |
Invariants |
|
Mappings |
|
Practitioner.name:geburtsname | |
Definition | Geburtsname mit in Deutschland üblichen Erweiterungen |
Cardinality | 0...0 |
Type | KBV_PR_Base_Datatype_Maiden_Name |
Summary | True |
Requirements | The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display. |
Comments | Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts may or may not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. |
Invariants |
|
Mappings |
|
Practitioner.telecom | |
Definition | Dieses Element beschreibt die vorhandenen Kontaktmöglichkeiten. |
Cardinality | 0...0 |
Type | KBV_PR_Base_Datatype_Contactpoint |
Summary | True |
Requirements | Need to know how to reach a practitioner independent to any roles the practitioner may have. |
Comments | Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific. |
Invariants |
|
Mappings |
|
Practitioner.address | |
Definition | 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. |
Cardinality | 0...0 |
Type | Address |
Summary | True |
Requirements | The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations. |
Comments | 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). |
Slicing | Unordered, Open, by type(Value) |
Invariants |
|
Mappings |
|
Practitioner.address.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.address.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...0 |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Practitioner.address.use | |
Definition | The purpose of this address. |
Cardinality | 0...1 |
Type | code |
Binding | The use of an address. |
Modifier | True |
Summary | True |
Requirements | Allows an appropriate address to be chosen from a list of many. |
Comments | Applications can assume that an address is current unless it explicitly says that it is temporary or old. |
Invariants |
|
Examples | General home |
Mappings |
|
Practitioner.address.type | |
Definition | Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. |
Cardinality | 0...1 |
Type | code |
Binding | The type of an address (physical / postal). |
Summary | True |
Comments | The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource). |
Invariants |
|
Examples | General both |
Mappings |
|
Practitioner.address.text | |
Definition | Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | A renderable, unencoded form. |
Comments | Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part. |
Invariants |
|
Examples | General 137 Nowhere Street, Erewhon 9132 |
Mappings |
|
Practitioner.address.line | |
Definition | This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. |
Cardinality | 0...* |
Type | string |
Summary | True |
Invariants |
|
Examples | General 137 Nowhere Street |
Mappings |
|
Practitioner.address.city | |
Definition | The name of the city, town, suburb, village or other community or delivery center. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Alias | Municpality |
Invariants |
|
Examples | General Erewhon |
Mappings |
|
Practitioner.address.district | |
Definition | The name of the administrative area (county). |
Cardinality | 0...1 |
Type | string |
Summary | True |
Alias | County |
Comments | District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead. |
Invariants |
|
Examples | General Madison |
Mappings |
|
Practitioner.address.state | |
Definition | Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes). |
Cardinality | 0...1 |
Type | string |
Summary | True |
Alias | Province, Territory |
Invariants |
|
Mappings |
|
Practitioner.address.postalCode | |
Definition | A postal code designating a region defined by the postal service. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Alias | Zip |
Invariants |
|
Examples | General 9132 |
Mappings |
|
Practitioner.address.country | |
Definition | Country - a nation as commonly understood or generally accepted. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | ISO 3166 3 letter codes can be used in place of a human readable country name. |
Invariants |
|
Mappings |
|
Practitioner.address.period | |
Definition | Time period when address was/is in use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Requirements | Allows addresses to be placed in historical context. |
Invariants |
|
Examples | General { "start": "2010-03-23", "end": "2010-07-01" } |
Mappings |
|
Practitioner.address:Strassenanschrift | |
Definition | Hier können Angaben zur Straßenanschrift gemacht werden. |
Cardinality | 0...0 |
Type | KBV_PR_Base_Datatype_Street_Address |
Summary | True |
Requirements | The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations. |
Comments | 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 resource). |
Invariants |
|
Examples | Beispiel für einfache Adresse { "use": "home", "type": "postal", "line": [ "Musterweg 42" ], "city": "Musterhausen", "postalCode": "99999" } |
Mappings |
|
Practitioner.address:Postfach | |
Definition | Eine Adresse gemäß postalischer Konventionen (im Gegensatz zu bspw. GPS-Koordinaten). Die Adresse kann sowohl zur Zustellung von Postsendungen oder zum Aufsuchen von Orten, die keine gültige Postadresse haben, verwendet werden. Die verwendeten Extensions in diesem Profil bilden die Struktur der Adresse ab, wie sie im VSDM-Format der elektronischen Versichertenkarte verwendet wird. Insbesondere bei ausländischenOrt Adresse oder Adressen, die nicht durch Einlesen einer elektronischen Versichertenkarte erfasst wurden, sind abweichende Strukturen möglich. Die Verwendung der Extensions ist nicht verpflichtend. |
Cardinality | 0...0 |
Type | KBV_PR_Base_Datatype_Post_Office_Box |
Summary | True |
Requirements | The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations. |
Comments | 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 resource). |
Invariants |
|
Examples | Beispiel für einfache Adresse { "use": "home", "type": "postal", "line": [ "Musterweg 42" ], "city": "Musterhausen", "postalCode": "99999" } |
Mappings |
|
Practitioner.gender | |
Definition | Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes. |
Cardinality | 0...0 |
Type | code |
Binding | The gender of a person used for administrative purposes. |
Summary | True |
Requirements | Needed to address the person correctly. |
Invariants |
|
Mappings |
|
Practitioner.gender.id | |
Definition | unique id for the element within a resource (for internal references) |
Cardinality | 0...1 |
Type | string |
Practitioner.gender.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Practitioner.gender.extension:other-amtlich | |
Definition | Optional Extension Element - found in all resources. |
Cardinality | 0...1 |
Type | Extension(Coding) |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Practitioner.gender.value | |
Definition | Primitive value for code |
Cardinality | 0...1 |
Type | System.String |
Practitioner.birthDate | |
Definition | The date of birth for the practitioner. |
Cardinality | 0...0 |
Type | date |
Summary | True |
Requirements | Needed for identification. |
Invariants |
|
Mappings |
|
Practitioner.photo | |
Definition | Image of the person. |
Cardinality | 0...0 |
Type | Attachment |
Requirements | Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too. |
Invariants |
|
Mappings |
|
Practitioner.qualification | |
Definition | The official certifications, training, and licenses that authorize or otherwise pertain to the provision of care by the practitioner. For example, a medical license issued by a medical board authorizing the practitioner to practice medicine within a certian locality. |
Cardinality | 0...0 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Practitioner.qualification.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Practitioner.qualification.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Practitioner.qualification.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants |
|
Mappings |
|
Practitioner.qualification.identifier | |
Definition | An identifier that applies to this person's qualification in this role. |
Cardinality | 0...* |
Type | Identifier |
Requirements | Often, specific identities are assigned for the qualification. |
Invariants |
|
Mappings |
|
Practitioner.qualification.code | |
Definition | Coded representation of the qualification. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Specific qualification the practitioner has to provide a service. |
Invariants |
|
Mappings |
|
Practitioner.qualification.period | |
Definition | Period during which the qualification is valid. |
Cardinality | 0...1 |
Type | Period |
Requirements | Qualifications are often for a limited period of time, and can be revoked. |
Invariants |
|
Mappings |
|
Practitioner.qualification.issuer | |
Definition | Organization that regulates and issues the qualification. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Invariants |
|
Mappings |
|
Practitioner.communication | |
Definition | A language the practitioner can use in patient communication. |
Cardinality | 0...0 |
Type | CodeableConcept |
Binding | A human language. |
Requirements | Knowing which language a practitioner speaks can help in facilitating communication with patients. |
Comments | 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. |
Invariants |
|
Mappings |
|
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="KBV-PR-116117-TERMINSERVICE-VCA-Practitioner" /> <text> <status value="generated" /> --- We have skipped the narrative for better readability of the resource --- </text> <url value="https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner" /> <version value="1.1.0" /> <name value="KBV_PR_116117_TERMINSERVICE_VCA_Practitioner" /> <title value="KBV_PR_116117_TERMINSERVICE_VCA_Practitioner" /> <status value="active" /> <publisher value="kv.digital GmbH" /> <contact> <name value="kv.digital GmbH" /> <telecom> <system value="url" /> <value value="https://www.kv.digital" /> </telecom> </contact> <description value="Name und LANR des überweisenden Arztes" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Practitioner" /> <baseDefinition value="https://fhir.kbv.de/StructureDefinition/KBV_PR_Base_Practitioner|1.6.0" /> <derivation value="constraint" /> <differential> <element id="Practitioner.meta"> <path value="Practitioner.meta" /> <min value="1" /> </element> <element id="Practitioner.meta.versionId"> <path value="Practitioner.meta.versionId" /> <max value="0" /> </element> <element id="Practitioner.meta.lastUpdated"> <path value="Practitioner.meta.lastUpdated" /> <max value="0" /> </element> <element id="Practitioner.meta.source"> <path value="Practitioner.meta.source" /> <max value="0" /> </element> <element id="Practitioner.meta.profile"> <path value="Practitioner.meta.profile" /> <slicing> <discriminator> <type value="value" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Practitioner.meta.profile:kvdigitalProfil"> <path value="Practitioner.meta.profile" /> <sliceName value="kvdigitalProfil" /> <min value="1" /> <max value="1" /> <patternCanonical value="https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner|1.1.0" /> </element> <element id="Practitioner.meta.security"> <path value="Practitioner.meta.security" /> <max value="0" /> </element> <element id="Practitioner.meta.tag"> <path value="Practitioner.meta.tag" /> <max value="0" /> </element> <element id="Practitioner.implicitRules"> <path value="Practitioner.implicitRules" /> <max value="0" /> </element> <element id="Practitioner.language"> <path value="Practitioner.language" /> <max value="0" /> </element> <element id="Practitioner.text"> <path value="Practitioner.text" /> <definition value="In diesem Element können die in der Instanz enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind." /> <mustSupport value="true" /> </element> <element id="Practitioner.text.status"> <path value="Practitioner.text.status" /> <fixedCode value="extensions" /> <mustSupport value="true" /> </element> <element id="Practitioner.text.div"> <path value="Practitioner.text.div" /> <mustSupport value="true" /> </element> <element id="Practitioner.contained"> <path value="Practitioner.contained" /> <max value="0" /> </element> <element id="Practitioner.extension"> <path value="Practitioner.extension" /> <max value="0" /> </element> <element id="Practitioner.extension:ergaenzende_Angaben"> <path value="Practitioner.extension" /> <sliceName value="ergaenzende_Angaben" /> <max value="0" /> </element> <element id="Practitioner.modifierExtension"> <path value="Practitioner.modifierExtension" /> <max value="0" /> </element> <element id="Practitioner.identifier"> <path value="Practitioner.identifier" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR"> <path value="Practitioner.identifier" /> <sliceName value="ANR" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.use"> <path value="Practitioner.identifier.use" /> <max value="0" /> </element> <element id="Practitioner.identifier:ANR.type"> <path value="Practitioner.identifier.type" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding"> <path value="Practitioner.identifier.type.coding" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.id"> <path value="Practitioner.identifier.type.coding.id" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.system"> <path value="Practitioner.identifier.type.coding.system" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.version"> <path value="Practitioner.identifier.type.coding.version" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.code"> <path value="Practitioner.identifier.type.coding.code" /> <fixedCode value="LANR" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.display"> <path value="Practitioner.identifier.type.coding.display" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.type.coding.userSelected"> <path value="Practitioner.identifier.type.coding.userSelected" /> <max value="0" /> </element> <element id="Practitioner.identifier:ANR.type.text"> <path value="Practitioner.identifier.type.text" /> <max value="0" /> </element> <element id="Practitioner.identifier:ANR.value"> <path value="Practitioner.identifier.value" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:ANR.period"> <path value="Practitioner.identifier.period" /> <max value="0" /> </element> <element id="Practitioner.identifier:ANR.assigner"> <path value="Practitioner.identifier.assigner" /> <max value="0" /> </element> <element id="Practitioner.identifier:EFN"> <path value="Practitioner.identifier" /> <sliceName value="EFN" /> <max value="0" /> </element> <element id="Practitioner.identifier:ZANR"> <path value="Practitioner.identifier" /> <sliceName value="ZANR" /> <max value="0" /> </element> <element id="Practitioner.identifier:Telematik-ID"> <path value="Practitioner.identifier" /> <sliceName value="Telematik-ID" /> <max value="0" /> </element> <element id="Practitioner.active"> <path value="Practitioner.active" /> <max value="0" /> </element> <element id="Practitioner.name"> <path value="Practitioner.name" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name:name"> <path value="Practitioner.name" /> <sliceName value="name" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name:name.text"> <path value="Practitioner.name.text" /> <max value="0" /> </element> <element id="Practitioner.name:name.family"> <path value="Practitioner.name.family" /> <maxLength value="80" /> <mustSupport value="true" /> </element> <element id="Practitioner.name:name.family.extension"> <path value="Practitioner.name.family.extension" /> <max value="0" /> </element> <element id="Practitioner.name:name.family.extension:namenszusatz"> <path value="Practitioner.name.family.extension" /> <sliceName value="namenszusatz" /> <max value="0" /> </element> <element id="Practitioner.name:name.family.extension:nachname"> <path value="Practitioner.name.family.extension" /> <sliceName value="nachname" /> <max value="0" /> </element> <element id="Practitioner.name:name.family.extension:vorsatzwort"> <path value="Practitioner.name.family.extension" /> <sliceName value="vorsatzwort" /> <max value="0" /> </element> <element id="Practitioner.name:name.given"> <path value="Practitioner.name.given" /> <min value="1" /> <maxLength value="80" /> <mustSupport value="true" /> </element> <element id="Practitioner.name:name.prefix"> <path value="Practitioner.name.prefix" /> <max value="0" /> </element> <element id="Practitioner.name:name.suffix"> <path value="Practitioner.name.suffix" /> <max value="0" /> </element> <element id="Practitioner.name:name.period"> <path value="Practitioner.name.period" /> <max value="0" /> </element> <element id="Practitioner.name:geburtsname"> <path value="Practitioner.name" /> <sliceName value="geburtsname" /> <max value="0" /> </element> <element id="Practitioner.telecom"> <path value="Practitioner.telecom" /> <max value="0" /> </element> <element id="Practitioner.address"> <path value="Practitioner.address" /> <max value="0" /> </element> <element id="Practitioner.address.extension"> <path value="Practitioner.address.extension" /> <max value="0" /> </element> <element id="Practitioner.address:Strassenanschrift"> <path value="Practitioner.address" /> <sliceName value="Strassenanschrift" /> <max value="0" /> </element> <element id="Practitioner.address:Postfach"> <path value="Practitioner.address" /> <sliceName value="Postfach" /> <max value="0" /> </element> <element id="Practitioner.gender"> <path value="Practitioner.gender" /> <max value="0" /> </element> <element id="Practitioner.birthDate"> <path value="Practitioner.birthDate" /> <max value="0" /> </element> <element id="Practitioner.photo"> <path value="Practitioner.photo" /> <max value="0" /> </element> <element id="Practitioner.qualification"> <path value="Practitioner.qualification" /> <max value="0" /> </element> <element id="Practitioner.communication"> <path value="Practitioner.communication" /> <max value="0" /> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "KBV-PR-116117-TERMINSERVICE-VCA-Practitioner", "text": { "status": "generated", --- We have skipped the narrative for better readability of the resource --- }, "url": "https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner", "version": "1.1.0", "name": "KBV_PR_116117_TERMINSERVICE_VCA_Practitioner", "title": "KBV_PR_116117_TERMINSERVICE_VCA_Practitioner", "status": "active", "publisher": "kv.digital GmbH", "contact": [ { "name": "kv.digital GmbH", "telecom": [ { "system": "url", "value": "https://www.kv.digital" } ] } ], "description": "Name und LANR des überweisenden Arztes", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Practitioner", "baseDefinition": "https://fhir.kbv.de/StructureDefinition/KBV_PR_Base_Practitioner|1.6.0", "derivation": "constraint", "differential": { "element": [ { "id": "Practitioner.meta", "path": "Practitioner.meta", "min": 1 }, { "id": "Practitioner.meta.versionId", "path": "Practitioner.meta.versionId", "max": "0" }, { "id": "Practitioner.meta.lastUpdated", "path": "Practitioner.meta.lastUpdated", "max": "0" }, { "id": "Practitioner.meta.source", "path": "Practitioner.meta.source", "max": "0" }, { "id": "Practitioner.meta.profile", "path": "Practitioner.meta.profile", "slicing": { "discriminator": [ { "type": "value", "path": "$this" } ], "rules": "open" }, "min": 1 }, { "id": "Practitioner.meta.profile:kvdigitalProfil", "path": "Practitioner.meta.profile", "sliceName": "kvdigitalProfil", "min": 1, "max": "1", "patternCanonical": "https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner|1.1.0" }, { "id": "Practitioner.meta.security", "path": "Practitioner.meta.security", "max": "0" }, { "id": "Practitioner.meta.tag", "path": "Practitioner.meta.tag", "max": "0" }, { "id": "Practitioner.implicitRules", "path": "Practitioner.implicitRules", "max": "0" }, { "id": "Practitioner.language", "path": "Practitioner.language", "max": "0" }, { "id": "Practitioner.text", "path": "Practitioner.text", "definition": "In diesem Element können die in der Instanz enthaltenen Informationen in einer menschenlesbaren Form zusammengefasst werden. Dabei ist zu beachten, dass keine Informationen aufgenommen werden dürfen, die nicht in strukturierter Form an anderer Stelle in der Instanz enthalten sind.", "mustSupport": true }, { "id": "Practitioner.text.status", "path": "Practitioner.text.status", "fixedCode": "extensions", "mustSupport": true }, { "id": "Practitioner.text.div", "path": "Practitioner.text.div", "mustSupport": true }, { "id": "Practitioner.contained", "path": "Practitioner.contained", "max": "0" }, { "id": "Practitioner.extension", "path": "Practitioner.extension", "max": "0" }, { "id": "Practitioner.extension:ergaenzende_Angaben", "path": "Practitioner.extension", "sliceName": "ergaenzende_Angaben", "max": "0" }, { "id": "Practitioner.modifierExtension", "path": "Practitioner.modifierExtension", "max": "0" }, { "id": "Practitioner.identifier", "path": "Practitioner.identifier", "min": 1, "mustSupport": true }, { "id": "Practitioner.identifier:ANR", "path": "Practitioner.identifier", "sliceName": "ANR", "min": 1, "mustSupport": true }, { "id": "Practitioner.identifier:ANR.use", "path": "Practitioner.identifier.use", "max": "0" }, { "id": "Practitioner.identifier:ANR.type", "path": "Practitioner.identifier.type", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding", "path": "Practitioner.identifier.type.coding", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.id", "path": "Practitioner.identifier.type.coding.id", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.system", "path": "Practitioner.identifier.type.coding.system", "fixedUri": "http://terminology.hl7.org/CodeSystem/v2-0203", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.version", "path": "Practitioner.identifier.type.coding.version", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.code", "path": "Practitioner.identifier.type.coding.code", "fixedCode": "LANR", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.display", "path": "Practitioner.identifier.type.coding.display", "min": 1, "mustSupport": true }, { "id": "Practitioner.identifier:ANR.type.coding.userSelected", "path": "Practitioner.identifier.type.coding.userSelected", "max": "0" }, { "id": "Practitioner.identifier:ANR.type.text", "path": "Practitioner.identifier.type.text", "max": "0" }, { "id": "Practitioner.identifier:ANR.value", "path": "Practitioner.identifier.value", "mustSupport": true }, { "id": "Practitioner.identifier:ANR.period", "path": "Practitioner.identifier.period", "max": "0" }, { "id": "Practitioner.identifier:ANR.assigner", "path": "Practitioner.identifier.assigner", "max": "0" }, { "id": "Practitioner.identifier:EFN", "path": "Practitioner.identifier", "sliceName": "EFN", "max": "0" }, { "id": "Practitioner.identifier:ZANR", "path": "Practitioner.identifier", "sliceName": "ZANR", "max": "0" }, { "id": "Practitioner.identifier:Telematik-ID", "path": "Practitioner.identifier", "sliceName": "Telematik-ID", "max": "0" }, { "id": "Practitioner.active", "path": "Practitioner.active", "max": "0" }, { "id": "Practitioner.name", "path": "Practitioner.name", "max": "1", "mustSupport": true }, { "id": "Practitioner.name:name", "path": "Practitioner.name", "sliceName": "name", "min": 1, "mustSupport": true }, { "id": "Practitioner.name:name.text", "path": "Practitioner.name.text", "max": "0" }, { "id": "Practitioner.name:name.family", "path": "Practitioner.name.family", "maxLength": 80, "mustSupport": true }, { "id": "Practitioner.name:name.family.extension", "path": "Practitioner.name.family.extension", "max": "0" }, { "id": "Practitioner.name:name.family.extension:namenszusatz", "path": "Practitioner.name.family.extension", "sliceName": "namenszusatz", "max": "0" }, { "id": "Practitioner.name:name.family.extension:nachname", "path": "Practitioner.name.family.extension", "sliceName": "nachname", "max": "0" }, { "id": "Practitioner.name:name.family.extension:vorsatzwort", "path": "Practitioner.name.family.extension", "sliceName": "vorsatzwort", "max": "0" }, { "id": "Practitioner.name:name.given", "path": "Practitioner.name.given", "min": 1, "maxLength": 80, "mustSupport": true }, { "id": "Practitioner.name:name.prefix", "path": "Practitioner.name.prefix", "max": "0" }, { "id": "Practitioner.name:name.suffix", "path": "Practitioner.name.suffix", "max": "0" }, { "id": "Practitioner.name:name.period", "path": "Practitioner.name.period", "max": "0" }, { "id": "Practitioner.name:geburtsname", "path": "Practitioner.name", "sliceName": "geburtsname", "max": "0" }, { "id": "Practitioner.telecom", "path": "Practitioner.telecom", "max": "0" }, { "id": "Practitioner.address", "path": "Practitioner.address", "max": "0" }, { "id": "Practitioner.address.extension", "path": "Practitioner.address.extension", "max": "0" }, { "id": "Practitioner.address:Strassenanschrift", "path": "Practitioner.address", "sliceName": "Strassenanschrift", "max": "0" }, { "id": "Practitioner.address:Postfach", "path": "Practitioner.address", "sliceName": "Postfach", "max": "0" }, { "id": "Practitioner.gender", "path": "Practitioner.gender", "max": "0" }, { "id": "Practitioner.birthDate", "path": "Practitioner.birthDate", "max": "0" }, { "id": "Practitioner.photo", "path": "Practitioner.photo", "max": "0" }, { "id": "Practitioner.qualification", "path": "Practitioner.qualification", "max": "0" }, { "id": "Practitioner.communication", "path": "Practitioner.communication", "max": "0" } ] } }
Anmerkungen
In der folgenden Tabelle finden sich Anmerkungen zu einzelnen Feldern.
Feld | Anmerkung |
---|---|
|
Die Schnittstelle akzeptiert alle Zeichen nach ISO/IEC 8859-15 (auch Latin-9 genannt) mit Ausnahme von:
|
Beispiele
Alle Beispiele sind hier im vorliegenden Projekt zu finden.
<Practitioner xmlns="http://hl7.org/fhir"> <id value="12df27c7-acdc-4467-b393-93416a1cc51x" /> <meta> <profile value="https://fhir.kbv.de/StructureDefinition/KBV_PR_116117_TERMINSERVICE_VCA_Practitioner|1.1.0" /> </meta> <text> <status value="extensions" /> --- We have skipped the narrative for better readability of the resource --- </text> <identifier> <type> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <code value="LANR" /> <display value="Lifelong physician number" /> </coding> </type> <system value="https://fhir.kbv.de/NamingSystem/KBV_NS_Base_ANR" /> <value value="123456789" /> </identifier> <name> <use value="official" /> <family value="Topp-Glücklich" /> <given value="Mini" /> </name> </Practitioner>