| Package | pharmacyeclaim.two |
| Resource Type | StructureDefinition |
| Id | profile-prescription |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=pharmacyeclaim.two@1.0.2-preview&canonical=http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-prescription |
| URL | http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-prescription |
| Status | draft |
| Name | Prescription |
| Title | Prescription |
| Description | This resource contains key information about the prescription data in support of the claim request. |
| Purpose | Prescription Details |
| Type | MedicationRequest |
| Kind | resource |
| StructureDefinition | |
| profile-claim-dispense | Claim Request for Dispense |
No resources found
No narrative content found in resource
FHIR{
"resourceType": "StructureDefinition",
"id": "profile-prescription",
"url": "http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-prescription",
"name": "Prescription",
"title": "Prescription",
"status": "draft",
"description": "This resource contains key information about the prescription data in support of the claim request.",
"purpose": "Prescription Details",
"fhirVersion": "4.0.1",
"kind": "resource",
"abstract": false,
"type": "MedicationRequest",
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/MedicationRequest",
"derivation": "constraint",
"differential": {
"element": [
{
"id": "MedicationRequest.id",
"path": "MedicationRequest.id",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier",
"path": "MedicationRequest.identifier",
"slicing": {
"discriminator": [
{
"type": "type",
"path": "type.coding.code"
}
],
"rules": "open"
},
"comment": "Usage Note: There must be least one identifier for the presciption (type=FILL) that is the Current RX Number ). A second one may be included, as directed by provincial implementers, to capture the provincial prescription number (type=JRX). For secondary payors identified in the claim, where the provincial plan is primary, this identifier may also be included.\r\n \r\n\r\nCPHA Mapping: Current RX number, D.55.03\r\nNo mapping from CPHA to a provincial prescription number \r\n\r\nThis is a business identifier, not a resource identifier.",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier.type",
"path": "MedicationRequest.identifier.type",
"comment": "Conformance Rule: Set value for code system = http://terminology.hl7.org/CodeSystem/v2-0203\" Set value of PrescribeITRX when the identifier is assigned by PrescribeIT. Set value = \"JRX\" (extensible) to indicate the jurisdictional prescription number.\r\n\r\nThis element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.identifier.system",
"path": "MedicationRequest.identifier.system",
"min": 1,
"fixedUri": "http://terminology.hl7.org/CodeSystem/v2-0203",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier.value",
"path": "MedicationRequest.identifier.value",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX",
"path": "MedicationRequest.identifier",
"sliceName": "PrescribeITRX",
"max": "1",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX.type",
"path": "MedicationRequest.identifier.type",
"comment": "Usage: Indicates that this identifier was issued by the order Filler (aka the Pharmacy)\r\n\r\nThis element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX.type.coding",
"path": "MedicationRequest.identifier.type.coding",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX.type.coding.code",
"path": "MedicationRequest.identifier.type.coding.code",
"min": 1,
"fixedCode": "PrescribeITRX",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX.system",
"path": "MedicationRequest.identifier.system",
"comment": "Usage Note: Must be populated. Essential for ensuring global uniqueness for this identifier\r\nCPHA Map Rule: This is a new field. \r\n\r\nIdentifier.system is always case sensitive.",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:PrescribeITRX.value",
"path": "MedicationRequest.identifier.value",
"comment": "Usage Note: If known, the PrescribeIT identiifer must be included\r\n\r\nIf the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID",
"path": "MedicationRequest.identifier",
"sliceName": "JurisdictionalRXID",
"comment": "Usage Note: This is the Jurisdictional Prescription Number and must be conveyed where known.\r\nThis is a business identifier, not a resource identifier.",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID.type",
"path": "MedicationRequest.identifier.type",
"min": 1,
"fixedCodeableConcept": {
"coding": [
{
"code": "JRX"
}
]
},
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID.type.coding",
"path": "MedicationRequest.identifier.type.coding",
"min": 1,
"max": "1",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID.type.coding.code",
"path": "MedicationRequest.identifier.type.coding.code",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID.system",
"path": "MedicationRequest.identifier.system",
"comment": "CPHA Map: This is a new field\r\nUsage: Must be provided if known\r\nIdentifier.system is always case sensitive.",
"mustSupport": true
},
{
"id": "MedicationRequest.identifier:JurisdictionalRXID.value",
"path": "MedicationRequest.identifier.value",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.intent",
"path": "MedicationRequest.intent",
"comment": "Usage Note: Set value = \"order\"\r\n\r\nIt is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.\r\rAn instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.\r\rThis element is labeled as a modifier because the intent alters when and how the resource is actually applicable.",
"mustSupport": true
},
{
"id": "MedicationRequest.medication[x]",
"path": "MedicationRequest.medication[x]",
"comment": "Usage Note: This is mandatory in FHIR; must contain the same medication code as in the Medication.code field.\r\n\r\nIf 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 or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.",
"type": [
{
"code": "CodeableConcept"
}
],
"mustSupport": true
},
{
"id": "MedicationRequest.medication[x].coding",
"path": "MedicationRequest.medication[x].coding",
"mustSupport": true
},
{
"id": "MedicationRequest.medication[x].coding.system",
"path": "MedicationRequest.medication[x].coding.system",
"mustSupport": true
},
{
"id": "MedicationRequest.medication[x].coding.code",
"path": "MedicationRequest.medication[x].coding.code",
"mustSupport": true
},
{
"id": "MedicationRequest.medication[x].text",
"path": "MedicationRequest.medication[x].text",
"mustSupport": true
},
{
"id": "MedicationRequest.subject",
"path": "MedicationRequest.subject",
"type": [
{
"code": "Reference",
"targetProfile": [
"http://pharmacyeclaims.ca/FHIR/v1.0/R4/StructureDefinition/profile-patient"
],
"aggregation": [
"bundled"
]
}
],
"mustSupport": true
},
{
"id": "MedicationRequest.requester",
"path": "MedicationRequest.requester",
"comment": "Usage Note: The identifier maps to the Prescriber ID and is therefore considered mandatory (though optional in the CPHA3 specification). A reference to the Prescriber resource is optional and may be used if additional details about the prescriber are required by an implementer.\r\n \r\n\r\nReferences 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.",
"type": [
{
"code": "Reference",
"targetProfile": [
"http://hl7.org/fhir/StructureDefinition/Practitioner"
],
"aggregation": [
"bundled"
]
}
],
"mustSupport": true
},
{
"id": "MedicationRequest.requester.reference",
"path": "MedicationRequest.requester.reference",
"comment": "Usage: Future Use. May be required by some impelmenters who wish more details\r\n\r\nUsing absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure \"/[type]/[id]\" then it should be assumed that the reference is to a FHIR RESTful server.",
"mustSupport": true
},
{
"id": "MedicationRequest.requester.identifier",
"path": "MedicationRequest.requester.identifier",
"comment": "CPHA Mapping: D.60.03 Prescriber ID Reference and D.61.03 Prescriber ID\r\n\r\nWhen an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. \n\nWhen both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).",
"mustSupport": true
},
{
"id": "MedicationRequest.requester.identifier.system",
"path": "MedicationRequest.requester.identifier.system",
"comment": "CPHA Mapping: D.60.03 Prescriber ID Reference. Refer to Terminology listing for details\r\n\r\nIdentifier.system is always case sensitive.",
"mustSupport": true
},
{
"id": "MedicationRequest.requester.identifier.value",
"path": "MedicationRequest.requester.identifier.value",
"min": 1,
"mustSupport": true
},
{
"id": "MedicationRequest.dosageInstruction.text",
"path": "MedicationRequest.dosageInstruction.text",
"min": 1,
"mustSupport": true
}
]
}
}