| Name | Value | Comments |
|---|
 abstract | false | |
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Medication | |
| copyright | | Used by permission of HL7 International, all rights reserved Creative Commons License | - Added the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
|
| date | 2016-10-18T00:00:00+11:00 | 2019-05-21 | |
| description | | When referencing a medication, the MedicationRequest resource can either use a code or refer to a Medication resource. This profile sets minimum expectations for the Medication resource to record, search, and fetch medications associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases | - Added the item 'When referencing a medication, the MedicationRequest resource can either use a code or refer to a Medication resource. This profile sets minimum expectations for the Medication resource to record, search, and fetch medications associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases'
|
| experimental | | false | |
| fhirVersion | 1.0.2 | 4.0.1 | |
| jurisdiction | | |
 jurisdiction[0] | | urn:iso:std:iso:3166#US | - Added the item 'urn:iso:std:iso:3166#US'
|
| kind | resource | |
| name | Argonaut Medication Profile | USCoreMedicationProfile | |
| publisher | Argonaut Project | HL7 International - Cross-Group Projects | |
| purpose | | |
| status | draft | active | |
| title | | US Core Medication Profile | - Added the item 'US Core Medication Profile'
|
| type | Medication | |
| url | http://fhir.org/guides/argonaut/StructureDefinition/argo-medication | http://hl7.org/fhir/us/core/StructureDefinition/us-core-medication | |
| version | | 6.0.0 | |
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments |
|---|
 Medication | | 0..* | Medication | Argonaut Medication Profile
| | 0..* | Medication | Definition of a Medication
| - Elements differ in short: 'Argonaut Medication Profile' vs 'Definition of a Medication'
- Elements differ in definition: 'This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication.' vs '\-'
- StructureDefinition USCoreMedicationProfile has added constraint that is not found in Argonaut Medication Profile and it is uncertain whether they are compatible (contained.contained.empty())
- StructureDefinition USCoreMedicationProfile has added constraint that is not found in Argonaut Medication Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
- StructureDefinition USCoreMedicationProfile has added constraint that is not found in Argonaut Medication Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
- StructureDefinition USCoreMedicationProfile has added constraint that is not found in Argonaut Medication Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
- StructureDefinition USCoreMedicationProfile has added constraint that is not found in Argonaut Medication Profile and it is uncertain whether they are compatible (text.`div`.exists())
|
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | - Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs '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 | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | - Elements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The 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 | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | - Elements differ in definition: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A 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.'
- Elements differ in comments: '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 as much as possible.' 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 it's narrative along with other profiles, value sets, etc.'
|
| language | | 0..1 | code | Language of the resource content
Binding: todo (required): A human language.
| | 0..1 | code | Language of the resource content
Binding: todo (preferred): A human language.
| - Elements differ in comments: '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).' vs '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).'
|
| text | | 0..1 | Narrative | Text summary of the resource, for human interpretation | | 0..1 | Narrative | Text summary of the resource, for human interpretation | - Elements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may 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.' vs 'A 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.'
- Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs '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 | Contained, inline Resources
| | 0..* | Resource | Contained, inline Resources
| - Elements differ in comments: '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.' 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.'
|
 extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. 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.' 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 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.'
|
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?! | 0..* | Extension | Extensions that cannot be ignored
| - Elements differ in definition: '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. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.' 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 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).'
|
| code | S | 1..1 | CodeableConcept | Codes that identify this medication
Binding: todo (extensible): Prescribable medications
| SΣ | 1..1 | CodeableConcept | (USCDI) Codes that identify this medication
Binding: todo (extensible) | - Elements differ in short: 'Codes that identify this medication' vs '(USCDI) Codes that identify this medication'
- Elements differ in definition: 'Used for identification and definition of a medication.' vs 'A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems.'
- Elements differ in comments: 'Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) should be marked as "primary". Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).' vs 'Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) will have the coding.userSelected set to true. As described in the coding datatype: "A coding may be marked as a "userSelected" if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).'
|
| isBrand | Σ | 0..1 | boolean | True if a brand | | | | | |
| manufacturer | Σ | 0..1 | Reference(Organization) | Manufacturer of the item | Σ | 0..1 | Reference(Organization) | Manufacturer of the item | - Elements differ in definition: 'Describes the details of the manufacturer.' vs 'Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product.'
|
| product | | 0..1 | BackboneElement | Administrable medication details | | | | | |
| package | | 0..1 | BackboneElement | Details about packaged medications | | | | | |
| identifier | | | | | Σ | 0..* | Identifier | Business identifier for this medication
| |
| status | | | | | ?!Σ | 0..1 | code | active | inactive | entered-in-error
Binding: todo (required): A coded concept defining if the medication is in active use.
| |
| form | | | | | | 0..1 | CodeableConcept | powder | tablets | capsule +
Binding: todo (example): A coded concept defining the form of a medication.
| |
| amount | | | | | Σ | 0..1 | Ratio | Amount of drug in package | |
| ingredient | | | | | | 0..* | BackboneElement | Active or inactive ingredient
| |
| batch | | | | | | 0..1 | BackboneElement | Details about packaged medications | |
Documentation for this format |