MedicationStatement
FHIR Profile
The profile is accessible via MedicationStatement and presented below. The profile represents the record of antibiotics given to a patient, either before or after surgery.
This profile is based on the MedicationStatement base profile for FHIR version R4, see also MedicationStatement.
MedicationStatement | I | MedicationStatement | There are no (further) constraints on this element Element idMedicationStatement Record of medication being taken by a patient DefinitionA record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered: MedicationStatement.status + MedicationStatement.wasNotTaken Status=Active + NotTaken=T = Not currently taking Status=Completed + NotTaken=T = Not taken in the past Status=Intended + NotTaken=T = No intention of taking Status=Active + NotTaken=F = Taking, but not as prescribed Status=Active + NotTaken=F = Taking Status=Intended +NotTaken= F = Will be taking (not started) Status=Completed + NotTaken=F = Taken in past Status=In Error + NotTaken=N/A = In Error.
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.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 idMedicationStatement.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 idMedicationStatement.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 idMedicationStatement.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 idMedicationStatement.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 idMedicationStatement.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 | There are no (further) constraints on this element Element idMedicationStatement.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.
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.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.
|
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idMedicationStatement.identifier External identifier DefinitionIdentifiers associated with this Medication Statement 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.
|
basedOn | Σ | 0..* | Reference(MedicationRequest | CarePlan | ServiceRequest) | There are no (further) constraints on this element Element idMedicationStatement.basedOn Fulfils plan, proposal or order DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. Reference(MedicationRequest | CarePlan | ServiceRequest) Constraints
|
partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) | There are no (further) constraints on this element Element idMedicationStatement.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. This should not be used when indicating which resource a MedicationStatement has been derived from. If that is the use case, then MedicationStatement.derivedFrom should be used. Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) Constraints
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationStatement.status active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken DefinitionA code representing the patient or other source's judgment about the state of the medication used that this statement is about. Generally, this will be active or completed. MedicationStatement is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for MedicationStatement.status contains codes that assert the status of the use of the medication by the patient (for example, stopped or on hold) as well as codes that assert the status of the medication statement itself (for example, entered in error). This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A coded concept indicating the current status of a MedicationStatement.
|
statusReason | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationStatement.statusReason Reason for current status DefinitionCaptures the reason for the current state of the MedicationStatement. This is generally only used for "exception" statuses such as "not-taken", "on-hold", "cancelled" or "entered-in-error". The reason for performing the event at all is captured in reasonCode, not here. A coded concept indicating the reason for the status of the statement.
| |
category | Σ | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idMedicationStatement.category Type of medication usage DefinitionIndicates where the medication is expected to be consumed or administered. A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.category.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 idMedicationStatement.category.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
|
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idMedicationStatement.category.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.category.coding.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 idMedicationStatement.category.coding.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
|
system | Σ | 0..1 | uriFixed Value | Element idMedicationStatement.category.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.category.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | code | There are no (further) constraints on this element Element idMedicationStatement.category.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.category.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idMedicationStatement.category.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.category.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
medication[x] | Σ | 1..1 | There are no (further) constraints on this element Element idMedicationStatement.medication[x] What medication was taken DefinitionIdentifies the medication being 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. A coded concept identifying the substance or product being taken.
| |
medicationCodeableConcept | CodeableConcept | Data type | ||
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.medication[x].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 idMedicationStatement.medication[x].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
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMedicationStatement.medication[x].coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.medication[x].coding.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 idMedicationStatement.medication[x].coding.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
|
system | Σ | 0..1 | uriFixed Value | Element idMedicationStatement.medication[x].coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
|
version | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.medication[x].coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 0..1 | codeFixed Value | Element idMedicationStatement.medication[x].coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
68322007
|
display | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.medication[x].coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idMedicationStatement.medication[x].coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.medication[x].text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
subject | Σ | 1..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element idMedicationStatement.subject Who is/was taking the medication DefinitionThe person, animal or group who is/was taking the medication.
|
context | Σ | 1..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idMedicationStatement.context Encounter / Episode associated with MedicationStatement DefinitionThe encounter or episode of care that establishes the context for this MedicationStatement. Reference(Encounter | EpisodeOfCare) Constraints
|
effective[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationStatement.effective[x] The date/time or interval when the medication is/was/will be taken DefinitionThe interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No). This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the "end" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||
effectivePeriod | Period | There are no (further) constraints on this element Data type | ||
dateAsserted | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idMedicationStatement.dateAsserted When the statement was asserted? DefinitionThe date when the medication statement was asserted by the information source.
|
informationSource | 0..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idMedicationStatement.informationSource Person or organization that provided the information about the taking of this medication DefinitionThe person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Constraints
| |
derivedFrom | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationStatement.derivedFrom Additional supporting information DefinitionAllows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from.
| |
reasonCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationStatement.reasonCode Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. A coded concept identifying why the medication is being taken.
| |
reasonReference | 0..* | Reference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationStatement.reasonReference Condition or observation that supports why the medication is being/was taken DefinitionCondition or observation that supports why the medication is being/was taken. This is a reference to a condition that is the reason why the medication is being/was taken. If only a code exists, use reasonForUseCode. Reference(Condition | Observation | DiagnosticReport) Constraints
| |
note | 0..* | Annotation | There are no (further) constraints on this element Element idMedicationStatement.note Further information about the statement DefinitionProvides extra information about the medication statement that is not conveyed by the other attributes.
| |
dosage | 0..* | Dosage | There are no (further) constraints on this element Element idMedicationStatement.dosage Details of how medication is/was taken or should be taken DefinitionIndicates how the medication is/was or should be taken by the patient. The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, "from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily." It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest.
|
Mapping
Here is a list of the exact mapping for this FHIR Profile. The mapping includes the DICA variable and corresponding FHIR data element. In case of a DICA option set, the relation between the DICA options and available values within the FHIR data element are defined.
DICA variable | FHIR Data Element | DICA Option Set | Value DICA Option Set | Code |
---|---|---|---|---|
systantibiot | category.coding.code | 101 | 1/yes | 18286008 |
postopantibiot | category.coding.code | 101 | 1/yes | 430193006 |
Constraints
Constraints can refer to the cardinality of an element, required value or type of value.
The following constraints apply:
- When either systantibiot or postopantibiot are defined as "yes" for a patient, a separate MedicationStatement Resource is created.
- Hence, if both pre- and postsurgery antibiotics have been used, then create two MedicationStatement Resources.
- Element status is required. This element requires one of the following values: active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken. The terms 'completed' and 'not taken' refer to the status of antibiotic administration during procedures. 'Completed' indicates that antibiotics were administered, while 'not taken' signifies that they were not. This binary classification is used for data recording purposes within the registry. While some institutions have a standardized protocol for antibiotic administration, others leave it to the discretion of the individual surgeon. For the purposes of the DBIR registry, the antibiotic administration status must be recorded as either completed or not taken.
- Element category is required. In category.coding, the "system" subelement has fixed value "http://snomed.info/sct". The subelement "code" can hold one of the following two values: 18286008 (Administration of medication before a surgical procedure) or 430193006 (Administration of medication after a surgical procedure).
- Element medication is required. As both variables concern antibiotics, values for the medication.coding.code.system is set as "http://snomed.info/sct", with fixed value 68322007 (Administration of antibiotic) for element medication.coding.code.
- Element subject is required, referring to a Patient Resource.
- Element context is required, referring to the Encounter or EpisodeOfCare is which the medication was given.
Example MedicationStatement Resource
{ "resourceType":"MedicationStatement", "id":"ExampleMedicationStatement", "meta":{ "profile":[ "http://mrdm.nl/profiles/fhir/r4/dbir/StructureDefinition/MedicationStatement" ] }, "status":"completed", "medicationCodeableConcept":{ "coding":[ { "system":"http://snomed.info/sct", "code":"68322007", "display":"Administration of antibiotic (procedure)" } ] }, "subject":{ "reference":"Patient/pat1", "display":"Paula Janssen" }, "context":{ "reference":"Encounter/12324" }, "category":[ { "coding":[ { "system":"http://snomed.info/sct", "code":"430193006", "display":"Administration of medication after a surgical procedure" } ] } ], "effectiveDateTime":"2024-02-01", "dateAsserted":"2024-02-22" }