RLCareTeamEquipe
Descrizione
Il profilo RLCareTeamEquipe è stato strutturato a partire dalla risorsa generica FHIR CareTeam con il fine di definire la composizione di un’equipe di professionisti sanitari. L’equipe può ricoprire il ruolo di case manager di un progetto individuale di un assistito.
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: RLCareTeamEquipe.
Snapshot View
CareTeam | I | CareTeam | There are no (further) constraints on this element Element IdCareTeam Planned participants in the coordination and delivery of care for a patient or group DefinitionThe Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.
| |
id | Σ | 1..1 | System.String | Element IdCareTeam.id UUID prodotto dal server FHIR (applicativo) che detiente la risorsa 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. System.String |
meta | Σ | 1..1 | Meta | Element IdCareTeam.meta Metadati della risorsa 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.
|
versionId | Σ | 1..1 | id | Element IdCareTeam.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. 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.
|
lastUpdated | Σ | 1..1 | instant | Element IdCareTeam.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz 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.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdCareTeam.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance 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. 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.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element IdCareTeam.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. 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. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element IdCareTeam.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. 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. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdCareTeam.meta.tag Tags applied to this resource DefinitionTags 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. 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. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". CommonTags (example)Constraints
|
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 | Σ ?! | 1..1 | codeBindingFixed Value | Element IdCareTeam.status Stato dell'aggregazione dell'equipe DefinitionValore fisso su "active" 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. CareTeamStatus (required)Constraints
active
|
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. CareTeamCategory (example)Constraints
|
name | Σ | 1..1 | string | Element IdCareTeam.name Nome dell'equipe DefinitionStringa alfanumerica di al più 100 caratteri Il dato è detenuto dal SGDT
|
subject | Σ I | 0..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element IdCareTeam.subject Who care team is for Alternate namespatient DefinitionIdentifies the patient or group whose intended care is handled by the team. 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
encounter | Σ I | 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 | Σ I | 1..1 | Period | Element IdCareTeam.period Periodo di attività dell'equipe 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
start | Σ I | 1..1 | dateTime | Element IdCareTeam.period.start Data inizio attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
end | Σ I | 0..1 | dateTime | Element IdCareTeam.period.end Data cessazione attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
participant | I | 0..* | BackboneElement | Element IdCareTeam.participant Elenco dei professionisti sanitari che compongono l'equipe DefinitionIdentifies all people and organizations who are expected to be involved in the care team. Il dato è detenuto dal SGDT
|
role | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdCareTeam.participant.role Type of involvement DefinitionIndicates 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example)Constraints
|
member | Σ I | 0..1 | Reference(RLPractitionerRoleProfessionistaSanitario) | Element IdCareTeam.participant.member Riferimento al professionista sanitario DefinitionReference al profilo RLPractitionerRoleProfessionistaSanitario 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(RLPractitionerRoleProfessionistaSanitario) Constraints
|
onBehalfOf | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
period | I | 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
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. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Indicates the reason for the care team. SNOMEDCTClinicalFindings (example)Constraints
| |
reasonReference | I | 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
managingOrganization | Σ I | 0..* | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
telecom | I | 0..* | ContactPoint | There are no (further) constraints on this element Element IdCareTeam.telecom A contact detail for the care team (that applies to all members) DefinitionA central contact detail for the care team (that applies to all members). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element IdCareTeam.note Comments made about the CareTeam DefinitionComments made about the CareTeam. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Differential View
CareTeam | I | CareTeam | There are no (further) constraints on this element Element IdCareTeam Planned participants in the coordination and delivery of care for a patient or group DefinitionThe Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.
| |
id | Σ | 1..1 | System.String | Element IdCareTeam.id UUID prodotto dal server FHIR (applicativo) che detiente la risorsa 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. System.String |
meta | Σ | 1..1 | Meta | Element IdCareTeam.meta Metadati della risorsa 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.
|
versionId | Σ | 1..1 | id | Element IdCareTeam.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. 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.
|
lastUpdated | Σ | 1..1 | instant | Element IdCareTeam.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz 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.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdCareTeam.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance 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. 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.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element IdCareTeam.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. 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. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element IdCareTeam.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. 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. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdCareTeam.meta.tag Tags applied to this resource DefinitionTags 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. 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. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". CommonTags (example)Constraints
|
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 | Σ ?! | 1..1 | codeBindingFixed Value | Element IdCareTeam.status Stato dell'aggregazione dell'equipe DefinitionValore fisso su "active" 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. CareTeamStatus (required)Constraints
active
|
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. CareTeamCategory (example)Constraints
|
name | Σ | 1..1 | string | Element IdCareTeam.name Nome dell'equipe DefinitionStringa alfanumerica di al più 100 caratteri Il dato è detenuto dal SGDT
|
subject | Σ I | 0..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element IdCareTeam.subject Who care team is for Alternate namespatient DefinitionIdentifies the patient or group whose intended care is handled by the team. 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
encounter | Σ I | 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 | Σ I | 1..1 | Period | Element IdCareTeam.period Periodo di attività dell'equipe 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
start | Σ I | 1..1 | dateTime | Element IdCareTeam.period.start Data inizio attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
end | Σ I | 0..1 | dateTime | Element IdCareTeam.period.end Data cessazione attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
participant | I | 0..* | BackboneElement | Element IdCareTeam.participant Elenco dei professionisti sanitari che compongono l'equipe DefinitionIdentifies all people and organizations who are expected to be involved in the care team. Il dato è detenuto dal SGDT
|
role | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdCareTeam.participant.role Type of involvement DefinitionIndicates 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example)Constraints
|
member | Σ I | 0..1 | Reference(RLPractitionerRoleProfessionistaSanitario) | Element IdCareTeam.participant.member Riferimento al professionista sanitario DefinitionReference al profilo RLPractitionerRoleProfessionistaSanitario 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(RLPractitionerRoleProfessionistaSanitario) Constraints
|
onBehalfOf | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
period | I | 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
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. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Indicates the reason for the care team. SNOMEDCTClinicalFindings (example)Constraints
| |
reasonReference | I | 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
managingOrganization | Σ I | 0..* | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
telecom | I | 0..* | ContactPoint | There are no (further) constraints on this element Element IdCareTeam.telecom A contact detail for the care team (that applies to all members) DefinitionA central contact detail for the care team (that applies to all members). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element IdCareTeam.note Comments made about the CareTeam DefinitionComments made about the CareTeam. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Hybrid View
CareTeam | I | CareTeam | There are no (further) constraints on this element Element IdCareTeam Planned participants in the coordination and delivery of care for a patient or group DefinitionThe Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.
| |
id | Σ | 1..1 | System.String | Element IdCareTeam.id UUID prodotto dal server FHIR (applicativo) che detiente la risorsa 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. System.String |
meta | Σ | 1..1 | Meta | Element IdCareTeam.meta Metadati della risorsa 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.
|
versionId | Σ | 1..1 | id | Element IdCareTeam.meta.versionId Versione della risorsa DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. 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.
|
lastUpdated | Σ | 1..1 | instant | Element IdCareTeam.meta.lastUpdated Data e ora di ultimo aggiornamento della risorsa DefinitionFormato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz 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.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdCareTeam.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance 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. 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.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element IdCareTeam.meta.profile Profilo al quale la risorsa si riferisce DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. 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. canonical(StructureDefinition) Constraints
https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe
|
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element IdCareTeam.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. 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. Security Labels from the Healthcare Privacy and Security Classification System. All Security Labels (extensible)Constraints
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdCareTeam.meta.tag Tags applied to this resource DefinitionTags 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. 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. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". CommonTags (example)Constraints
|
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 | Σ ?! | 1..1 | codeBindingFixed Value | Element IdCareTeam.status Stato dell'aggregazione dell'equipe DefinitionValore fisso su "active" 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. CareTeamStatus (required)Constraints
active
|
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. CareTeamCategory (example)Constraints
|
name | Σ | 1..1 | string | Element IdCareTeam.name Nome dell'equipe DefinitionStringa alfanumerica di al più 100 caratteri Il dato è detenuto dal SGDT
|
subject | Σ I | 0..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element IdCareTeam.subject Who care team is for Alternate namespatient DefinitionIdentifies the patient or group whose intended care is handled by the team. 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
encounter | Σ I | 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 | Σ I | 1..1 | Period | Element IdCareTeam.period Periodo di attività dell'equipe 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
start | Σ I | 1..1 | dateTime | Element IdCareTeam.period.start Data inizio attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
end | Σ I | 0..1 | dateTime | Element IdCareTeam.period.end Data cessazione attività DefinitionFormato: YYYY-MM-DD secondo lo standard FHIR. Il dato è detenuto dal SGDT
|
participant | I | 0..* | BackboneElement | Element IdCareTeam.participant Elenco dei professionisti sanitari che compongono l'equipe DefinitionIdentifies all people and organizations who are expected to be involved in the care team. Il dato è detenuto dal SGDT
|
role | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element IdCareTeam.participant.role Type of involvement DefinitionIndicates 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. Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example)Constraints
|
member | Σ I | 0..1 | Reference(RLPractitionerRoleProfessionistaSanitario) | Element IdCareTeam.participant.member Riferimento al professionista sanitario DefinitionReference al profilo RLPractitionerRoleProfessionistaSanitario 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(RLPractitionerRoleProfessionistaSanitario) Constraints
|
onBehalfOf | Σ I | 0..1 | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
period | I | 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
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. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Indicates the reason for the care team. SNOMEDCTClinicalFindings (example)Constraints
| |
reasonReference | I | 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
managingOrganization | Σ I | 0..* | Reference(Organization) | There are no (further) constraints on this element 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
telecom | I | 0..* | ContactPoint | There are no (further) constraints on this element Element IdCareTeam.telecom A contact detail for the care team (that applies to all members) DefinitionA central contact detail for the care team (that applies to all members). The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.
|
note | 0..* | Annotation | There are no (further) constraints on this element Element IdCareTeam.note Comments made about the CareTeam DefinitionComments made about the CareTeam. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
Table View
CareTeam | .. | |
CareTeam.id | 1.. | |
CareTeam.meta | 1.. | |
CareTeam.meta.versionId | 1.. | |
CareTeam.meta.lastUpdated | 1.. | |
CareTeam.meta.profile | 1..1 | |
CareTeam.status | 1.. | |
CareTeam.name | 1.. | |
CareTeam.period | 1.. | |
CareTeam.period.start | 1.. | |
CareTeam.period.end | .. | |
CareTeam.participant | .. | |
CareTeam.participant.member | Reference(RLPractitionerRoleProfessionistaSanitario) | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="RLCareTeamEquipe" /> <url value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe" /> <name value="RLCareTeamEquipe" /> <status value="draft" /> <description value="Profilo volto a definire un equipe di professionisti sanitari" /> <keyword> <system value="https://fhir.siss.regione.lombardia.it/CodeSystem/Tag" /> <code value="PI" /> </keyword> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="CareTeam" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/CareTeam" /> <derivation value="constraint" /> <differential> <element id="CareTeam.id"> <path value="CareTeam.id" /> <short value="UUID prodotto dal server FHIR (applicativo) che detiente la risorsa" /> <min value="1" /> </element> <element id="CareTeam.meta"> <path value="CareTeam.meta" /> <short value="Metadati della risorsa" /> <min value="1" /> </element> <element id="CareTeam.meta.versionId"> <path value="CareTeam.meta.versionId" /> <short value="Versione della risorsa" /> <min value="1" /> </element> <element id="CareTeam.meta.lastUpdated"> <path value="CareTeam.meta.lastUpdated" /> <short value="Data e ora di ultimo aggiornamento della risorsa" /> <definition value="Formato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz" /> <min value="1" /> </element> <element id="CareTeam.meta.profile"> <path value="CareTeam.meta.profile" /> <short value="Profilo al quale la risorsa si riferisce" /> <min value="1" /> <max value="1" /> <fixedCanonical value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe" /> </element> <element id="CareTeam.status"> <path value="CareTeam.status" /> <short value="Stato dell'aggregazione dell'equipe" /> <definition value="Valore fisso su "active"" /> <min value="1" /> <fixedCode value="active" /> </element> <element id="CareTeam.name"> <path value="CareTeam.name" /> <short value="Nome dell'equipe" /> <definition value="Stringa alfanumerica di al più 100 caratteri" /> <comment value="Il dato è detenuto dal SGDT" /> <min value="1" /> </element> <element id="CareTeam.period"> <path value="CareTeam.period" /> <short value="Periodo di attività dell'equipe" /> <min value="1" /> </element> <element id="CareTeam.period.start"> <path value="CareTeam.period.start" /> <short value="Data inizio attività" /> <definition value="Formato: YYYY-MM-DD secondo lo standard FHIR." /> <comment value="Il dato è detenuto dal SGDT" /> <min value="1" /> </element> <element id="CareTeam.period.end"> <path value="CareTeam.period.end" /> <short value="Data cessazione attività" /> <definition value="Formato: YYYY-MM-DD secondo lo standard FHIR." /> <comment value="Il dato è detenuto dal SGDT" /> </element> <element id="CareTeam.participant"> <path value="CareTeam.participant" /> <short value="Elenco dei professionisti sanitari che compongono l'equipe" /> <comment value="Il dato è detenuto dal SGDT" /> </element> <element id="CareTeam.participant.member"> <path value="CareTeam.participant.member" /> <short value="Riferimento al professionista sanitario" /> <definition value="Reference al profilo RLPractitionerRoleProfessionistaSanitario" /> <type> <code value="Reference" /> <targetProfile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/RLPractitionerRoleProfessionistaSanitario" /> </type> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "RLCareTeamEquipe", "url": "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe", "name": "RLCareTeamEquipe", "status": "draft", "description": "Profilo volto a definire un equipe di professionisti sanitari", "keyword": [ { "system": "https://fhir.siss.regione.lombardia.it/CodeSystem/Tag", "code": "PI" } ], "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "CareTeam", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/CareTeam", "derivation": "constraint", "differential": { "element": [ { "id": "CareTeam.id", "path": "CareTeam.id", "short": "UUID prodotto dal server FHIR (applicativo) che detiente la risorsa", "min": 1 }, { "id": "CareTeam.meta", "path": "CareTeam.meta", "short": "Metadati della risorsa", "min": 1 }, { "id": "CareTeam.meta.versionId", "path": "CareTeam.meta.versionId", "short": "Versione della risorsa", "min": 1 }, { "id": "CareTeam.meta.lastUpdated", "path": "CareTeam.meta.lastUpdated", "short": "Data e ora di ultimo aggiornamento della risorsa", "definition": "Formato standard FHIR: YYY-MM-DDThh:mm:ss.sss+zz:zz", "min": 1 }, { "id": "CareTeam.meta.profile", "path": "CareTeam.meta.profile", "short": "Profilo al quale la risorsa si riferisce", "min": 1, "max": "1", "fixedCanonical": "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLCareTeamEquipe" }, { "id": "CareTeam.status", "path": "CareTeam.status", "short": "Stato dell'aggregazione dell'equipe", "definition": "Valore fisso su \"active\"", "min": 1, "fixedCode": "active" }, { "id": "CareTeam.name", "path": "CareTeam.name", "short": "Nome dell'equipe", "definition": "Stringa alfanumerica di al più 100 caratteri", "comment": "Il dato è detenuto dal SGDT", "min": 1 }, { "id": "CareTeam.period", "path": "CareTeam.period", "short": "Periodo di attività dell'equipe", "min": 1 }, { "id": "CareTeam.period.start", "path": "CareTeam.period.start", "short": "Data inizio attività", "definition": "Formato: YYYY-MM-DD secondo lo standard FHIR.", "comment": "Il dato è detenuto dal SGDT", "min": 1 }, { "id": "CareTeam.period.end", "path": "CareTeam.period.end", "short": "Data cessazione attività", "definition": "Formato: YYYY-MM-DD secondo lo standard FHIR.", "comment": "Il dato è detenuto dal SGDT" }, { "id": "CareTeam.participant", "path": "CareTeam.participant", "short": "Elenco dei professionisti sanitari che compongono l'equipe", "comment": "Il dato è detenuto dal SGDT" }, { "id": "CareTeam.participant.member", "path": "CareTeam.participant.member", "short": "Riferimento al professionista sanitario", "definition": "Reference al profilo RLPractitionerRoleProfessionistaSanitario", "type": [ { "code": "Reference", "targetProfile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/RLPractitionerRoleProfessionistaSanitario" ] } ] } ] } }
Tipologie di ricerca
Attualmente non sono state definite tipologie di ricerca.
Search parameter
Attualmente non sono definiti Search Parameters.
ValueSet
Attualmente non sono definiti value set specifici per il profilo RLCareTeamEquipe.