EgdeEHG_IG - Local Development build (v0.1.7). See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON

Resource Profile: CareTeam - Egde Health Gateway - profile

Egde Health Gateway care team profile

Usage:

• This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

• Differential Table
• Key Elements Table
• Snapshot Table
• Statistics/References
• All

This structure is derived from CareTeam

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
name	S	1..1	string	Name of the team, such as crisis assessment team
subject		0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
participant
role		0..*	CodeableConcept	Type of involvement Binding: Care Team role (required)
member		0..1	Reference(Practitioner - Egde Health Gateway - profile for Norwegian practitioners | Practitioner)	Who is involved
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
CareTeam.participant.role	required	CareTeamRoleVS

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	0..1	code	proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates the status of the care team.
name	SΣ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
CareTeam.status	required	CareTeamStatus

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	CareTeam	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	CareTeam	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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	CareTeam	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()
dom-5	error	CareTeam	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	CareTeam	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates the status of the care team.
category	Σ	0..*	CodeableConcept	Type of team Binding: CareTeamCategory (example): Indicates the type of care team.
name	SΣ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
period	Σ	0..1	Period	Time period team covers
participant	C	0..*	BackboneElement	Members of the team
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
role	Σ	0..*	CodeableConcept	Type of involvement Binding: Care Team role (required)
member	Σ	0..1	Reference(Practitioner - Egde Health Gateway - profile for Norwegian practitioners | Practitioner)	Who is involved
onBehalfOf	Σ	0..1	Reference(Organization)	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists Binding: SNOMEDCTClinicalFindings (example): Indicates the reason for the care team.
reasonReference		0..*	Reference(Condition)	Why the care team exists
managingOrganization	Σ	0..*	Reference(Organization)	Organization responsible for the care team
telecom		0..*	ContactPoint	A contact detail for the care team (that applies to all members)
note		0..*	Annotation	Comments made about the CareTeam
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
CareTeam.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
CareTeam.status	required	CareTeamStatus
CareTeam.category	example	CareTeamCategory
CareTeam.participant.role	required	CareTeamRoleVS
CareTeam.reasonCode	example	SNOMEDCTClinicalFindings

Constraints

Id	Grade	Path(s)	Details	Requirements
ctm-1	error	CareTeam.participant	CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner : onBehalfOf.exists() implies (member.resolve().iif(empty(), true, ofType(Practitioner).exists()))
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

This structure is derived from CareTeam

Summary

Mandatory: 1 element
Must-Support: 1 element

Structures

This structure refers to these other structures:

• Patient - Egde Health Gateway - profile for Norwegian patients (http://www.egde.no/StructureDefinition/ehg-no-Patient)
• Practitioner - Egde Health Gateway - profile for Norwegian practitioners (http://www.egde.no/StructureDefinition/ehg-no-Practitioner)

Differential View

This structure is derived from CareTeam

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
name	S	1..1	string	Name of the team, such as crisis assessment team
subject		0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
participant
role		0..*	CodeableConcept	Type of involvement Binding: Care Team role (required)
member		0..1	Reference(Practitioner - Egde Health Gateway - profile for Norwegian practitioners | Practitioner)	Who is involved
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
CareTeam.participant.role	required	CareTeamRoleVS

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
status	?!Σ	0..1	code	proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates the status of the care team.
name	SΣ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
CareTeam.status	required	CareTeamStatus

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	CareTeam	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	CareTeam	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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4	error	CareTeam	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()
dom-5	error	CareTeam	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	CareTeam	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
CareTeam		0..*	CareTeam	Planned participants in the coordination and delivery of care for a patient or group
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Ids for this team
status	?!Σ	0..1	code	proposed | active | suspended | inactive | entered-in-error Binding: CareTeamStatus (required): Indicates the status of the care team.
category	Σ	0..*	CodeableConcept	Type of team Binding: CareTeamCategory (example): Indicates the type of care team.
name	SΣ	1..1	string	Name of the team, such as crisis assessment team
subject	Σ	0..1	Reference(Patient - Egde Health Gateway - profile for Norwegian patients | Patient)	Who care team is for
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
period	Σ	0..1	Period	Time period team covers
participant	C	0..*	BackboneElement	Members of the team
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
role	Σ	0..*	CodeableConcept	Type of involvement Binding: Care Team role (required)
member	Σ	0..1	Reference(Practitioner - Egde Health Gateway - profile for Norwegian practitioners | Practitioner)	Who is involved
onBehalfOf	Σ	0..1	Reference(Organization)	Organization of the practitioner
period		0..1	Period	Time period of participant
reasonCode		0..*	CodeableConcept	Why the care team exists Binding: SNOMEDCTClinicalFindings (example): Indicates the reason for the care team.
reasonReference		0..*	Reference(Condition)	Why the care team exists
managingOrganization	Σ	0..*	Reference(Organization)	Organization responsible for the care team
telecom		0..*	ContactPoint	A contact detail for the care team (that applies to all members)
note		0..*	Annotation	Comments made about the CareTeam
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
CareTeam.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
CareTeam.status	required	CareTeamStatus
CareTeam.category	example	CareTeamCategory
CareTeam.participant.role	required	CareTeamRoleVS
CareTeam.reasonCode	example	SNOMEDCTClinicalFindings

Constraints

Id	Grade	Path(s)	Details	Requirements
ctm-1	error	CareTeam.participant	CareTeam.participant.onBehalfOf can only be populated when CareTeam.participant.member is a Practitioner : onBehalfOf.exists() implies (member.resolve().iif(empty(), true, ofType(Practitioner).exists()))
ele-1	error	**ALL** elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	**ALL** extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()

This structure is derived from CareTeam

Summary

Mandatory: 1 element
Must-Support: 1 element

Structures

This structure refers to these other structures:

• Patient - Egde Health Gateway - profile for Norwegian patients (http://www.egde.no/StructureDefinition/ehg-no-Patient)
• Practitioner - Egde Health Gateway - profile for Norwegian practitioners (http://www.egde.no/StructureDefinition/ehg-no-Practitioner)

Other representations of profile: CSV, Excel, Schematron