Example
MedicationAdministration/medadmin0301
(Turtle)
Raw
XML
Turtle
(
canonical
form
(+
also
see
Turtle/RDF
Format
Specification
)
StructureDefinition
for
ElementDefinition
Raw
XML
Intravenous
Antibiotic
-
Vancomycin
not(exists(for $type in f:type return $type/preceding-sibling::f:type[f:code/@value=$type/f:code/@va
lue and f:profile/@value = $type/f:profile/@value]))
not(exists(f:binding)) or (count(f:type/f:code) = 0) or f:type/f:code/@value=('code','Coding','Code
ableConcept','Quantity','Extension', 'string', 'uri')
not(exists(f:*[starts-with(local-name(.), 'pattern')])) or not(exists(f:*[starts-with(local-name(.),
'value')]))
(not(f:max/@value) and not(f:min/@value)) or (f:max/@value = '*') or (f:max/@value >=
f:min/@value)
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
The path identifies the element and is expressed as a "."-separated list of
ancestor elements, beginning with the name of the resource or extension.
Codes that define how this element is represented in instances, when the deviation varies
from the normal case.
This is rarely used except for special cases where the representation deviates from the
normal, which is done only very reluctantly, and can only be done in the base standard
(and profiles must reproduce what the base standard does).
The name of this element definition (to refer to it from other element definitions using
ElementDefinition.nameReference). This is a unique name referring to a specific set of
constraints applied to this element. One use of this is to provide a name to different
slices of the same element.
The name SHALL be unique within the structure within the context of the constrained resource
element. (Though to avoid confusion, uniqueness across all elements is recommended.).
The text to display beside the element indicating its meaning or to use to prompt for
the element in a user display or form.
Question and label serve similar purposes in they both can be used to prompt for capturing
a data element. Whether the question form or label form should be used will depend on
the type of instrument being used to capture the information.
The data element definition and other constraints SHALL be a proper constraint on the
meaning (as defined in the code system, including relationships) of any code listed here.
Where multiple codes exist in a terminology that could correspond to the data element,
the most granular code(s) should be selected, so long as they are not more restrictive
than the data element itself.
Indicates that the element is sliced into a set of alternative definitions (there are
multiple definitions on a single element in the base resource). The set of slices is any
elements that come after this in the element sequence that have the same path, until a
shorter path occurs (the shorter path terminates the set).
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
Designates which child elements are used to discriminate between the slices when processing
an instance. If one or more discriminators are provided, the value of the child elements
in the instance data SHALL completely distinguish which slice the element in the resource
matches based on the allowed values for those elements in each of the slices.
A human-readable text description of how the slicing works. If there is no discriminator,
this is required to be present to provide whatever information is possible about how the
slices can be differentiated.
If it's really not possible to differentiate them, the design should be re-evaluated to
make te content usable.
Order should only be required when it is a pressing concern for presentation. Profile
authors should consider making the order a feature of the rules about the narrative, not
the rules about the data - requiring ordered data makes the profile much less re-usable.
Whether additional slices are allowed or not. When the slices are ordered, profile authors
can also say that additional slices are only allowed at the end.
Allowing additional elements makes for a much for flexible template - it's open for use
in wider contexts, but also means that the content of the resource is not closed, and
applications have to decide how to handle content not described by the profile.
A concise definition that is shown in the generated XML format that summarizes profiles
(used throughout the specification).
May change the term to provide language more appropriate to the context of the profile
or to reflect slicing.
Provides a complete explanation of the meaning of the data element for human readability.
For the case of elements derived from existing elements (e.g. constraints), the definition
SHALL be consistent with the base definition, but convey the meaning of the element in
the particular context of use of the resource.
It is easy for a different definition to change the meaning of an element and this can
have nasty downstream consequences. Please be careful when providing definitions.
Comments about the use of the element, including notes about how to use the data properly,
exceptions to proper use, etc.
If it is possible to capture usage rules using invariants, that mechanism should be used
in preference to this element.
This element does not describe the usage of the element (that's done in comments), rather
it's for traceability of *why* the element is either needed or why the constraints exist
as they do. This may be used to point to source materials or specifications that drove
the structure of this data element.
./inboundRelationship[typeCode=META]/source[classCode=ACT, moodCode=EVN, isCriterionInd=true]/reason
Code/originalText
Allows for better easier recognition of the element by multiple communities, including
international communities.
@value='*' or (normalize-space(@value)!='' and normalize-space(translate(@value, '0123456789',''))='
')
The Type of the element can be left blank, in which case the type is inherited from the
resource. The type can only be listed in this field if it is an allowed option in the
base resource.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
If the element is a reference to another resource, this element contains "Reference",
and the profile element refers to the profile of the allowed target of the resource, which
may be a reference to the general definition of a resource (e.g. http://hl7.org/fhir/StructureDefini
tion/Patient). There would be one pair of type/code for each allowed target resource type.
Identifies a profile structure that SHALL hold for resources or datatypes referenced as
the type of this element. Can be a local reference - to another structure in this profile,
or a reference to a structure in another profile.
The reference might be a simple name in the form #[name], which is a reference to another
named constraint in a resource - where the resource contains more than one constraint,
or a URL which is a reference to a resource Profile, with a terminal #[name] which identifies
a specific structure entry in the profile.
If the type is a reference to another resource, how the resource is or can be aggreated
- is it a contained resource, or a reference, and if the context is a bundle, is it included
in the bundle.
Identifies the name of a slice defined elsewhere in the profile whose constraints should
be applied to the current element.
If child components of this element are defined, they act as constraints on the referenced
slice.
Default values can only be specified on a resource, data type, or extension definition,
and never in a profile that applies to one of these. Specifying a default value means
that the property can never been unknown - it must always have a value. Further, the default
value can never be changed. For these reasons, default values are (and should be) used
extremely sparingly.
Implicit meanings for missing values can only be specified on a resource, data type, or
extension definition, and never in a profile that applies to one of these. An implicit
meaning for a missing value can never be changed, and specifying one has the consequence
that constraining its use in profiles eliminates use cases as possibilities, not merely
moving them out of scope.
Specifies a value that SHALL be exactly the value for this element in the instance. For
purposes of comparison, non-signficant whitespace is ignored, and all values must be an
exact match (case and accent sensitive). Missing elements/attributes must also be missing.
This is not recommended for Coding and CodeableConcept since these often have highly contextual
properties such as version or display.
Specifies a value that the value in the instance SHALL follow - that is, any value in
the pattern must be found in the instance. Other additional values may be found too. This
is effectively constraint by example. The values of elements present in the pattern must
match exactly (case-senstive, accent-sensitive, etc.).
A sample value for this element demonstrating the type of information that would typically
be captured.
This will most commonly be present for data where it's not implicitly obvious from either
the data type or value set what the values might be. (I.e. Example values for dates or
quantities would generally be unnecessary.) If the example value are fully populated,
the publication tool can generate an instance automatically.
Indicates the maximum length in characters that is permitted to be present in conformant
instances and which is expected to be supported by conformant consumers that support the
element.
Receivers are not required to reject instances that exceed the maximum length. The full
length could be stored. In some cases, data might be truncated, though truncation should
be undertaken with care and an understanding of the consequences of doing so. If not specified,
there is no conformance expectation for length support.
A reference to an invariant that may make additional statements about the cardinality
or value in the instance.
Formal constraints such as co-occurrence and other constraints that can be computationally
evaluated within the context of the instance.
Constraints should be declared on the "context" element - the lowest element
in the hierarchy that is common to all nodes referenced by the constraint.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
Allows identification of which elements have their cardinalities impacted by the constraint.
Will not be referenced for constraints that do not affect cardinality.
Used to label the constraint in OCL or in short displays incapable of displaying the full
human description.
This allows constraints to be asserted as "shall" (error) and "should"
(warning).
Text that can be used to describe the constraint in messages identifying that the constraint
has been violated.
Elements SHALL use "f" as the namespace prefix for the FHIR namespace, and "x"
for the xhtml namespace, and SHALL not use any other prefixes.
If true, conformant resource authors SHALL be capable of providing a value for the element
and resource consumers SHALL be capable of extracting and doing something useful with
the data element. If false, the element may be ignored and not supported.
"Something useful" is context dependent. This flag is never set to true by the
FHIR specification itself - it is only set to true in profiles, and when the profile sets
it true, it SHALL describe what it means for applications to support the element. In general,
the question is what would a reasonable observer expect of a system that explicitly claims
to "support" this element?
Allows a profile to set expectations for system capabilities beyond merely respecting
cardinality constraints.
If true, the value of this element affects the interpretation of the element or resource
that contains it, and the value of the element cannot be ignored. Typically, this is used
for status, negation and qualification codes. The effect of this is that the element cannot
be ignored by systems: they SHALL either recognize the element and process it, and/or
a pre-determination has been made that it is not relevant to their particular system.
Only the definition of an element can set IsModifier true - either the specification itself
or where an extension is originally defined. Once set to false, it cannot be set to true
in derived profiles. An element/extension that has isModifier=true SHOULD also have a
minimum cardinality of 1, so that there is no lack of clarity about what to do if it is
missing. If it can be missing, the definition SHALL make the meaning of a missing element
clear.
Allows elements to be introduced into a specification that can't safely be ignored by
applications that don't recognize them.
Whether the element should be included if a client requests a search with the parameter
_summary=true.
Some resources include a set of simple metadata, and some very large data. This element
is used to reduce the quantity of data returned in searches. Note that servers may pre-cache
summarised resources for optimal performance, so servers may not support per-profile use
of the isSummary flag.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
SHALL be unique within the profile. If the same name as an imported profile, will override
the imported binding (and SHALL be a proper constraint on the imported binding).
Indicates the degree of conformance expectations associated with this binding - that is,
the degree to which the provided value set must be adhered to in the instances.
Points to the value set or external definition (e.g. implicit value set) that identifies
the set of codes to be used.
For value sets,the referenceResource, the display can contain the value set description.
The reference may be version-specific or not.
May be used to represent additional information that is not part of the basic definition
of the element. In order 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.
There can be no stigma associated with the use of extensions by any application, project,
or standard - regardless of the institution or jurisdiction that uses or defines the extensions.
The use of extensions is what allows the FHIR specification to retain a core level of
simplicity for everyone.
For most mappings, the syntax is undefined. Syntax will be provided for mappings to the
RIM. Multiple mappings may be possible and may include constraints on other resource
elements that identify when a particular mapping applies.
not(exists(for $type in f:type return $type/preceding-sibling::f:type[f:code/@value=$type/f:code/@va
lue and f:profile/@value = $type/f:profile/@value]))
not(exists(f:binding)) or (count(f:type/f:code) = 0) or f:type/f:code/@value=('code','Coding','Code
ableConcept','Quantity','Extension', 'string', 'uri')
not(exists(f:*[starts-with(local-name(.), 'pattern')])) or not(exists(f:*[starts-with(local-name(.),
'value')]))
(not(f:max/@value) and not(f:min/@value)) or (f:max/@value = '*') or (f:max/@value >=
f:min/@value)
The path identifies the element and is expressed as a "."-separated list of
ancestor elements, beginning with the name of the resource or extension.
Codes that define how this element is represented in instances, when the deviation varies
from the normal case.
This is rarely used except for special cases where the representation deviates from the
normal, which is done only very reluctantly, and can only be done in the base standard
(and profiles must reproduce what the base standard does).
The name of this element definition (to refer to it from other element definitions using
ElementDefinition.nameReference). This is a unique name referring to a specific set of
constraints applied to this element. One use of this is to provide a name to different
slices of the same element.
The name SHALL be unique within the structure within the context of the constrained resource
element. (Though to avoid confusion, uniqueness across all elements is recommended.).
The text to display beside the element indicating its meaning or to use to prompt for
the element in a user display or form.
Question and label serve similar purposes in they both can be used to prompt for capturing
a data element. Whether the question form or label form should be used will depend on
the type of instrument being used to capture the information.
The data element definition and other constraints SHALL be a proper constraint on the
meaning (as defined in the code system, including relationships) of any code listed here.
Where multiple codes exist in a terminology that could correspond to the data element,
the most granular code(s) should be selected, so long as they are not more restrictive
than the data element itself.
Indicates that the element is sliced into a set of alternative definitions (there are
multiple definitions on a single element in the base resource). The set of slices is any
elements that come after this in the element sequence that have the same path, until a
shorter path occurs (the shorter path terminates the set).
Designates which child elements are used to discriminate between the slices when processing
an instance. If one or more discriminators are provided, the value of the child elements
in the instance data SHALL completely distinguish which slice the element in the resource
matches based on the allowed values for those elements in each of the slices.
A human-readable text description of how the slicing works. If there is no discriminator,
this is required to be present to provide whatever information is possible about how the
slices can be differentiated.
If it's really not possible to differentiate them, the design should be re-evaluated to
make te content usable.
Order should only be required when it is a pressing concern for presentation. Profile
authors should consider making the order a feature of the rules about the narrative, not
the rules about the data - requiring ordered data makes the profile much less re-usable.
Whether additional slices are allowed or not. When the slices are ordered, profile authors
can also say that additional slices are only allowed at the end.
Allowing additional elements makes for a much for flexible template - it's open for use
in wider contexts, but also means that the content of the resource is not closed, and
applications have to decide how to handle content not described by the profile.
A concise definition that is shown in the generated XML format that summarizes profiles
(used throughout the specification).
May change the term to provide language more appropriate to the context of the profile
or to reflect slicing.
Provides a complete explanation of the meaning of the data element for human readability.
For the case of elements derived from existing elements (e.g. constraints), the definition
SHALL be consistent with the base definition, but convey the meaning of the element in
the particular context of use of the resource.
It is easy for a different definition to change the meaning of an element and this can
have nasty downstream consequences. Please be careful when providing definitions.
Comments about the use of the element, including notes about how to use the data properly,
exceptions to proper use, etc.
If it is possible to capture usage rules using invariants, that mechanism should be used
in preference to this element.
This element does not describe the usage of the element (that's done in comments), rather
it's for traceability of *why* the element is either needed or why the constraints exist
as they do. This may be used to point to source materials or specifications that drove
the structure of this data element.
./inboundRelationship[typeCode=META]/source[classCode=ACT, moodCode=EVN, isCriterionInd=true]/reason
Code/originalText
Allows for better easier recognition of the element by multiple communities, including
international communities.
@value='*' or (normalize-space(@value)!='' and normalize-space(translate(@value, '0123456789',''))='
')
The Type of the element can be left blank, in which case the type is inherited from the
resource. The type can only be listed in this field if it is an allowed option in the
base resource.
If the element is a reference to another resource, this element contains "Reference",
and the profile element refers to the profile of the allowed target of the resource, which
may be a reference to the general definition of a resource (e.g. http://hl7.org/fhir/StructureDefini
tion/Patient). There would be one pair of type/code for each allowed target resource type.
Identifies a profile structure that SHALL hold for resources or datatypes referenced as
the type of this element. Can be a local reference - to another structure in this profile,
or a reference to a structure in another profile.
The reference might be a simple name in the form #[name], which is a reference to another
named constraint in a resource - where the resource contains more than one constraint,
or a URL which is a reference to a resource Profile, with a terminal #[name] which identifies
a specific structure entry in the profile.
If the type is a reference to another resource, how the resource is or can be aggreated
- is it a contained resource, or a reference, and if the context is a bundle, is it included
in the bundle.
Identifies the name of a slice defined elsewhere in the profile whose constraints should
be applied to the current element.
If child components of this element are defined, they act as constraints on the referenced
slice.
Default values can only be specified on a resource, data type, or extension definition,
and never in a profile that applies to one of these. Specifying a default value means
that the property can never been unknown - it must always have a value. Further, the default
value can never be changed. For these reasons, default values are (and should be) used
extremely sparingly.
Implicit meanings for missing values can only be specified on a resource, data type, or
extension definition, and never in a profile that applies to one of these. An implicit
meaning for a missing value can never be changed, and specifying one has the consequence
that constraining its use in profiles eliminates use cases as possibilities, not merely
moving them out of scope.
Specifies a value that SHALL be exactly the value for this element in the instance. For
purposes of comparison, non-signficant whitespace is ignored, and all values must be an
exact match (case and accent sensitive). Missing elements/attributes must also be missing.
This is not recommended for Coding and CodeableConcept since these often have highly contextual
properties such as version or display.
Specifies a value that the value in the instance SHALL follow - that is, any value in
the pattern must be found in the instance. Other additional values may be found too. This
is effectively constraint by example. The values of elements present in the pattern must
match exactly (case-senstive, accent-sensitive, etc.).
A sample value for this element demonstrating the type of information that would typically
be captured.
This will most commonly be present for data where it's not implicitly obvious from either
the data type or value set what the values might be. (I.e. Example values for dates or
quantities would generally be unnecessary.) If the example value are fully populated,
the publication tool can generate an instance automatically.
Indicates the maximum length in characters that is permitted to be present in conformant
instances and which is expected to be supported by conformant consumers that support the
element.
Receivers are not required to reject instances that exceed the maximum length. The full
length could be stored. In some cases, data might be truncated, though truncation should
be undertaken with care and an understanding of the consequences of doing so. If not specified,
there is no conformance expectation for length support.
A reference to an invariant that may make additional statements about the cardinality
or value in the instance.
Formal constraints such as co-occurrence and other constraints that can be computationally
evaluated within the context of the instance.
Constraints should be declared on the "context" element - the lowest element
in the hierarchy that is common to all nodes referenced by the constraint.
Allows identification of which elements have their cardinalities impacted by the constraint.
Will not be referenced for constraints that do not affect cardinality.
Used to label the constraint in OCL or in short displays incapable of displaying the full
human description.
This allows constraints to be asserted as "shall" (error) and "should"
(warning).
Text that can be used to describe the constraint in messages identifying that the constraint
has been violated.
Elements SHALL use "f" as the namespace prefix for the FHIR namespace, and "x"
for the xhtml namespace, and SHALL not use any other prefixes.
If true, conformant resource authors SHALL be capable of providing a value for the element
and resource consumers SHALL be capable of extracting and doing something useful with
the data element. If false, the element may be ignored and not supported.
"Something useful" is context dependent. This flag is never set to true by the
FHIR specification itself - it is only set to true in profiles, and when the profile sets
it true, it SHALL describe what it means for applications to support the element. In general,
the question is what would a reasonable observer expect of a system that explicitly claims
to "support" this element?
Allows a profile to set expectations for system capabilities beyond merely respecting
cardinality constraints.
If true, the value of this element affects the interpretation of the element or resource
that contains it, and the value of the element cannot be ignored. Typically, this is used
for status, negation and qualification codes. The effect of this is that the element cannot
be ignored by systems: they SHALL either recognize the element and process it, and/or
a pre-determination has been made that it is not relevant to their particular system.
Only the definition of an element can set IsModifier true - either the specification itself
or where an extension is originally defined. Once set to false, it cannot be set to true
in derived profiles. An element/extension that has isModifier=true SHOULD also have a
minimum cardinality of 1, so that there is no lack of clarity about what to do if it is
missing. If it can be missing, the definition SHALL make the meaning of a missing element
clear.
Allows elements to be introduced into a specification that can't safely be ignored by
applications that don't recognize them.
Whether the element should be included if a client requests a search with the parameter
_summary=true.
Some resources include a set of simple metadata, and some very large data. This element
is used to reduce the quantity of data returned in searches. Note that servers may pre-cache
summarised resources for optimal performance, so servers may not support per-profile use
of the isSummary flag.
SHALL be unique within the profile. If the same name as an imported profile, will override
the imported binding (and SHALL be a proper constraint on the imported binding).
Indicates the degree of conformance expectations associated with this binding - that is,
the degree to which the provided value set must be adhered to in the instances.
Points to the value set or external definition (e.g. implicit value set) that identifies
the set of codes to be used.
For value sets,the referenceResource, the display can contain the value set description.
The reference may be version-specific or not.
For most mappings, the syntax is undefined. Syntax will be provided for mappings to the
RIM. Multiple mappings may be possible and may include constraints on other resource
elements that identify when a particular mapping applies.
</StructureDefinition>
@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sct: <http://snomed.info/id/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# - resource -------------------------------------------------------------------
[a fhir:MedicationAdministration;
fhir:nodeRole fhir:treeRoot;
fhir:Resource.id [ fhir:value "medadmin0301"]; #
fhir:DomainResource.text [
fhir:Narrative.status [ fhir:value "generated" ];
fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative: MedicationAdministration</b><a name=\"medadmin0301\"> </a></p><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Resource MedicationAdministration "medadmin0301" </p></div><p><b>status</b>: in-progress</p><h3>Medications</h3><table class=\"grid\"><tr><td>-</td><td><b>Reference</b></td></tr><tr><td>*</td><td><a name=\"med0301\"> </a><blockquote><p/><p><a name=\"med0301\"> </a></p><p><b>code</b>: Vancomycin Hydrochloride (VANCOMYCIN HYDROCHLORIDE) <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-v3-ndc.html\">National drug codes</a>#0409-6531-02)</span></p></blockquote></td></tr></table><p><b>subject</b>: <a href=\"patient-example-a.html\">Patient/pat1: Donald Duck</a> "Donald DUCK"</p><p><b>encounter</b>: <a href=\"encounter-example-f001-heart.html\">Encounter/f001: encounter who leads to this prescription</a></p><p><b>occurence</b>: 2015-01-15T14:30:00+01:00 --> (ongoing)</p><h3>Performers</h3><table class=\"grid\"><tr><td>-</td><td><b>Actor</b></td></tr><tr><td>*</td><td><a href=\"practitioner-example-f007-sh.html\">Practitioner/f007: Patrick Pump</a> "Simone HEPS"</td></tr></table><h3>Reasons</h3><table class=\"grid\"><tr><td>-</td><td><b>Concept</b></td></tr><tr><td>*</td><td>Given as Ordered <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-reason-medication-given.html\">Reason Medication Given Codes</a>#b)</span></td></tr></table><p><b>request</b>: <a href=\"medicationrequest0318.html\">MedicationRequest/medrx0318</a></p><h3>Dosages</h3><table class=\"grid\"><tr><td>-</td><td><b>Text</b></td><td><b>Route</b></td><td><b>Method</b></td><td><b>Dose</b></td></tr><tr><td>*</td><td>500mg IV q6h x 3 days</td><td>Intravenous route (qualifier value) <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"https://browser.ihtsdotools.org/\">SNOMED CT</a>#47625008)</span></td><td>IV Push <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> ()</span></td><td>500 mg<span style=\"background: LightGoldenRodYellow\"> (Details: UCUM code mg = 'mg')</span></td></tr></table><p><b>eventHistory</b>: <a name=\"signature\"> </a></p><blockquote><p/><p><a name=\"signature\"> </a></p><p><b>target</b>: <a href=\"servicerequest-example2.html\">ServiceRequest/physiotherapy</a></p><p><b>recorded</b>: 2 Feb 2017, 4:23:07 am</p><h3>Agents</h3><table class=\"grid\"><tr><td>-</td><td><b>Role</b></td><td><b>Who</b></td></tr><tr><td>*</td><td>author (originator) <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (<a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-v3-ParticipationType.html\">ParticipationType</a>#AUT)</span></td><td><a href=\"practitioner-example.html\">Practitioner/example: Dr Adam Careful</a> "Adam CAREFUL"</td></tr></table><h3>Signatures</h3><table class=\"grid\"><tr><td>-</td><td><b>Type</b></td><td><b>When</b></td><td><b>Who</b></td><td><b>TargetFormat</b></td><td><b>SigFormat</b></td><td><b>Data</b></td></tr><tr><td>*</td><td>Author's Signature (Details: urn:iso-astm:E1762-95:2013 code 1.2.840.10065.1.12.1.1 = 'Author's Signature', stated as 'Author's Signature')</td><td>2 Feb 2017, 4:23:07 am</td><td><a href=\"practitioner-example.html\">Practitioner/example: Dr Adam Careful</a> "Adam CAREFUL"</td><td>application/fhir+xml</td><td>application/signature+xml</td><td>dGhpcyBibG9iIGlzIHNuaXBwZWQ=</td></tr></table></blockquote></div>"
]; #
fhir:DomainResource.contained [
a fhir:Medication;
fhir:index 0;
fhir:Resource.id [ fhir:value "med0301" ];
fhir:Medication.code [
fhir:CodeableConcept.coding [
fhir:index 0;
fhir:Coding.system [ fhir:value "http://hl7.org/fhir/sid/ndc" ];
fhir:Coding.code [ fhir:value "0409-6531-02" ];
fhir:Coding.display [ fhir:value "Vancomycin Hydrochloride (VANCOMYCIN HYDROCHLORIDE)" ]
]
]
], [
a fhir:Provenance;
fhir:index 1;
fhir:Resource.id [ fhir:value "signature" ];
fhir:Provenance.target [
fhir:index 0;
fhir:Reference.reference [ fhir:value "ServiceRequest/physiotherapy" ]
];
fhir:Provenance.recorded [ fhir:value "2017-02-01T17:23:07Z"^^xsd:dateTime ];
fhir:Provenance.agent [
fhir:index 0;
fhir:Provenance.agent.role [
fhir:index 0;
fhir:CodeableConcept.coding [
fhir:index 0;
fhir:Coding.system [ fhir:value "http://terminology.hl7.org/CodeSystem/v3-ParticipationType" ];
fhir:Coding.code [ fhir:value "AUT" ]
]
];
fhir:Provenance.agent.who [
fhir:Reference.reference [ fhir:value "Practitioner/example" ];
fhir:Reference.display [ fhir:value "Dr Adam Careful" ]
]
];
fhir:Provenance.signature [
fhir:index 0;
fhir:Signature.type [
fhir:index 0;
fhir:Coding.system [ fhir:value "urn:iso-astm:E1762-95:2013" ];
fhir:Coding.code [ fhir:value "1.2.840.10065.1.12.1.1" ];
fhir:Coding.display [ fhir:value "Author's Signature" ]
];
fhir:Signature.when [ fhir:value "2017-02-01T17:23:07Z"^^xsd:dateTime ];
fhir:Signature.who [
fhir:Reference.reference [ fhir:value "Practitioner/example" ];
fhir:Reference.display [ fhir:value "Dr Adam Careful" ]
];
fhir:Signature.targetFormat [ fhir:value "application/fhir+xml" ];
fhir:Signature.sigFormat [ fhir:value "application/signature+xml" ];
fhir:Signature.data [ fhir:value "dGhpcyBibG9iIGlzIHNuaXBwZWQ="^^xsd:base64Binary ]
]
]; #
fhir:MedicationAdministration.status [ fhir:value "in-progress"]; #
fhir:MedicationAdministration.medication [
fhir:CodeableReference.reference [
fhir:Reference.reference [ fhir:value "#med0301" ]
]
]; #
fhir:MedicationAdministration.subject [
fhir:Reference.reference [ fhir:value "Patient/pat1" ];
fhir:Reference.display [ fhir:value "Donald Duck" ]
]; #
fhir:MedicationAdministration.encounter [
fhir:Reference.reference [ fhir:value "Encounter/f001" ];
fhir:Reference.display [ fhir:value "encounter who leads to this prescription" ]
]; #
fhir:MedicationAdministration.occurencePeriod [
fhir:Period.start [ fhir:value "2015-01-15T14:30:00+01:00"^^xsd:dateTime ]
]; #
fhir:MedicationAdministration.performer [
fhir:index 0;
fhir:MedicationAdministration.performer.actor [
fhir:Reference.reference [ fhir:value "Practitioner/f007" ];
fhir:Reference.display [ fhir:value "Patrick Pump" ]
]
]; #
fhir:MedicationAdministration.reason [
fhir:index 0;
fhir:CodeableReference.concept [
fhir:CodeableConcept.coding [
fhir:index 0;
fhir:Coding.system [ fhir:value "http://terminology.hl7.org/CodeSystem/reason-medication-given" ];
fhir:Coding.code [ fhir:value "b" ];
fhir:Coding.display [ fhir:value "Given as Ordered" ]
]
]
]; #
fhir:MedicationAdministration.request [
fhir:Reference.reference [ fhir:value "MedicationRequest/medrx0318" ]
]; #
fhir:MedicationAdministration.dosage [
fhir:MedicationAdministration.dosage.text [ fhir:value "500mg IV q6h x 3 days" ];
fhir:MedicationAdministration.dosage.route [
fhir:CodeableConcept.coding [
fhir:index 0;
a sct:47625008;
fhir:Coding.system [ fhir:value "http://snomed.info/sct" ];
fhir:Coding.code [ fhir:value "47625008" ];
fhir:Coding.display [ fhir:value "Intravenous route (qualifier value)" ]
]
];
fhir:MedicationAdministration.dosage.method [
fhir:CodeableConcept.text [ fhir:value "IV Push" ]
];
fhir:MedicationAdministration.dosage.dose [
fhir:Quantity.value [ fhir:value "500"^^xsd:decimal ];
fhir:Quantity.unit [ fhir:value "mg" ];
fhir:Quantity.system [ fhir:value "http://unitsofmeasure.org" ];
fhir:Quantity.code [ fhir:value "mg" ]
]
]; #
fhir:MedicationAdministration.eventHistory [
fhir:index 0;
fhir:Reference.reference [ fhir:value "#signature" ];
fhir:Reference.display [ fhir:value "Author's Signature" ]
]] . #
# - ontology header ------------------------------------------------------------
[a owl:Ontology;
owl:imports fhir:fhir.ttl] .
# -------------------------------------------------------------------------------------
Usage
note:
every
effort
has
been
made
to
ensure
that
the
examples
are
correct
and
useful,
but
they
are
not
a
normative
part
of
the
specification.
Medications
|
Propose
a
change
