Insulinapplikation (MedicationAdministration)
Eine Insulinapplikation (InsulinAdministration) kann entweder manuell, in der ESYST-App, oder automatisch, durch den ESYSTA-Pen (device
), im System registriert werden. Bei der Registrierung von Insulin-Pens bei ESYSTA kann der Benutzer Attribute für diesen Pen angeben, wie z. B. den Typ (Erweiterung Type
) und die Marke des verwendeten Insulins (medication[x]
). Einige Insulin-Pens wie der ESYSTA-Pen können mit einem farbigen Marker zur einfachen Unterscheidung von verschiedener Pens gekennzeichnet werden (Erweiterung Color
). Die folgende Festlegung spezifiziert eine InsulinAdministration
. Diese enthält stets die gespritzte Menge (dosage
) und den zugehörigen Zeitstempel effective[x]
.
Kompatibilität
Dieses Profil basiert auf der Basisdefinition des FHIR MedicationAdminitration und wurde durch Einschränkungen spezifiziert. Instanzen müssen gegen das folgende FHIR-Profil valide sein.
FHIR-Profil (InsulinAdministration)
InsulinAdministration (MedicationAdministration) | I | MedicationAdministration | There are no (further) constraints on this element Element idMedicationAdministration Administration of medication to a patient DefinitionDescribes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationAdministration.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationAdministration.implicitRules A set of rules under which this content was created DefinitionA 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. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationAdministration.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idMedicationAdministration.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 0..* | Extension | Element idMedicationAdministration.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
Color | S I | 0..1 | Extension(code) | Element idMedicationAdministration.extension:Color Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. http://portal.esysta.com/fhir/StructureDefinition/InsulinPenMarkerColor Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.extension:Color.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idMedicationAdministration.extension:Color.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationAdministration.extension:Color.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://portal.esysta.com/fhir/StructureDefinition/InsulinPenMarkerColor
| |
value[x] | 1..1 | Binding | There are no (further) constraints on this element Element idMedicationAdministration.extension:Color.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). Unordered, Open, by $this(Type) BindingInsulinPenMarkerColorVS (required) Constraints
| |
valueCode | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.extension:Color.value[x]:valueCode Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). InsulinPenMarkerColorVS (required) Constraints
| |
Type | S I | 0..1 | Extension(code) | Element idMedicationAdministration.extension:Type Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. http://portal.esysta.com/fhir/StructureDefinition/InsulinType Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.extension:Type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idMedicationAdministration.extension:Type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationAdministration.extension:Type.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://portal.esysta.com/fhir/StructureDefinition/InsulinType
| |
value[x] | 1..1 | Binding | There are no (further) constraints on this element Element idMedicationAdministration.extension:Type.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). Unordered, Open, by $this(Type) Binding Constraints
| |
valueCode | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.extension:Type.value[x]:valueCode Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| |
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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's 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | S | 1..1 | Identifier | There are no (further) constraints on this element Element idMedicationAdministration.identifier External identifier DefinitionIdentifiers associated with this Medication Administration that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server. This is a business identifier, not a resource identifier.
|
instantiates | Σ | 0..* | uri | There are no (further) constraints on this element Element idMedicationAdministration.instantiates Instantiates protocol or definition DefinitionA protocol, guideline, orderset, or other definition that was adhered to in whole or in part by this event. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | Procedure) | There are no (further) constraints on this element Element idMedicationAdministration.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(MedicationAdministration | Procedure) Constraints
|
status | S Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.status in-progress | not-done | on-hold | completed | entered-in-error | stopped | unknown DefinitionWill generally be set to show that the administration has been completed. For some long running administrations such as infusions, it is possible for an administration to be started but not completed or it may be paused while some other process is under way. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A set of codes indicating the current status of a MedicationAdministration.
|
statusReason | S | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.statusReason Reason administration not performed DefinitionA code indicating why the administration was not performed. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A set of codes indicating the reason why the MedicationAdministration is negated.
|
category | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idMedicationAdministration.category Type of medication usage DefinitionIndicates where the medication is expected to be consumed or administered. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing where the medication administered is expected to occur.
| |
medication[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationAdministration.medication[x] What was administered DefinitionIdentifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource. Unordered, Open, by $this(Type) BindingCodes identifying substance or product that can be administered.
| |
(All Slices) | There are no (further) constraints on this element | |||
medicationReference | Reference(Medication) | There are no (further) constraints on this element Data type | ||
medicationCodeableConcept | S Σ | 1..1 | CodeableConceptBinding | Element idMedicationAdministration.medication[x]:medicationCodeableConcept What was administered DefinitionIdentifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications. If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource. Codes identifying substance or product that can be administered.
|
subject | S Σ I | 1..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element idMedicationAdministration.subject Who received medication DefinitionThe person or animal or group receiving the medication. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
context | I | 0..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idMedicationAdministration.context Encounter or Episode of Care administered as part of DefinitionThe visit, admission, or other contact between patient and health care provider during which the medication administration was performed. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Encounter | EpisodeOfCare) Constraints
|
supportingInformation | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationAdministration.supportingInformation Additional information to support administration DefinitionAdditional information (for example, patient height and weight) that supports the administration of the medication. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
effective[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationAdministration.effective[x] Start and end time of administration DefinitionA specific date/time or interval of time during which the administration took place (or did not take place, when the 'notGiven' attribute is true). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate. Unordered, Open, by $this(Type) Constraints
| |
(All Slices) | There are no (further) constraints on this element | |||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||
effectiveDateTime | S Σ | 1..1 | dateTime | Element idMedicationAdministration.effective[x]:effectiveDateTime Start and end time of administration DefinitionA specific date/time or interval of time during which the administration took place (or did not take place, when the 'notGiven' attribute is true). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate.
|
performer | Σ | 0..* | BackboneElement | There are no (further) constraints on this element Element idMedicationAdministration.performer Who performed the medication administration and what they did DefinitionIndicates who or what performed the medication administration and how they were involved.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.performer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.performer.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.performer.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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's 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
function | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.performer.function Type of performance DefinitionDistinguishes the type of involvement of the performer in the medication administration. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A code describing the role an individual played in administering the medication.
| |
actor | Σ I | 1..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson | Device) | There are no (further) constraints on this element Element idMedicationAdministration.performer.actor Who performed the medication administration DefinitionIndicates who or what performed the medication administration. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Patient | RelatedPerson | Device) Constraints
|
reasonCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.reasonCode Reason administration performed DefinitionA code indicating why the medication was given. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A set of codes indicating the reason why the MedicationAdministration was made.
| |
reasonReference | I | 0..* | Reference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationAdministration.reasonReference Condition or observation that supports why the medication was administered DefinitionCondition or observation that supports why the medication was administered. This is a reference to a condition that is the reason for the medication request. If only a code exists, use reasonCode. Reference(Condition | Observation | DiagnosticReport) Constraints
|
request | I | 0..1 | Reference(MedicationRequest) | There are no (further) constraints on this element Element idMedicationAdministration.request Request administration performed against DefinitionThe original request, instruction or authority to perform the administration. This is a reference to the MedicationRequest where the intent is either order or instance-order. It should not reference MedicationRequests where the intent is any other value.
|
device | S I | 0..* | Reference(Device) | There are no (further) constraints on this element Element idMedicationAdministration.device Device used to administer DefinitionThe device used in administering the medication to the patient. For example, a particular infusion pump. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
note | S | 0..* | Annotation | There are no (further) constraints on this element Element idMedicationAdministration.note Information about the administration DefinitionExtra information about the medication administration that is not conveyed by the other attributes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
|
dosage | S I | 1..1 | BackboneElement | There are no (further) constraints on this element Element idMedicationAdministration.dosage Details of how medication was taken DefinitionDescribes the medication dosage information details e.g. dose, rate, site, route, etc.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.dosage.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.dosage.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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's 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
text | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.text Free text dosage instructions e.g. SIG DefinitionFree text dosage can be used for cases where the dosage administered is too complex to code. When coded dosage is present, the free text dosage may still be present for display to humans. The dosage instructions should reflect the dosage of the medication that was administered. Note that FHIR strings SHALL NOT exceed 1MB in size
| |
site | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.site Body site administered to DefinitionA coded specification of the anatomic site where the medication first entered the body. For example, "left arm". If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body.
| |
route | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.route Path of substance into body DefinitionA code specifying the route or physiological path of administration of a therapeutic agent into or onto the patient. For example, topical, intravenous, etc. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
| |
method | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationAdministration.dosage.method How drug was administered DefinitionA coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. For example, Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequently. A coded concept describing the technique by which the medicine is administered.
| |
dose | S I | 1..1 | SimpleQuantity | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose Amount of medication per dose DefinitionThe amount of the medication given at one administration event. Use this value when the administration is essentially an instantaneous event such as a swallowing a tablet or giving an injection. If the administration is not instantaneous (rate is present), this can be specified to convey the total amount administered over period of time of a single administration.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
value | S Σ | 1..1 | decimal | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.value Numerical value (with implicit precision) DefinitionThe value of the measured amount. The value includes an implicit precision in the presentation of the value. Precision is handled implicitly in almost all cases of measurement. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).
|
comparator | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.comparator < | <= | >= | > - how to understand the value DefinitionNot allowed to be used in this context Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology. Note that FHIR strings SHALL NOT exceed 1MB in size If there is no comparator, then there is no modification of the value How the Quantity should be understood and represented.
|
unit | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.unit Unit representation DefinitionA human-readable form of the unit. There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms. Note that FHIR strings SHALL NOT exceed 1MB in size
|
system | Σ I | 0..1 | uri | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.system System that defines coded unit form DefinitionThe identification of the system that provides the coded form of the unit. Need to know the system that defines the coded form of the unit. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idMedicationAdministration.dosage.dose.code Coded form of the unit DefinitionA computer processable form of the unit in some unit representation system. Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.
|
rate[x] | 0..1 | There are no (further) constraints on this element Element idMedicationAdministration.dosage.rate[x] Dose quantity per unit of time DefinitionIdentifies the speed with which the medication was or will be introduced into the patient. Typically, the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time, e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. If the rate changes over time, and you want to capture this in MedicationAdministration, then each change should be captured as a distinct MedicationAdministration, with a specific MedicationAdministration.dosage.rate, and the date time when the rate change occurred. Typically, the MedicationAdministration.dosage.rate element is not used to convey an average rate.
| ||
rateRatio | Ratio | There are no (further) constraints on this element Data type | ||
rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data type | ||
eventHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idMedicationAdministration.eventHistory A list of events of interest in the lifecycle DefinitionA summary of the events of interest that have occurred, such as when the administration was verified. This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.
|
ValueSet 'InsulinPreparationVS'
Version | 0.0.1 |
Published by | Emperra GmbH E-Health Technologies |
Status | Active |
Experimental | True |
Contact Information
Emperra GmbH E-Health Technologies
Website: https://emperra.com
This value set includes codes from the following code systems:
- Import all codes from CodeSystem InsulinPreparationCS
ValueSet 'InsulinPenMarkerColorVS'
Version | 0.0.1 |
Published by | Emperra GmbH E-Health Technologies |
Status | Active |
Experimental | True |
Contact Information
Emperra GmbH E-Health Technologies
Website: https://emperra.com
This value set includes codes from the following code systems:
The following codes from system: SNOMED_CT
Code Display 371240000 Red 371244009 Yellow 371246006 Green 405738005 Blue
Erweiterung (InsulinPenMarkerColor)
InsulinPenMarkerColor (Extension) | I | Extension | There are no (further) constraints on this element Element idExtension Optional Extensions Element DefinitionOptional Extension Element - found in all resources.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idExtension.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idExtension.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | Element idExtension.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://portal.esysta.com/fhir/StructureDefinition/InsulinPenMarkerColor
| |
value[x] | 1..1 | Binding | Element idExtension.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list). InsulinPenMarkerColorVS (required) Constraints
| |
valueCode | code | Data type |
Erweiterung (InsulinType)
InsulinType (Extension) | I | Extension | There are no (further) constraints on this element Element idExtension Optional Extensions Element DefinitionOptional Extension Element - found in all resources.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idExtension.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..0 | Extension | There are no (further) constraints on this element Element idExtension.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | Element idExtension.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://portal.esysta.com/fhir/StructureDefinition/InsulinType
| |
value[x] | 1..1 | Binding | Element idExtension.value[x] Value of extension DefinitionValue of extension - must be one of a constrained set of the data types (see Extensibility for a list).
| |
valueCode | code | Data type |
ValueSet 'InsulinTypeVS'
Version | 0.0.1 |
Published by | Emperra GmbH E-Health Technologies |
Status | Active |
Experimental | True |
Contact Information
Emperra GmbH E-Health Technologies
Website: https://emperra.com
This value set includes codes from the following code systems:
Beispiel
Fiktives Beispiel einer validen InsulinAdministration Instanz:
<MedicationAdministration xmlns="http://hl7.org/fhir"> <id value="insulin-911" /> <meta> <profile value="http://portal.esysta.com/fhir/StructureDefinition/InsulinAdministration" /> </meta> <extension url="http://portal.esysta.com/fhir/StructureDefinition/InsulinPenMarkerColor"> <valueCode value="405738005" /> </extension> <extension url="http://portal.esysta.com/fhir/StructureDefinition/InsulinType"> <valueCode value="255361000" /> </extension> <identifier> <use value="official" /> <system value="http://portal.esysta.com/fhir/MedicationAdministration/" /> <value value="insulin-911" /> </identifier> <status value="completed" /> <medicationCodeableConcept> <coding> <system value="http://portal.esysta.com/fhir/CodeSystem/InsulinPreparationCS" /> <code value="23" /> <display value="Lantus®" /> </coding> </medicationCodeableConcept> <subject> <reference value="Patient/patient-1" /> </subject> <effectiveDateTime value="2021-03-17T15:58:00.725727Z" /> <device> <reference value="Device/device-3P4712" /> </device> <note> <text value="Ich habe mir zu wenig Insulin gespritzt. Ich fühle mich on FHIR!" /> </note> <dosage> <dose> <value value="17" /> <unit value="IU" /> <system value="http://snomed.info/sct" /> <code value="258997004" /> </dose> </dosage> </MedicationAdministration>