Genererad berättande text: StructureDefinition RIVManagingTeam-careteam Namn Flaggor Kard. Typ Beskrivning & begränsningar<img src="[binary]" alt="doco" style="background-color: inherit"/> CareTeam 0..* CareTeam Planned participants in the coordination and delivery of care #xD; identifier S 0..* Identifier Identifierare för team #xD; category S 1..1 CodeableConcept Kategori av CareTeam Obligatoriskt mönster: Minst följande #xD; coding 1..1 Coding Code defined by a terminology system Fast värde: (Komplex) #xD; system 1..1 uri Identity of the terminology system Fast värde: http://example.org/fhir/fasta-kontakter/CodeSystem/typ-av-careteam-cs #xD; code 1..1 code Symbol in syntax defined by the system Fast värde: team #xD; name S 0..1 string Teamets namn #xD; subject S 0..1 Reference(Patient) Invånare som teamet gäller för #xD; period S 0..1 Period Time period team covers #xD; start S 0..1 dateTime Startdatum #xD; end S 0..1 dateTime Slutdatum #xD; participant S 0..* BackboneElement Deltagare i teamet #xD; member S 0..1 Reference(PractitionerRole | Practitioner) Teamdeltagare #xD; telecom S 0..* ContactPoint Kontaktuppgifter till teamet #xD; Skivor för extension Innehåll/regler för alla skivor #xD; extension:availability S 0..1 (Komplex) Tillgänglighet för kontaktväg URL: http://example.org/fhir/fasta-kontakter/StructureDefinition/RIVContactPointAvailability #xD; value[x] #xD; availableTime #xD; daysOfWeek 1..* code Veckodag #xD; availableStartTime 0..1 time Starttid #xD; availableEndTime 0..1 time Sluttid #xD; system S 0..1 code phone | fax | email | pager | url | sms | other #xD; value S 0..1 string The actual contact point details #xD; note S 0..* Annotation Kommentar #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Dokumentation för detta format
Profil som beskriver ett vård- eller omsorgsteam i svensk vård och omsorg. Ett team kan vara kopplat till en invånare och kan ha egna kontaktuppgifter. Teamet kan också utgöra kontaktväg eller organisatoriskt sammanhang för en fast kontakt.
Mappning mellan informationsmodell och Team
Mappning mellan informationsmodellen för fasta kontakter och FHIR-profilen RIVManagingTeam.
Planned participants in the coordination and delivery of care
The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
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.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The 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).
Text summary of the resource, for human interpretation
A 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 a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
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.
Must have either extensions or value[x], not both
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Identifierare som kan användas för att identifiera teamet.
This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R5/resource.html#identifiers)). 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.
Allows identification of the care team as it is known by various participating systems and in a way that remains consistent across servers.
proposed | active | suspended | inactive | entered-in-error
Indicates 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.
This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Participant.active {map: active = true; :default = false}
There may be multiple axis of categorization and one team may serve multiple purposes.
Used for filtering what teams(s) are retrieved and displayed to different types of users.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
A reference to a code defined by a terminology system.
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.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
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.
Very often the text is the same as a displayName of one of the codings.
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.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Namn på det vård- eller omsorgsteam som beskrivs.
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.).
Invånare som teamet gäller för. Kan utelämnas om teamet inte är direkt kopplat till en specifik invånare.
Use Group for care provision to all members of the group (e.g. group therapy). Use Patient for care provision to an individual patient.
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.
Invånaren som teamet gäller för. Själva person-id:t finns på den refererade Patient-resursen, i Patient.identifier.
Indicates 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.
Det datum då teamet börjar gälla i det aktuella sammanhanget.
If the low element is missing, the meaning is that the low boundary is not known.
Det datum då teamet upphör att gälla i det aktuella sammanhanget.
The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
If the end of the period is missing, it means that the period is ongoing
Aktörer som ingår i eller representerar teamet. Deltagare kan exempelvis vara vård- och omsorgspersonal, roll/funktion eller annan relevant aktör.
CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner
onBehalfOf.exists() implies (member.resolve() is Practitioner)
CareTeam.participant.role or CareTeam.participant.member exists
REL (REL.4 is always the Patient) ( or PRT?)
Extensions that cannot be ignored even if unrecognized
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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. 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 are expected to modify the meaning or interpretation of the element that contains them
Indicates specific responsibility of an individual within the care team, such as "Primary care physician", "Trained social worker counselor", "Caregiver", etc.
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. If a participant has multiple roles within the team, then there should be multiple participants.
Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
Aktör som ingår i teamet, exempelvis en person i roll eller en person.
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.
Teamdeltagare kan representeras som PractitionerRole eller Practitioner. Personalens identifierare finns på Practitioner.identifier, direkt eller via PractitionerRole.practitioner.
REL.5 (or PRT-5 : ( PRV-4 {provider participations} ) / PRT-5 : ( PRV-4 {non-provider person participations} ) / PRT-5 : ( PRV-4 = (patient non-subject of care) ) / PRT-8?)
Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.
When the member is generally available within this care team
When the member is generally available within this care team.
This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule.
To manage members who share the same role, but with different timing. For example, two physical therapists where one is available Monday through Friday whereas the other is available on the weekend.
Organization responsible for the care team
The organization responsible for the care team.
Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.
Kontaktuppgifter som ska användas av invånaren för att nå teamet. Kontaktuppgifterna kan även användas när en fast kontakt nås via detta team.
The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.
Anger under vilka tider och veckodagar kontaktvägen är tillgänglig.
Source of the definition for the extension code - a logical name or a URL.
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.
Anger under vilka veckodagar och tider kontaktvägen är tillgänglig.
Anger återkommande veckodagar och tider då kontaktvägen är tillgänglig.
A collection of times that the {item} is available.
Cannot include start/end times when selecting all day availability.
allDay.exists().not() or (allDay implies availableStartTime.exists().not() and availableEndTime.exists().not())
Veckodag då kontaktvägen är tillgänglig.
Indicates which days of the week are available between the start and end Times.
The purpose for which an extended contact detail should be used.
Is this always available? (hence times are irrelevant) i.e. 24 hour service.
The timezone is expected to be specified or implied by the context this datatype is used.
The opening time of day. Note: If the AllDay flag is set, then this time is ignored.
The closing time of day. Note: If the AllDay flag is set, then this time is ignored.
Not available during this time due to provided reason
Not available during this time due to provided reason.
The {item} is not available during this period of time due to the provided reason.
Reason presented to the user explaining why time not available
Reason presented to the user explaining why time not available.
The reason will generally be provided to give the textual reason for displaying when the {item} is not available, e.g. 'Closed public holidays' or 'Independence Day'. In cases such as this, the `during` might not be included and local knowledge would be required in such cases (as don't desire to keep updating when the holiday occurs each year). e.g.2: 'Closed for maintenance over the summer' for this example you would want to include the `during` period, unless this was a university hospital and the "summer" period was well known, but would recommend its inclusion anyway.
The reason that can be presented to the user as to why this time is not available.
Service not available during this period
Service not available during this period.
The {item} is not available (seasonally or for a public holiday) during this period.
phone | fax | email | pager | url | sms | other
Telecommunications form for contact point - what communications system is required to make use of the contact.
Telecommunications form for contact point.
Typ av kontaktväg, exempelvis telefon, e-post eller webbadress.
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value.
Need to support legacy numbers that are not in a tightly controlled format.
Värdet för kontaktvägen, exempelvis telefonnummer, e-postadress eller URL.
home | work | temp | old | mobile - purpose of this contact point
Identifies the purpose for the contact point.
Applications can assume that a contact is current unless it explicitly says that it is temporary or old.
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one
Specify preferred order of use (1 = highest)
Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values.
Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Ranks need not be unique. E.g. it's possible to have multiple contacts with rank=1. If the ranks have different systems or uses, this would be interpreted to mean "X is my most preferred phone number, Y is my most preferred email address" or "X is my preferred home email and Y is my preferred work email". If the system and use for equally-ranked contacts are the same, then the level of preference is equivalent for both repetitions. Ranks need not be sequential and not all repetitions must have a rank. For example, it's possible to have 4 contacts with ranks of 2, 5 and two with no rank specified. That would be interpreted to mean the first is preferred over the second and no preference stated for the remaining contacts.
Time period when the contact point was/is in use
Time period when the contact point was/is in use.
Kommentar eller kompletterande information om teamet.
Personalens namn finns på Practitioner.name, direkt eller via PractitionerRole.practitioner.
Personalens befattning kan uttryckas på PractitionerRole.code när deltagaren representeras via PractitionerRole.