| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/uv/ips/StructureDefinition/MedicationStatement-uv-ips' vs 'http://hl7.eu/fhir/base-r5/StructureDefinition/medicationStatement-eu-core' |
| Error | StructureDefinition.version | Values for version differ: '2.0.0' vs '2.0.0-ballot' |
| Information | StructureDefinition.name | Values for name differ: 'MedicationStatementIPS' vs 'MedicationStatementEuCore' |
| Information | StructureDefinition.title | Values for title differ: 'MedicationStatement (IPS)' vs 'MedicationStatement (EU core)' |
| Information | StructureDefinition.date | Values for date differ: '2024-06-19T10:50:07-05:00' vs '2025-12-22T08:19:43+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Patient Care' vs 'HL7 Europe' |
| Information | StructureDefinition.jurisdiction | Removed the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#001' |
| Information | StructureDefinition.jurisdiction | Added the item 'http://unstats.un.org/unsd/methods/m49/m49.htm#150' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '5.0.0' |
| Information | StructureDefinition.definition | Values for definition differ: 'A 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.' vs 'A 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 medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement 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.
The MedicationStatement resource was previously called MedicationStatement.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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 its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'Contained resources do not have a 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These 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.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May 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.' vs 'May 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 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May 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).' vs 'May 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 managable, 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).' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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/R4/extensibility.html#modifierExtension).' vs '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).' |
| Information | StructureDefinition.short | Values for short differ: 'External identifier' vs 'Medication Statement Identifier' |
| Information | StructureDefinition.definition | Values for definition differ: 'A larger event of which this particular event is a component or step.' vs 'A larger event of which this particular MedicationStatement is a component or step.' |
| Error | MedicationStatement.partOf | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationAdministration|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationDispense|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationStatement|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure|4.0.1], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation|4.0.1]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Procedure|5.0.0], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationStatement|5.0.0]]) |
| Information | StructureDefinition.short | Values for short differ: 'active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken' vs 'State of the medication' |
| Information | StructureDefinition.definition | Values for definition differ: 'A 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.' vs 'A code representing the status of recording the medication statement.' |
| Information | StructureDefinition.comment | Values for comment differ: 'In the scope of the IPS the entered-in-error concept is not allowed.' vs 'This status concerns just the recording of the medication statement. MedicationStatement.adherence should be used for indicating a patient's adherence to the information in this resource. Note, the statuses are different than in previous releases for MedicationStatement or MedicationStatement.
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.' |
| Information | StructureDefinition.short | Values for short differ: 'Type of medication usage' vs 'Type of intended use' |
| Information | StructureDefinition.definition | Values for definition differ: 'Indicates where the medication is expected to be consumed or administered.' vs 'Type of medication statement (for example, drug classification like ATC, where meds would be administered, legal category of the medication.).' |
| Information | MedicationStatement.category | Element maximum cardinalities differ: '1' vs '2147483647' |
| Information | MedicationStatement.category | Example/preferred bindings differ at MedicationStatement.category using binding from MedicationStatementIPS |
| Warning | MedicationStatement.subject | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.definition | Values for definition differ: 'The 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).' vs 'The 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.adherence element is Not Taking).' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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 and is expected to continue indefinitely at the time the usage is recorded, the 'end' date will be omitted. If the end date is known, then it is included as the 'end date'. 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.' |
| Warning | MedicationStatement.effective[x] | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | MedicationStatement.effective[x] | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'When the statement was asserted?' vs 'When the usage was asserted?' |
| Information | StructureDefinition.definition | Values for definition differ: 'The date when the medication statement was asserted by the information source.' vs 'The date when the Medication Statement was asserted by the information source.' |
| Information | MedicationStatement.informationSource | Element maximum cardinalities differ: '1' vs '2147483647' |
| Information | StructureDefinition.short | Values for short differ: 'Additional supporting information' vs 'Link to information used to derive the MedicationStatement' |
| Error | MedicationStatement.derivedFrom | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource|4.0.1]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource|5.0.0]]) |
| Information | StructureDefinition.short | Values for short differ: 'Further information about the statement' vs 'Further information about the usage' |
| Information | StructureDefinition.definition | Values for definition differ: 'Provides extra information about the medication statement that is not conveyed by the other attributes.' vs 'Provides extra information about the Medication Statement that is not conveyed by the other attributes.' |
| Information | StructureDefinition.short | Values for short differ: 'Details of how medication is/was taken or should be taken' vs 'Details of how medication is/was taken or should be taken.' |
| Warning | MedicationStatement.dosage | Elements differ in definition for mustSupport: 'true' vs 'false' |
abstract
jurisdiction[0]
jurisdiction[1]
MedicationStatement
extension
modifierExtension
