FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
Query
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
API
-
Project FHIR API
This is the location where you can find your resource using a FHIR client.
-
Simplifier FHIR API
The global endpoint is where users can search for all resources in Simplifier. Resources have a globally unique guid Id here.
Tools
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
Project Capital
HdBe MedicationAgreement
A medication agreement is a prescriber’s proposal for a patient to use medication. An agreement to discontinue the use of medication is also a medication agreement.
Purpose
The goal of the medication agreement is to provide insight into the agreements reached between the prescriber and the patient on the use of medication.
Instructions
MedicationAgreementAdditionalInformation: When choosing a medicine, you can deviate from what is expected or from what the standard is. For example, when the hospital uses a different formulary than the community pharmacy. For reasons of efficiency, for example, one gastric acid inhibitor has been chosen in the hospital: pantoprazole. Upon admission, a patient with omeprazole is converted to pantoprazole for the duration of the stay. When discharged, the patient goes back to omeprazole. It is clear that something can go wrong here and that the patient takes both omeprazole and pantoprazole when there is no intervention. In the hospital's medication agreement for pantoprazole a remark can be made about the deviation so that it is clear that pantoprazole is the substitute for omeprazole or that it should be used in addition to omeprazole. Another example are the half strengths. The hospital sometimes stocks tablets with half the strength of the normal trade preparation (own production). The patient enters the hospital on 25 mg chlortalidone, half a tablet once a day, he receives 12.5 mg intramural chlortalidone, one tablet once a day. Then the nursing does not have to break tablets in this case. Here there is a risk that the patient will use the 25 mg again at home, but then a whole tablet at a time in stead of half a tablet. By means of an explanation in the medication agreement (Additional information) of the last chlortalidone 25 mg, it can be indicated whether this has been an intended increase.
- type LogicalModel
- FHIR R4
- status Draft
-
version...
- abstract
Unregistered conflicting canonical
The canonical from this resource does not match any claim in this context and conflicts with a claim from another scope.
https://fhir.healthdata.be/
Canonical claims are used to verify ownership of your canonical URLs.
Canonical
default
nl-NL
fr-BE
| HdBeMedicationAgreement (MedicationAgreement) | Element | Element idMedicationAgreement MedicationAgreement DefinitionRoot concept of the MedicationAgreement information model. This root concept contains all data elements of the MedicationAgreement information model.
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idMedicationAgreement.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idMedicationAgreement.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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| Prescriber | I | 0..1 | Reference(HdBeHealthProfessional) | Element idMedicationAgreement.Prescriber Prescriber DefinitionThe health professional that entered the medication agreement with the patient. 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(HdBeHealthProfessional) Constraints
|
| PrescriptionReason | I | 0..1 | Reference(HdBeProblem) | Element idMedicationAgreement.PrescriptionReason PrescriptionReason DefinitionThe medical reason for the prescription or for use of the medication. This can be used to enter a medical indication which was the direct cause for prescription or for use of the medication in question. It can concern every type of problem (or condition) of the patient, almost all diagnoses, complaints or symptoms. 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.
|
| AgreedMedicine | I | 1..1 | Reference(HdBePharmaceuticalProduct) | Element idMedicationAgreement.AgreedMedicine AgreedMedicine DefinitionThe medicine agreed upon to be used. 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(HdBePharmaceuticalProduct) Constraints
|
| InstructionsForUse | 0..1 | HdBeInstructionsForUse | Element idMedicationAgreement.InstructionsForUse InstructionsForUse DefinitionInstructions for the use of the medication, e.g. dose and route of administration.
| |
| MedicationAgreementDateTime | 1..1 | dateTime | Element idMedicationAgreement.MedicationAgreementDateTime MedicationAgreementDateTime DefinitionThe time at which the agreement was made. Appointment date + time are required (order of the appointments must be clear in cases with multiple appointments on one day)
| |
| PeriodOfUse | 0..1 | HdBeTimeInterval | Element idMedicationAgreement.PeriodOfUse PeriodOfUse DefinitionStart date: This is the time at which the agreement was to take effect (or took effect or will take effect). This is the time at which the instructions for use in this agreement start. In the case of an agreement to discontinue use, this is the start date of the original medication agreement. The end date indicates from when the medication is to be discontinued. Duration: The intended duration of use. E.g. 5 days or 8 weeks. It is not allowed to indicate the duration in months, because different months have a variable duration in days. End date: The time at which the period of use ends (or ended or will end). In the case of an agreement to discontinue use, this is the time at which the medication is to be discontinued. To avoid confusion between 'to' and 'up to', the submission of time is always mandatory for the end date. With medication for an indefinite period only a start date is indicated.
| |
| MedicationAgreementStopType | 0..1 | CodeableConceptBinding | Element idMedicationAgreement.MedicationAgreementStopType MedicationAgreementStopType DefinitionStop type, the manner in which this medication is discontinued (temporary or definitive). 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. MedicationAgreementStopType codes
| |
| ReasonMedicationAgreement | 0..1 | CodeableConceptBinding | Element idMedicationAgreement.ReasonMedicationAgreement ReasonMedicationAgreement DefinitionReason for this agreement. This can be the reason to start, change or stop the medication treatment. 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. ReasonMedicationAgreement codes
| |
| MedicationAgreementAdditionalInformation | 0..* | CodeableConceptBinding | Element idMedicationAgreement.MedicationAgreementAdditionalInformation MedicationAgreementAdditionalInformation DefinitionAdditional information includes details on the structure of the agreement made that are relevant for pharmacovigilance and fulfillment by the pharmacist. This can be used e.g. to indicate that there was a conscious decision to deviate from the norm or that the agreement is to be structured in a certain way. See also the Instructions section for more information about use of the element. 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. MedicationAgreementAdditionalInformation codes
| |
| Comment | 0..1 | string | Element idMedicationAgreement.Comment Comment DefinitionComments regarding to the medication agreement. For example: in consultation with the medical specialist. Note that FHIR strings may not exceed 1MB in size
|
Documentation:
https://simplifier.net/capital/hdbemedicationagreement
Last updated on