FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
Query
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
API
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
Tools
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
Organization Kassenärztliche Bundesvereinigung (KBV) /
Project KBV-Basis-Profile
KBV_PR_Base_CareTeam
Dieses Profil bildet ein Versorgungsteam ab.
- type Profile on CareTeam
- FHIR R4
- status Active
-
version1.7.0
Valid canonical
This resource matches a canonical claim from this project.
Claim: https://fhir.kbv.de/
Canonical claims are used to verify ownership of your canonical URLs.
Canonical
| KBV_PR_Base_CareTeam (CareTeam) | I | CareTeam | Element idCareTeam Planned participants in the coordination and delivery of care for a patient or group DefinitionHier werden behandelnde Personen und nicht behandelnde Kontaktpersonen als Versorgungsteam des/der PatientIn erfasst.
| |
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idCareTeam.meta Metadata about the resource DefinitionThe 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.
|
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idCareTeam.implicitRules A set of rules under which this content was created DefinitionA 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. 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.
|
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idCareTeam.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idCareTeam.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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.
| |
| contained | 0..* | Resource | There are no (further) constraints on this element Element idCareTeam.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
| modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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.
|
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idCareTeam.identifier External Ids for this team DefinitionBusiness identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server. Allows identification of the care team as it is known by various participating systems and in a way that remains consistent across servers. This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
|
| status | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idCareTeam.status proposed | active | suspended | inactive | entered-in-error DefinitionIndicates the current state of the care team. This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid. Indicates the status of the care team.
|
| category | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCareTeam.category Type of team DefinitionIdentifies what kind of team. This is to support differentiation between multiple co-existing teams, such as care plan team, episode of care team, longitudinal care team. Used for filtering what teams(s) are retrieved and displayed to different types of users. There may be multiple axis of categorization and one team may serve multiple purposes. Indicates the type of care team.
|
| name | Σ | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.name Name of the team, such as crisis assessment team DefinitionA label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams. The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.).
|
| subject | Σ | 1..1 | Reference(Patient | Group | KBV_PR_Base_Patient) | Element idCareTeam.subject Who care team is for Alternate namespatient DefinitionReferenziert den Patienten oder die Gruppe, deren beabsichtigte Pflege vom Team übernommen wird. Allows the team to care for a group (e.g. marriage) therapy. Allows for an organization to designate a team such as the PICC line team. Reference(Patient | Group | KBV_PR_Base_Patient) Constraints
|
| encounter | Σ | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idCareTeam.encounter Encounter created as part of DefinitionThe Encounter during which this CareTeam was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.
|
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idCareTeam.period Time period team covers DefinitionIndicates when the team did (or is intended to) come into effect and end. Allows tracking what team(s) are in effect at a particular time.
|
| participant | I | 1..* | BackboneElement | Element idCareTeam.participant Members of the team DefinitionHier wird eine Person als Teil des Versorgungsteams eines/einer PatientIn erfasst.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.participant.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
| modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.participant.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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.
|
| role | Σ | 0..* | CodeableConcept | Element idCareTeam.participant.role Type of involvement DefinitionHier wird die Rolle angegeben, die die Person in Bezug auf die Versorgung des/der PatientIn einnimmt. Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.participant.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| coding | Σ | 0..* | Coding | Element idCareTeam.participant.role.coding Code defined by a terminology system DefinitionHier wird die Rolle in Bezug auf den/die Patienten/Patientin anhand von Codes angegeben. Allows for alternative encodings within a code system, and translations to other code systems. 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. Unordered, Open, by $this(Value) Constraints
|
| rollePatientenbezug | Σ | 0..1 | CodingBinding | Element idCareTeam.participant.role.coding:rollePatientenbezug Code defined by a terminology system DefinitionHier wird die Rolle in Bezug auf den/die Patientin anhand einer vorgegebenen Werteliste angegeben. Allows for alternative encodings within a code system, and translations to other code systems. 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. KBV_VS_Base_Role_Care_Team (required) Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. 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.
|
| version | Σ | 1..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.version Version of the system - if relevant DefinitionThe 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. 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.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.code Symbol in syntax defined by the system DefinitionA 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). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idCareTeam.participant.role.coding:rollePatientenbezug.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). 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. 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.
|
| text | Σ | 0..1 | string | Element idCareTeam.participant.role.text Plain text representation of the concept DefinitionHier wird die Rolle in Bezug auf den/die Patient:in als Freitext angegeben. 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. Very often the text is the same as a displayName of one of the codings.
|
| member | Σ | 1..1 | Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | KBV_PR_Base_Practitioner | KBV_PR_Base_PractitionerRole | KBV_PR_Base_RelatedPerson | KBV_PR_Base_Patient | KBV_PR_Base_Organization | KBV_PR_Base_CareTeam) | Element idCareTeam.participant.member Who is involved DefinitionHier wird das Mitglied des Versorgungsteams referenziert. Patient only needs to be listed if they have a role other than "subject of care". Member is optional because some participants may be known only by their role, particularly in draft plans. Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Organization | CareTeam | KBV_PR_Base_Practitioner | KBV_PR_Base_PractitionerRole | KBV_PR_Base_RelatedPerson | KBV_PR_Base_Patient | KBV_PR_Base_Organization | KBV_PR_Base_CareTeam) Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.member.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | I | 0..* | Extension | There are no (further) constraints on this element Element idCareTeam.participant.member.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
| reference | Σ I | 1..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.member.reference Literal reference, Relative, internal or absolute URL DefinitionA 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. 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.
|
| type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element idCareTeam.participant.member.type Type the reference refers to (e.g. "Patient") DefinitionThe 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). 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. Aa resource (or, for logical models, the URI of the logical model).
|
| identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idCareTeam.participant.member.identifier Logical reference, when literal reference is not known DefinitionAn 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. 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).
|
| display | Σ | 0..1 | string | There are no (further) constraints on this element Element idCareTeam.participant.member.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. 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.
|
| onBehalfOf | Σ | 0..1 | Reference(Organization | KBV_PR_Base_Organization) | Element idCareTeam.participant.onBehalfOf Organization of the practitioner DefinitionThe organization of the practitioner. Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of. Reference(Organization | KBV_PR_Base_Organization) Constraints
|
| period | 0..1 | Period | There are no (further) constraints on this element Element idCareTeam.participant.period Time period of participant DefinitionIndicates when the specific member or organization did (or is intended to) come into effect and end.
| |
| reasonCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idCareTeam.reasonCode Why the care team exists DefinitionDescribes why the care team exists. Indicates the reason for the care team.
| |
| reasonReference | 0..* | Reference(Condition) | There are no (further) constraints on this element Element idCareTeam.reasonReference Why the care team exists DefinitionCondition(s) that this care team addresses.
| |
| managingOrganization | Σ | 0..* | Reference(Organization | KBV_PR_Base_Organization) | Element idCareTeam.managingOrganization Organization responsible for the care team DefinitionThe organization responsible for the care team. Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan. Reference(Organization | KBV_PR_Base_Organization) Constraints
|
| telecom | I | 0..* | KBV_PR_Base_Datatype_Contactpoint | Element idCareTeam.telecom Details of a Technology mediated contact point (phone, fax, email, etc.) DefinitionDieses Element beschreibt die vorhandenen Kontaktmöglichkeiten. The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members. KBV_PR_Base_Datatype_Contactpoint Constraints
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idCareTeam.note Comments made about the CareTeam DefinitionComments made about the CareTeam.
|
Documentation:
https://simplifier.net/base1x0/kbv_pr_base_careteam
Last updated on