R4
Ballot
#1
(Mixed
Normative/Trial
use)
Administration
This
page
is
uncommon
to
need
details
about
multiple
other
names
for
that
person.
Summary
true
Practitioner.telecom
Definition
A
contact
detail
for
the
practitioner,
e.g.
a
telephone
number
or
an
email
address.
Control
0..*
Type
Contact
Requirements
Need
to
know
how
to
reach
a
practitioner.
Summary
true
Comments
Person
may
have
multiple
ways
to
be
contacted
with
different
uses
or
applicable
periods.
May
need
to
have
options
for
contacting
part
of
the
person
urgently,
and
also
to
help
with
identification.
Practitioner.address
Definition
FHIR
Specification
(v3.3.0:
R4
Ballot
2).
The
postal
address
where
the
practitioner
can
be
found
or
visited
or
to
current
version
which
mail
can
be
delivered.
Control
0..1
Type
Address
Requirements
Need
to
keep
track
where
the
practitioner
can
found
during
work
or
for
directing
mail.
Summary
true
Practitioner.gender
Definition
Administrative
Gender
-
the
gender
that
the
person
supercedes
this
version
is
considered
to
have
for
administration
and
record
keeping
purposes.
Control
0..1
Binding
AdministrativeGender:
(
See
http://hl7.org/fhir/vs/administrative-gender
)
Type
CodeableConcept
Requirements
Needed
to
address
the
person
correctly.
Summary
true
Practitioner.birthDate
Definition
The
date
and
time
of
birth
for
the
practitioner.
Control
0..1
Type
dateTime
Requirements
Needed
for
identification.
Summary
true
Practitioner.photo
Definition
Image
5.0.0
.
For
a
full
list
of
available
versions,
see
the
person.
Control
0..*
Type
Attachment
Requirements
Many
EHR
systems
have
the
capability
to
capture
an
image
Directory
of
patients
and
personnel.
Fits
with
newer
social
media
usage
too.
Practitioner.organization
Definition
The
organization
that
the
practitioner
represents.
Control
0..1
Type
published
versions
Resource
.
Page
versions:
R5
(
Organization
R4B
)
Requirements
Need
to
be
able
to
track
the
represented
organization
separately,
if
any.
Summary
R4
true
Practitioner.role
|
|
|
Ballot Status : Informative |
|
This
is
authorized
to
act
as
a
practitioner
in
these
role(s)
for
the
organization.
Control
0..1
Type
Period
Requirements
Even
after
the
agencies
is
revoked,
the
fact
that
it
existed
must
still
be
recorded.
Summary
true
Practitioner.location
Definition
The
location(s)
at
which
this
practitioner
provides
care.
Control
0..*
Type
Resource
(
Location
)
Practitioner.qualification
Definition
Qualifications
obtained
by
training
and
certification.
Control
0..*
Practitioner.qualification.code
Definition
Coded
representation
of
the
qualification.
Control
1..1
Binding
Qualification:
(
See
http://hl7.org/fhir/vs/anzsco-occupations
)
Type
CodeableConcept
Practitioner.qualification.period
Definition
Period
during
which
the
qualification
is
valid.
Control
0..1
Type
Period
Requirements
Qualifications
are
often
json
schema
for
a
limited
period
of
time,
and
can
be
revoked.
Practitioner.qualification.issuer
Definition
Organization
that
regulates
and
issues
the
qualification.
Control
0..1
Type
Resource
(
Organization
)
Practitioner.communication
Definition
A
language
the
practitioner
is
able
to
use
in
patient
communication.
Control
0..*
Binding
Language:
see
IETF
language
tag
Type
CodeableConcept
Requirements
Knowing
Encounter,
which
language
a
practitioner
speaks
can
help
in
facilitating
communication
with
patients.
Comments
The
structure
aa-BB
with
this
exact
casing
is
one
the
most
widely
used
notations
for
locale.
However
not
all
systems
actually
code
this
but
instead
have
it
as
free
text.
Hence
CodeableConcept
instead
just
a
part
of
code
as
the
data
type.
full
JSON
Schema
.
{
"$schema": "http://json-schema.org/draft-06/schema#",
"id": "http://hl7.org/fhir/json-schema/Encounter",
"$ref": "#/definitions/Encounter",
"description": "see http://hl7.org/fhir/json.html#schema for information about the FHIR Json Schemas",
"definitions": {
"Encounter": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.",
"properties": {
"resourceType": {
"description": "This is a Encounter resource",
"const": "Encounter"
},
"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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"identifier": {
"description": "Identifier(s) by which this encounter is known.",
"items": {
"$ref": "Identifier.schema.json#/definitions/Identifier"
},
"type": "array"
},
"status": {
"description": "planned | arrived | triaged | in-progress | onleave | finished | cancelled +.",
"enum": [
"planned",
"arrived",
"triaged",
"in-progress",
"onleave",
"finished",
"cancelled",
"entered-in-error",
"unknown"
]
},
"_status": {
"description": "Extensions for status",
"$ref": "Element.schema.json#/definitions/Element"
},
"statusHistory": {
"description": "The status history permits the encounter resource to contain the status history without needing to read through the historical versions of the resource, or even have the server store them.",
"items": {
"$ref": "#/definitions/Encounter_StatusHistory"
},
"type": "array"
},
"class": {
"description": "Concepts representing classification of patient encounter such as ambulatory (outpatient), inpatient, emergency, home health or others due to local variations.",
"$ref": "Coding.schema.json#/definitions/Coding"
},
"classHistory": {
"description": "The class history permits the tracking of the encounters transitions without needing to go through the resource history. This would be used for a case where an admission starts of as an emergency encounter, then transisions into an inpatient scenario. Doing this and not restarting a new encounter ensures that any lab/diagnostic results can more easily follow the patient and not require re-processing and not get lost or cancelled during a kindof discharge from emergency to inpatient.",
"items": {
"$ref": "#/definitions/Encounter_ClassHistory"
},
"type": "array"
},
"type": {
"description": "Specific type of encounter (e.g. e-mail consultation, surgical day-care, skilled nursing, rehabilitation).",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"serviceType": {
"description": "Broad categorization of the service that is to be provided (e.g. cardiology).",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"priority": {
"description": "Indicates the urgency of the encounter.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"subject": {
"description": "The patient or group present at the encounter.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"episodeOfCare": {
"description": "Where a specific encounter should be classified as a part of a specific episode(s) of care this field should be used. This association can facilitate grouping of related encounters together for a specific purpose, such as government reporting, issue tracking, association via a common problem. The association is recorded on the encounter as these are typically created after the episode of care, and grouped on entry rather than editing the episode of care to append another encounter to it (the episode of care could span years).",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"basedOn": {
"description": "The request this encounter satisfies (e.g. incoming referral or procedure request).",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"participant": {
"description": "The list of people responsible for providing the service.",
"items": {
"$ref": "#/definitions/Encounter_Participant"
},
"type": "array"
},
"appointment": {
"description": "The appointment that scheduled this encounter.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"period": {
"description": "The start and end time of the encounter.",
"$ref": "Period.schema.json#/definitions/Period"
},
"length": {
"description": "Quantity of time the encounter lasted. This excludes the time during leaves of absence.",
"$ref": "Duration.schema.json#/definitions/Duration"
},
"reason": {
"description": "Reason the encounter takes place, expressed as a code. For admissions, this can be used for a coded admission diagnosis.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"diagnosis": {
"description": "The list of diagnosis relevant to this encounter.",
"items": {
"$ref": "#/definitions/Encounter_Diagnosis"
},
"type": "array"
},
"account": {
"description": "The set of accounts that may be used for billing for this Encounter.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"hospitalization": {
"description": "Details about the admission to a healthcare service.",
"$ref": "#/definitions/Encounter_Hospitalization"
},
"location": {
"description": "List of locations where the patient has been during this encounter.",
"items": {
"$ref": "#/definitions/Encounter_Location"
},
"type": "array"
},
"serviceProvider": {
"description": "The organization that is primarily responsible for this Encounter\u0027s services. This MAY be the same as the organization on the Patient record, however it could be different, such as if the actor performing the services was from an external organization (which may be billed seperately) for an external consultation. Refer to the example bundle showing an abbreviated set of Encounters for a colonoscopy.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"partOf": {
"description": "Another Encounter of which this encounter is a part of (administratively or in time).",
"$ref": "Reference.schema.json#/definitions/Reference"
}
},
"additionalProperties": false,
"required": [
"class",
"resourceType"
]
},
"Encounter_StatusHistory": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"status": {
"description": "planned | arrived | triaged | in-progress | onleave | finished | cancelled +.",
"enum": [
"planned",
"arrived",
"triaged",
"in-progress",
"onleave",
"finished",
"cancelled",
"entered-in-error",
"unknown"
]
},
"_status": {
"description": "Extensions for status",
"$ref": "Element.schema.json#/definitions/Element"
},
"period": {
"description": "The time that the episode was in the specified status.",
"$ref": "Period.schema.json#/definitions/Period"
}
},
"additionalProperties": false,
"required": [
"period"
]
},
"Encounter_ClassHistory": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"class": {
"description": "inpatient | outpatient | ambulatory | emergency +.",
"$ref": "Coding.schema.json#/definitions/Coding"
},
"period": {
"description": "The time that the episode was in the specified class.",
"$ref": "Period.schema.json#/definitions/Period"
}
},
"additionalProperties": false,
"required": [
"period",
"class"
]
},
"Encounter_Participant": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"type": {
"description": "Role of participant in encounter.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"period": {
"description": "The period of time that the specified participant participated in the encounter. These can overlap or be sub-sets of the overall encounter\u0027s period.",
"$ref": "Period.schema.json#/definitions/Period"
},
"individual": {
"description": "Persons involved in the encounter other than the patient.",
"$ref": "Reference.schema.json#/definitions/Reference"
}
},
"additionalProperties": false
},
"Encounter_Diagnosis": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"condition": {
"description": "Reason the encounter takes place, as specified using information from another resource. For admissions, this is the admission diagnosis. The indication will typically be a Condition (with other resources referenced in the evidence.detail), or a Procedure.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"role": {
"description": "Role that this diagnosis has within the encounter (e.g. admission, billing, discharge …).",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"rank": {
"description": "Ranking of the diagnosis (for each role type).",
"$ref": "#/definitions/positiveInt"
},
"_rank": {
"description": "Extensions for rank",
"$ref": "Element.schema.json#/definitions/Element"
}
},
"additionalProperties": false,
"required": [
"condition"
]
},
"Encounter_Hospitalization": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"preAdmissionIdentifier": {
"description": "Pre-admission identifier.",
"$ref": "Identifier.schema.json#/definitions/Identifier"
},
"origin": {
"description": "The location/organization from which the patient came before admission.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"admitSource": {
"description": "From where patient was admitted (physician referral, transfer).",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"reAdmission": {
"description": "Whether this hospitalization is a readmission and why if known.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"dietPreference": {
"description": "Diet preferences reported by the patient.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"specialCourtesy": {
"description": "Special courtesies (VIP, board member).",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"specialArrangement": {
"description": "Any special requests that have been made for this hospitalization encounter, such as the provision of specific equipment or other things.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"destination": {
"description": "Location/organization to which the patient is discharged.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"dischargeDisposition": {
"description": "Category or kind of location after discharge.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
}
},
"additionalProperties": false
},
"Encounter_Location": {
"description": "An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of 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. 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.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"location": {
"description": "The location where the encounter takes place.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"status": {
"description": "The status of the participants\u0027 presence at the specified location during the period specified. If the participant is is no longer at the location, then the period will have an end date/time.",
"enum": [
"planned",
"active",
"reserved",
"completed"
]
},
"_status": {
"description": "Extensions for status",
"$ref": "Element.schema.json#/definitions/Element"
},
"period": {
"description": "Time period during which the patient was present at the location.",
"$ref": "Period.schema.json#/definitions/Period"
}
},
"additionalProperties": false,
"required": [
"location"
]
}
}
}
©
®©
HL7.org
2011+.
FHIR
DSTU
(v0.0.82.2943)
Mixed
Nomative/Trial
Use
Ballot
(v3.3.0-13671)
generated
on
Tue,
Sep
30,
2014
18:10+1000.
Apr
3,
2018
12:15+1000.
QA
Page
Links:
What's
a
DSTU?
Search
|
Version
History
|
Table
of
Contents
|
Credits
|
Compare
to
DSTU3
|
|
Propose
a
change