This wiki has undergone a migration to Confluence found Here
Difference between revisions of "MedicationKnowledge FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 52: | Line 52: | ||
*This resource may be a kind of product as well as a specific instance of a product. | *This resource may be a kind of product as well as a specific instance of a product. | ||
| − | This resource is related to Medication, but contains additional attributes to fully describe a medication for different contexts - clinical decision support, payment/coverage, drug information. | + | *This resource is related to Medication, but contains additional attributes to fully describe a medication for different contexts - clinical decision support, payment/coverage, drug information. |
| − | Will be used in multiple environment including community pharmacies, hospital pharmacies, hospitals, prescriber offices, etc | + | *Will be used in multiple environment including community pharmacies, hospital pharmacies, hospitals, prescriber offices, etc |
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 71: | Line 71: | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
*medicationKnowledge corresponds to a manufactured product (MANU) role played by a manufactured material MMAT entity. The Common Product Model in the V3 ballot encompasses this scope but also provides much more. | *medicationKnowledge corresponds to a manufactured product (MANU) role played by a manufactured material MMAT entity. The Common Product Model in the V3 ballot encompasses this scope but also provides much more. | ||
| − | |||
==Resource appropriateness== | ==Resource appropriateness== | ||
*Products cannot be used if they cannot be identified and systems to establish and maintain queryable lists of products are widespread. For systems to interoperate they must have a shared basis for product identification as well as the characteristics of a medication. Characteristics can include attributes such as colour, markings, an image, as well as cost and formulary coverage. It may also be as broad as the clinical knowledge about a medication such as drug-drug interactions, dosing recommendations, and drug-allergy interactions. | *Products cannot be used if they cannot be identified and systems to establish and maintain queryable lists of products are widespread. For systems to interoperate they must have a shared basis for product identification as well as the characteristics of a medication. Characteristics can include attributes such as colour, markings, an image, as well as cost and formulary coverage. It may also be as broad as the clinical knowledge about a medication such as drug-drug interactions, dosing recommendations, and drug-allergy interactions. | ||
| − | |||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 96: | Line 94: | ||
**Clinical Decision Support systems | **Clinical Decision Support systems | ||
**Hospital Information Systems/EHRs | **Hospital Information Systems/EHRs | ||
| − | |||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| Line 113: | Line 110: | ||
*A prescriber or dispenser wants to query to get information about the coverage and cost of a particular drug. This resource can be used to query for the drug and a particular formulary. | *A prescriber or dispenser wants to query to get information about the coverage and cost of a particular drug. This resource can be used to query for the drug and a particular formulary. | ||
*A prescriber or dispenser wants to query to get potential equivalent products – for example, they can search using the ingredient(s) and strength to return branded products that contain the same set of ingredient(s) and strength(s) | *A prescriber or dispenser wants to query to get potential equivalent products – for example, they can search using the ingredient(s) and strength to return branded products that contain the same set of ingredient(s) and strength(s) | ||
| − | |||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| Line 120: | Line 116: | ||
*medicationKnowledge is expected to reference Substance, Organization, Medication | *medicationKnowledge is expected to reference Substance, Organization, Medication | ||
*This resource may be referenced by other resources such as CatalogEntry in the future | *This resource may be referenced by other resources such as CatalogEntry in the future | ||
| − | |||
<!-- What are the resources do you expect will reference this resource and in what context? | <!-- What are the resources do you expect will reference this resource and in what context? | ||
Revision as of 16:53, 19 September 2017
This page documents a Pending FHIR Resource Proposal
Contents
- 1 PutProposedResourceNameHere
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
- 1.15 FMG Notes
PutProposedResourceNameHere
MedicationKnowledge
Owning work group name
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups
- BR&R
- O&O
FHIR Resource Development Project Insight ID
- Pending
Scope of coverage
- Identification and characteristics of a Product consumed by Patients
- The scope of a MedicationKnowledge resource encompasses all the products that are conventionally understood to be medications or products consumed by patients including non-prescribed medication, herbal products, diet supplements, illicit drugs, and even some products that may be classified as devices. This resource is intended to include attributes that describe the medication including, but not limited to type, colour, image, cost, formulary coverage, etc.
- This resource may be a kind of product as well as a specific instance of a product.
- This resource is related to Medication, but contains additional attributes to fully describe a medication for different contexts - clinical decision support, payment/coverage, drug information.
- Will be used in multiple environment including community pharmacies, hospital pharmacies, hospitals, prescriber offices, etc
RIM scope
- medicationKnowledge corresponds to a manufactured product (MANU) role played by a manufactured material MMAT entity. The Common Product Model in the V3 ballot encompasses this scope but also provides much more.
Resource appropriateness
- Products cannot be used if they cannot be identified and systems to establish and maintain queryable lists of products are widespread. For systems to interoperate they must have a shared basis for product identification as well as the characteristics of a medication. Characteristics can include attributes such as colour, markings, an image, as well as cost and formulary coverage. It may also be as broad as the clinical knowledge about a medication such as drug-drug interactions, dosing recommendations, and drug-allergy interactions.
Expected implementations
- This resource is likely to be implemented by applications:
- Pharmacy Practice Management Systems
- Electronic Medical Records
- Clinical Decision Support systems
- Hospital Information Systems/EHRs
Content sources
- Existing normative V3 CPM RMIMs
- Existing specifications in Canada, The Netherlands and UK
- Some commercial systems
Example Scenarios
- A prescriber or dispenser wants to query to get information about the coverage and cost of a particular drug. This resource can be used to query for the drug and a particular formulary.
- A prescriber or dispenser wants to query to get potential equivalent products – for example, they can search using the ingredient(s) and strength to return branded products that contain the same set of ingredient(s) and strength(s)
Resource Relationships
- medicationKnowledge is expected to reference Substance, Organization, Medication
- This resource may be referenced by other resources such as CatalogEntry in the future
Timelines
- Ready for Comment only ballot – January 2018 ballot cycle
- STU status for STU4 publication
gForge Users
- Melva Peters
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
