Release
4
Clinical
Summary
This
page
is
part
of
the
FHIR
Specification
(v4.0.1:
R4
-
Mixed
Normative
and
STU
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
|
Work
Group
|
|
|
|
This
value
set
is
used
in
the
following
places:
Resource:
MolecularSequence.referenceSeq.referenceSeqId
(CodeableConcept
/
Example
)
4.4.1.345.1
Content
Logical
Definition
This
value
set
includes
codes
from
the
following
code
systems:
Include
all
codes
defined
in
http://www.ensembl.org
Include
all
codes
defined
in
http://www.ncbi.nlm.nih.gov/nuccore
4.4.1.345.2
Expansion
This
expansion
generated
01
Nov
2019
This
value
set
could
not
be
expanded
by
the
publication
tooling:
Error
from
server:
Unable
to
provide
support
for
code
system
http://www.ensembl.org
See
the
full
registry
of
value
sets
defined
as
part
of
FHIR.
Explanation
of
the
columns
that
may
appear
on
this
page:
Lvl
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
For
value
sets,
levels
are
mostly
used
to
organize
codes
for
user
convenience,
but
may
follow
code
system
hierarchy
-
see
Code
System
for
further
information
Source
The
source
of
the
definition
representation
of
the
code
(when
the
value
set
draws
in
codes
defined
elsewhere)
Code
The
code
(used
as
the
code
in
the
resource
instance).
If
the
code
is
in
italics,
this
indicates
that
the
code
json
schema
for
CareTeam,
which
is
not
selectable
('Abstract')
Display
The
display
(used
in
the
display
element
of
just
a
Coding
).
If
there
is
no
display,
implementers
should
not
simply
display
the
code,
but
map
the
concept
into
their
application
Definition
An
explanation
of
the
meaning
part
of
the
concept
Comments
Additional
notes
about
how
to
use
the
code
full
JSON
Schema
.
{
"$schema": "http://json-schema.org/draft-06/schema#",
"id": "http://hl7.org/fhir/json-schema/CareTeam",
"$ref": "#/definitions/CareTeam",
"description": "see http://hl7.org/fhir/json.html#schema for information about the FHIR Json Schemas",
"definitions": {
"CareTeam": {
"description": "The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.",
"properties": {
"resourceType": {
"description": "This is a CareTeam resource",
"const": "CareTeam"
},
"id": {
"description": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"$ref": "id.schema.json#/definitions/id"
},
"meta": {
"description": "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.",
"$ref": "Meta.schema.json#/definitions/Meta"
},
"implicitRules": {
"description": "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.",
"$ref": "#/definitions/uri"
},
"_implicitRules": {
"description": "Extensions for implicitRules",
"$ref": "Element.schema.json#/definitions/Element"
},
"language": {
"description": "The base language in which the resource is written.",
"$ref": "#/definitions/code"
},
"_language": {
"description": "Extensions for language",
"$ref": "Element.schema.json#/definitions/Element"
},
"text": {
"description": "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.",
"$ref": "Narrative.schema.json#/definitions/Narrative"
},
"contained": {
"description": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"items": {
"$ref": "ResourceList.schema.json#/definitions/ResourceList"
},
"type": "array"
},
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"modifierExtension": {
"description": "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\u0027s 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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"identifier": {
"description": "Business 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.",
"items": {
"$ref": "Identifier.schema.json#/definitions/Identifier"
},
"type": "array"
},
"status": {
"description": "Indicates the current state of the care team.",
"enum": [
"proposed",
"active",
"suspended",
"inactive",
"entered-in-error"
]
},
"_status": {
"description": "Extensions for status",
"$ref": "Element.schema.json#/definitions/Element"
},
"category": {
"description": "Identifies 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.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"name": {
"description": "A label for human use intended to distinguish like teams. E.g. the \"red\" vs. \"green\" trauma teams.",
"$ref": "#/definitions/string"
},
"_name": {
"description": "Extensions for name",
"$ref": "Element.schema.json#/definitions/Element"
},
"subject": {
"description": "Identifies the patient or group whose intended care is handled by the team.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"encounter": {
"description": "The Encounter during which this CareTeam was created or to which the creation of this record is tightly associated.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"period": {
"description": "Indicates when the team did (or is intended to) come into effect and end.",
"$ref": "Period.schema.json#/definitions/Period"
},
"participant": {
"description": "Identifies all people and organizations who are expected to be involved in the care team.",
"items": {
"$ref": "#/definitions/CareTeam_Participant"
},
"type": "array"
},
"reasonCode": {
"description": "Describes why the care team exists.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"reasonReference": {
"description": "Condition(s) that this care team addresses.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"managingOrganization": {
"description": "The organization responsible for the care team.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"telecom": {
"description": "A central contact detail for the care team (that applies to all members).",
"items": {
"$ref": "ContactPoint.schema.json#/definitions/ContactPoint"
},
"type": "array"
},
"note": {
"description": "Comments made about the CareTeam.",
"items": {
"$ref": "Annotation.schema.json#/definitions/Annotation"
},
"type": "array"
}
},
"additionalProperties": false,
"required": [
"resourceType"
]
},
"CareTeam_Participant": {
"description": "The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for a patient.",
"properties": {
"id": {
"description": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
"$ref": "string.schema.json#/definitions/string"
},
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"modifierExtension": {
"description": "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\u0027s 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.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"role": {
"description": "Indicates specific responsibility of an individual within the care team, such as \"Primary care physician\", \"Trained social worker counselor\", \"Caregiver\", etc.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"member": {
"description": "The specific person or organization who is participating/expected to participate in the care team.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"onBehalfOf": {
"description": "The organization of the practitioner.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"period": {
"description": "Indicates when the specific member or organization did (or is intended to) come into effect and end.",
"$ref": "Period.schema.json#/definitions/Period"
}
},
"additionalProperties": false
}
}
}
®©
HL7.org
2011+.
FHIR
Release
4
(Technical
Correction
#1)
(v4.0.1)
generated
on
Fri,
Nov
1,
2019
09:33+1100.
09:34+1100.
QA
Page
Links:
Search
|
Version
History
|
Table
of
Contents
|
Credits
|
Compare
to
R3
|
|
Propose
a
change