Generated Narrative: StructureDefinition MedicationTreatmentLineLM Name Flags Card. Type Description & Constraints MedicationTreatmentLineLM 0..* Base Medication Treatment Line (model) Instances of this logical model can be the target of a Reference #xD; identifier 0..* Identifier Unique business identifier(s) for the medication treatment line #xD; medication[x] 1..1 Medicinal product for which the treatment line refers to. Identification or sufficient description of the product. #xD; medicationCodeableConcept CodeableConcept #xD; medicationReference Reference(Medicinal product (model)) #xD; status 1..1 CodeableConcept Status of the treatment line entry #xD; version 0..1 string Business version of the treatment line #xD; timestamp 0..1 dateTime Timestamp of the version of the treatment line #xD; treatmentStatus 0..1 CodeableConcept The state of the actual treatment - taking, not taken... #xD; treatmentStatusReasonCode 0..1 CodeableConcept The reason - coded - for the treatment status - i.e. adverse events, refusal... #xD; treatmentStatusReasonText 0..1 string The reason - free text - for the treatment status - i.e. adverse events, refusal... #xD; effectivePeriod 0..1 BackboneElement The period of time the treatment is in effect #xD; verificationInformation 0..* BackboneElement Verification of medication line #xD; verifier 1..1 Reference() HCP (or device, if authorized) verifying the treatments/overview #xD; verificationTime 1..1 dateTime The date and time when this medication treatment line was verified #xD; category 0..* CodeableConcept Whatever category for the treatment line. Categorisation of treatment lines is implementation-specific. #xD; medicationTreatment 0..* Reference(Medication Treatment (model)) Reference or identifier of the group of lines that belong together #xD; indication 0..* CodeableConcept Reason why the product has been prescribed to the patient, or why the patient claims to be taking it #xD; indicationText 0..1 string Textual explanation for why the medication has been prescribed or why the patient is taking it. This might not be allowed by some implementations. #xD; intendedUse 0..1 CodeableConcept Intended Use of the medication - prophylaxis, therapy... #xD; usageInstructions 0..* DosagingInformation Instructions about administration of the product #xD; preparationInstructions 0..* string Additional instructions about preparation or dispense #xD; comment 0..* BackboneElement Comment on the individual line #xD; author 1..1 Reference() Author of the comment (Pharmacist, doctor, social carer, patient, device, related person) #xD; date 1..1 dateTime time of comment #xD; commentText 1..1 string content of the comment #xD; substitution 0..1 BackboneElement Whether and which type of substitution is allowed for this medication treatment line #xD; substitutionType 1..1 CodeableConcept The type of substitution that is allowed. #xD; substitutionTypeReason 0..1 CodeableConcept Coded reason for the substitution requirement #xD; substitutionTypeReasonText 0..1 string Textual reason for the substitution requirement #xD; recordingMetadata 1..1 BackboneElement Metadata about reporting/authoring of the treatment line #xD; recorder 1..1 Reference() Person entering the statement by initiating a treatment or documenting a statement by a patient or another professional. The recorder may be different from the author. #xD; recordedTime 1..1 dateTime Time of creation of the treatment line #xD; patientReported 0..1 boolean The treatment line has been documented according to patient's statement #xD; responsibleAuthor 0..1 Reference(Practitioner (model)) HCP who takes the clinical decision for the medication treatment line. If an author is not present, the responsibility of the medication line is with the recorder. #xD; authoringTime 0..1 dateTime The time the clinical decision was made by the responsibleAuthor. Normally, the same time as recording time when it's the same person. #xD; derivedFrom 0..* BackboneElement Any data object that this treatment line is derived from #xD; request 0..* Reference() Prescriptions that have been the source for creating the unverified treatment line #xD; statement 0..* Reference() Medication-related statements from patients, pharmacists, or other HCPs, that are the source for creating the unverified treatment line #xD; dispensation 0..* Reference() Related dispensations that are not necessarily related to existing prescriptions/requests/statements. #xD; administration 0..* Reference() Related administrations that are not necessarily related to existing prescriptions/requests/statements. #xD; other 0..* Reference() Other related sources of information - CarePlan, Immunizations, Documents (e.g. Discharge letters)... #xD; Documentation for this format
Integrating the Healthcare Enterprise (IHE)
Logical model for representing one line/medication in medication overview.
IHE http://www.ihe.net/Governance/#Intellectual_Property
Unique business identifier(s) for the medication treatment line
Medicinal product for which the treatment line refers to. Identification or sufficient description of the product.
Status of the record, not the status of the treatment.
Timestamp of the version of the treatment line
The state of the actual treatment - taking, not taken...
The reason - coded - for the treatment status - i.e. adverse events, refusal...
The reason - free text - for the treatment status - i.e. adverse events, refusal...
The period of time the treatment is in effect
Verification of medication line. The overview is verified as a whole, but each line is equipped with the information. The actual functional meaning and impact of this validation depends on the implementation.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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 managable, 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.
Must have either extensions or value[x], not both
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
HCP (or device, if authorized) verifying the treatments/overview
The date and time when this medication treatment line was verified
Whatever category for the treatment line. Categorisation of treatment lines is implementation-specific.
Reference or identifier of the group of lines that belong together
Reason why the product has been prescribed to the patient, or why the patient claims to be taking it
Textual explanation for why the medication has been prescribed or why the patient is taking it. This might not be allowed by some implementations.
Intended Use of the medication - prophylaxis, therapy...
Instructions about administration of the product
Instructions about requested or actual administration of the product. This is repeatable to support complex or concurrent dosage instructions. e.g. take 1 per day for 3 weeks; 2x PRN
Additional instructions about preparation or dispense
Author of the comment (Pharmacist, doctor, social carer, patient, device, related person)
Whether and which type of substitution is allowed for this medication treatment line
The type of substitution that is allowed.
Coded reason for the substitution requirement
Textual reason for the substitution requirement
Metadata about reporting/authoring of the treatment line
Person entering the statement by initiating a treatment or documenting a statement by a patient or another professional. The recorder may be different from the author.
The treatment line has been documented according to patient's statement
HCP who takes the clinical decision for the medication treatment line. If an author is not present, the responsibility of the medication line is with the recorder.
The time the clinical decision was made by the responsibleAuthor. Normally, the same time as recording time when it's the same person.
Any data object that this treatment line is derived from
Prescriptions that have been the source for creating the unverified treatment line
Medication-related statements from patients, pharmacists, or other HCPs, that are the source for creating the unverified treatment line
Related dispensations that are not necessarily related to existing prescriptions/requests/statements.
Related administrations that are not necessarily related to existing prescriptions/requests/statements.
Other related sources of information - CarePlan, Immunizations, Documents (e.g. Discharge letters)...