<status value="draft" /> <description value="Claim request specifically for professional services in Canada" /> <purpose value="Claim request specifically for professional services in Canada" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Claim" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Claim" /> <derivation value="constraint" /> <differential> <element id="Claim"> <path value="Claim" /> <comment value="Usage Note: This profile is used for both Pay Provider claims and Pay Subscriber/Cardholder claims, which are differentiated by the payee.type The Claim resource fulfills three information request requirements: Claim - a request for adjudication for reimbursement for products and/or services provided; Preauthorization - a request to authorize the future provision of products and/or services including an anticipated adjudication; and, Predetermination - a request for a non-bind adjudication of possible future products and/or services." /> </element> <element id="Claim.id"> <path value="Claim.id" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.meta"> <path value="Claim.meta" /> <mustSupport value="true" /> </element> <element id="Claim.meta.profile"> <path value="Claim.meta.profile" /> <max value="1" /> <fixedCanonical value="http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-claim-professional" /> <mustSupport value="true" /> </element> <element id="Claim.identifier"> <path value="Claim.identifier" /> <slicing> <discriminator> <type value="value" /> <path value="system" /> </discriminator> <rules value="open" /> </slicing> <comment value="Usage Note: Both the CPHA Trace Number and the Claim Identifier must be present in the message. The CPHA Trace number is present for backward compatibility purposes. It will be phased out as it is limited to 6N" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier.system"> <path value="Claim.identifier.system" /> <mustSupport value="true" /> </element> <element id="Claim.identifier.value"> <path value="Claim.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier:CPHA-Trace-Number"> <path value="Claim.identifier" /> <sliceName value="CPHA-Trace-Number" /> <comment value="Usage Note: This is limited to 6N, as per the CPHA message specification. This is present for backward compatibility. In the future, once all implementations natively support FHIR, this identifier will be deprecated in favour of the Claim-identifier which has no limitations. Usage Note: This will be the trace number from the Claim Request.identifier. The number assigned, by the provider, to the transaction to which this response applies. This is limited to 6N, in order to maintain backward compatibility with CPHA. CPHA Mapping: Trace Number B.23.03" /> <max value="1" /> </element> <element id="Claim.identifier:CPHA-Trace-Number.system"> <path value="Claim.identifier.system" /> <comment value="Set value = http://pharmacyeclaims.ca/FHIR/CPHA-identifier/trace-number Identifier.system is always case sensitive." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier:CPHA-Trace-Number.value"> <path value="Claim.identifier.value" /> <comment value="Usage Note: Unique number produced sequentially by the provider software (or manually in absence of computer) for each transaction transmitted by the provider. CPHA Map: Trace Number E.02.03 6N If 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 value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier:Claim-identifier"> <path value="Claim.identifier" /> <sliceName value="Claim-identifier" /> <comment value="Usage Note: This must be present for all FHIR-based identfiiers. This identifier is not limited as is the Trace-Number CPHA Map: Maps to the D.55.03 Current RX Number and also the D.53.03 Original RX Number and is therefore limited to 9N. In professional services claims, these have the same values. Usage: serves as an invoice number for professional services whereby there is no Prescription number" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier:Claim-identifier.system"> <path value="Claim.identifier.system" /> <comment value="Usage Note: This is assigned by the sending system to uniquely identify the namespace. Identifier.system is always case sensitive. CPHA Mapping: None; this is new" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.identifier:Claim-identifier.value"> <path value="Claim.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.status"> <path value="Claim.status" /> <comment value="This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. CPHA - no mapping" /> <fixedCode value="active" /> <mustSupport value="true" /> </element> <element id="Claim.type"> <path value="Claim.type" /> <comment value="The majority of jurisdictions use: oral, pharmacy, vision, professional and institutional, or variants on those terms, as the general styles of claims. The valueset is extensible to accommodate other jurisdictional requirements. CPHA - no mapping" /> <fixedCodeableConcept> <text value="pharmacy" /> </fixedCodeableConcept> <mustSupport value="true" /> </element> <element id="Claim.type.text"> <path value="Claim.type.text" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.subType"> <path value="Claim.subType" /> <min value="1" /> <fixedCodeableConcept> <text value="ProfessionalServices" /> </fixedCodeableConcept> <mustSupport value="true" /> </element> <element id="Claim.use"> <path value="Claim.use" /> <fixedCode value="claim" /> <mustSupport value="true" /> </element> <element id="Claim.patient"> <path value="Claim.patient" /> <type> <code value="Reference" /> <targetProfile value="http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-patient" /> <aggregation value="bundled" /> </type> <mustSupport value="true" /> </element> <element id="Claim.patient.reference"> <path value="Claim.patient.reference" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.created"> <path value="Claim.created" /> <comment value="Usage note: This may be different from the service date and is mandatory in FHIR This field is independent of the date of creation of the resource as it may reflect the creation date of a source document prior to digitization. Typically for claims all services must be completed as of this date." /> <mustSupport value="true" /> </element> <element id="Claim.enterer"> <path value="Claim.enterer" /> <mustSupport value="true" /> </element> <element id="Claim.provider"> <path value="Claim.provider" /> <type> <code value="Reference" /> <targetProfile value="http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-organization-pharmacy" /> <aggregation value="bundled" /> </type> <mustSupport value="true" /> </element> <element id="Claim.provider.reference"> <path value="Claim.provider.reference" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.priority"> <path value="Claim.priority" /> <mustSupport value="true" /> </element> <element id="Claim.priority.coding"> <path value="Claim.priority.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Claim.priority.coding.system"> <path value="Claim.priority.coding.system" /> <min value="1" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/processpriority" /> <mustSupport value="true" /> </element> <element id="Claim.priority.coding.code"> <path value="Claim.priority.coding.code" /> <min value="1" /> <fixedCode value="stat" /> <mustSupport value="true" /> </element> <element id="Claim.priority.text"> <path value="Claim.priority.text" /> <comment value="CPHA Map: None, this is a new mandatory field Very often the text is the same as a displayName of one of the codings." /> <min value="1" /> <fixedString value="Immediate" /> <mustSupport value="true" /> </element> <element id="Claim.related"> <path value="Claim.related" /> <comment value="Usage Note: This is a reference to a related dispense claim identifier to allow adjudicators to formally relate the professional claim to the claim for the medication dispense. Usage Note: If known to the pharmacy, this link should be provided. CPHA Map: None - this is a new data element For example, for the original treatment and follow-up exams." /> <mustSupport value="true" /> </element> <element id="Claim.related.claim"> <path value="Claim.related.claim" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.related.claim.identifier"> <path value="Claim.related.claim.identifier" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.related.claim.identifier.system"> <path value="Claim.related.claim.identifier.system" /> <mustSupport value="true" /> </element> <element id="Claim.related.claim.identifier.value"> <path value="Claim.related.claim.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.prescription.reference"> <path value="Claim.prescription.reference" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.originalPrescription"> <path value="Claim.originalPrescription" /> <comment value="Usage: Number assigned to a prescription or service record on the original date of prescription or professional service was provided. In a professional sevices claim, this is typically the same identifier as the current prescription number. CPHA Map - D.53.03 Original Prescription Number 9N For example, a physician may prescribe a medication which the pharmacy determines is contraindicated, or for which the patient has an intolerance, and therefore issues a new prescription for an alternate medication which has the same therapeutic intent. The prescription from the pharmacy becomes the 'prescription' and that from the physician becomes the 'original prescription'." /> <mustSupport value="false" /> </element> <element id="Claim.payee"> <path value="Claim.payee" /> <comment value="Usage Note: This field differentiates between the "Pay Provider" and "Pay Cardholder (aka Subscriber) " claims. Usage Note: Set code = "subscriber" or "provider" to indicate the payee type requested. CPHA Map: This was differentiated by transaction type 01 or 04. Often providers agree to receive the benefits payable to reduce the near-term costs to the patient. The insurer may decline to pay the provider and choose to pay the subscriber instead." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.payee.type"> <path value="Claim.payee.type" /> <mustSupport value="true" /> </element> <element id="Claim.payee.type.coding"> <path value="Claim.payee.type.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> <binding> <strength value="extensible" /> <valueSet value="http://hl7.org/fhir/ValueSet/payeetype" /> </binding> </element> <element id="Claim.payee.type.coding.system"> <path value="Claim.payee.type.coding.system" /> <min value="1" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/payeetype" /> <mustSupport value="true" /> </element> <element id="Claim.payee.type.coding.code"> <path value="Claim.payee.type.coding.code" /> <comment value="Usage Note: Set code = "subscriber" or "provider" to indicate the payee type requested. CPHA Map: Transaction Code 01 for Provider claims, code 04 for cardholder claims. Note that FHIR strings SHALL NOT exceed 1MB in size" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam"> <path value="Claim.careTeam" /> <comment value="Usage Note: This is used to specify who delivered the service as well as who was responsible for the service. For example, a nurse may deliver the service but the pharmacist may be responsible for the service. In this case, both providers should be specified. CPHA Map: New data element and is therefore not mandatory; must be populated when known." /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam.sequence"> <path value="Claim.careTeam.sequence" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam.provider"> <path value="Claim.careTeam.provider" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam.provider.identifier"> <path value="Claim.careTeam.provider.identifier" /> <comment value="Usage Note: The identifier of the pharmacist or other clinician When 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. When 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 Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference 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)." /> <min value="1" /> </element> <element id="Claim.careTeam.provider.identifier.system"> <path value="Claim.careTeam.provider.identifier.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam.provider.identifier.value"> <path value="Claim.careTeam.provider.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.careTeam.responsible"> <path value="Claim.careTeam.responsible" /> <comment value="Usage Note: This value is "true" for the pharmacist who is responsible for the claim. This is "false" for a clinician (eg nurse) who is under the supervision of the responsible pharmacist. Responsible might not be required when there is only a single provider listed." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo"> <path value="Claim.supportingInfo" /> <slicing> <discriminator> <type value="value" /> <path value="code.coding.code" /> </discriminator> <rules value="open" /> </slicing> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.sequence"> <path value="Claim.supportingInfo.sequence" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.category"> <path value="Claim.supportingInfo.category" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.category.coding"> <path value="Claim.supportingInfo.category.coding" /> <comment value="Conformance Rule: Set code value = Dispense, and value = reference to the dispense resource. Set code = DaysSupply Set code = Refils Remaining 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." /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.category.coding.code"> <path value="Claim.supportingInfo.category.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.value[x]"> <path value="Claim.supportingInfo.value[x]" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo.reason"> <path value="Claim.supportingInfo.reason" /> <comment value="Usage: for professional services, a reason may be provided. For example: the reason for the additional stay, or why a tooth is missing." /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason"> <path value="Claim.supportingInfo" /> <sliceName value="Reason" /> <comment value="Usage: A reason may be specified for a professional service. Often there are multiple jurisdiction specific valuesets which are required." /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.sequence"> <path value="Claim.supportingInfo.sequence" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.category"> <path value="Claim.supportingInfo.category" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.category.coding"> <path value="Claim.supportingInfo.category.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.category.coding.code"> <path value="Claim.supportingInfo.category.coding.code" /> <min value="1" /> <fixedCode value="Reason" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.value[x]"> <path value="Claim.supportingInfo.value[x]" /> <max value="0" /> </element> <element id="Claim.supportingInfo:Reason.reason"> <path value="Claim.supportingInfo.reason" /> <comment value="Usage: A code must be specified when known; text is also supported for audit purposes only For example: the reason for the additional stay, or why a tooth is missing." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.reason.coding"> <path value="Claim.supportingInfo.reason.coding" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.reason.coding.code"> <path value="Claim.supportingInfo.reason.coding.code" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:Reason.reason.text"> <path value="Claim.supportingInfo.reason.text" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth"> <path value="Claim.supportingInfo" /> <sliceName value="SpecialAuth" /> <comment value="Usage Note: This allows the provider to claim for products and services which require prior authorization, This field enables the provider to claim for a product or service which is not ordinarily covered (e.g. NIHB Non-Formulary Benefits which can be provided by prior authorization). Authorization numbers will be issued by the payor. CPHA Map: Special Authorization Number or Code D.64.03 Often there are multiple jurisdiction specific valuesets which are required." /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth.sequence"> <path value="Claim.supportingInfo.sequence" /> <fixedPositiveInt value="2" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth.category"> <path value="Claim.supportingInfo.category" /> <comment value="Usage: This is a fixed value of "SpecialAuth" This may contain a category for the local bill type codes." /> <fixedCodeableConcept> <coding> <code value="SpecialAuth" /> </coding> </fixedCodeableConcept> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth.category.coding"> <path value="Claim.supportingInfo.category.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth.category.coding.code"> <path value="Claim.supportingInfo.category.coding.code" /> <min value="1" /> <fixedCode value="SpecialAuth" /> <mustSupport value="true" /> </element> <element id="Claim.supportingInfo:SpecialAuth.code.coding"> <path value="Claim.supportingInfo.code.coding" /> <mustSupport value="false" /> </element> <element id="Claim.supportingInfo:SpecialAuth.code.coding.system"> <path value="Claim.supportingInfo.code.coding.system" /> <mustSupport value="false" /> </element> <element id="Claim.supportingInfo:SpecialAuth.code.coding.code"> <path value="Claim.supportingInfo.code.coding.code" /> <mustSupport value="false" /> </element> <element id="Claim.supportingInfo:SpecialAuth.value[x]"> <path value="Claim.supportingInfo.value[x]" /> <comment value="Usage Note: This allows the provider to claim for products and services which require prior authorization, This field enables the provider to claim for a product or service which is not ordinarily covered (e.g. NIHB Non-Formulary Benefits which can be provided by prior authorization). Authorization numbers will be issued by the payor. CPHA Map: Special Authorization Number or Code D.64.03 Could be used to provide references to other resources, document. For example could contain a PDF in an Attachment of the Police Report for an Accident." /> <min value="1" /> <type> <code value="string" /> </type> <mustSupport value="true" /> </element> <element id="Claim.diagnosis"> <path value="Claim.diagnosis" /> <comment value="Usage Note: Indicates prescriber's designation of the medical condition for which the patient is being treated if required by plan. Conformance Rule: Current support for: ICD-9 or ICD-10CA, ODB reason for use codes, DND Eligible Medical Conditions. If one or more are known, they must be included. Adjudicators may also include implementation specific rules, eg SNOMED and this may also be included if known or agreed to by implementers. CPHA Map: Medical Condition/ Reason for Use D.51.03 A/N6 and Medical Reason/Reference D.50.03 Limited to one code" /> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.sequence"> <path value="Claim.diagnosis.sequence" /> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.diagnosis[x]"> <path value="Claim.diagnosis.diagnosis[x]" /> <type> <code value="CodeableConcept" /> </type> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.diagnosis[x].coding"> <path value="Claim.diagnosis.diagnosis[x].coding" /> <comment value="Usage Note: Allows multiple codes to be specified where translation has occurred. Vendors should send all possible codings as this may vary amongst adjudicators. Alignment: PrescribeIT supports SNOMED 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." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.diagnosis[x].coding.system"> <path value="Claim.diagnosis.diagnosis[x].coding.system" /> <comment value="Usage: Provides for the Identification of reference codes that are used by the prescriber to designate the medical condition or reason for use. Conformance Rule: System values are: CPHA Map: Medical Reason Reference D.50.03 A1 ICD-9 (http://hl7.org/fhir/sid/icd-9-cm) ODB reason for use (system =http://pharmacyeclaims.ca/FHIR/CPHA-diagnosis-ODB-reason-code| ICD-10 (http://hl7.org/fhir/sid/icd-10) DND Eligible Medical Conditions (system = http://pharmacyeclaims.ca/FHIR/CPHA-diagnosis-DND-eligible-medical-conditions|Claim.diagnosis.code) 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." /> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.diagnosis[x].coding.code"> <path value="Claim.diagnosis.diagnosis[x].coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.diagnosis.diagnosis[x].text"> <path value="Claim.diagnosis.diagnosis[x].text" /> <comment value="Usage Note: May be included where code system mapping has occurred Very often the text is the same as a displayName of one of the codings." /> <mustSupport value="true" /> </element> <element id="Claim.insurance"> <path value="Claim.insurance" /> <comment value="Usage Note: This is currently restricted to 5 instances of insurance. All known instances should be included with the sequence number reflecting the COB Order. Only one instance can be the focal=true. The first/primary claim submission will not include any prior ClaimResponses. All insurance coverages for the patient which may be applicable for reimbursement, of the products and services listed in the claim, are typically provided in the claim to allow insurers to confirm the ordering of the insurance coverages relative to local 'coordination of benefit' rules. One coverage (and only one) with 'focal=true' is to be used in the adjudication of this claim. Coverages appearing before the focal Coverage in the list, and where 'Coverage.subrogation=false', should provide a reference to the ClaimResponse containing the adjudication results of the prior claim." /> <mustSupport value="true" /> </element> <element id="Claim.insurance.sequence"> <path value="Claim.insurance.sequence" /> <comment value="Usage Note: This reflects the order for COB purposes. By example, if a secondary claim is being submitted, the sequence = 2 and focal = true and the claimResponse from the primary adjudicator will be present. If a primary claim is being submitted, multiple coverages can be included. Sequence 1 and focal=true. Usage Note: Where available, the claimResponse frrom prior claims must be included. CPHA Map: N/A - new 32 bit number; for values larger than this, use decimal" /> <mustSupport value="true" /> </element> <element id="Claim.insurance.focal"> <path value="Claim.insurance.focal" /> <mustSupport value="true" /> </element> <element id="Claim.insurance.coverage"> <path value="Claim.insurance.coverage" /> <type> <code value="Reference" /> <targetProfile value="http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-coverage" /> <aggregation value="bundled" /> </type> <mustSupport value="true" /> </element> <element id="Claim.insurance.coverage.reference"> <path value="Claim.insurance.coverage.reference" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.insurance.claimResponse"> <path value="Claim.insurance.claimResponse" /> <comment value="Usage Note: Includes the claim response from prior adjudicators, for secondary, tertiary claims. CPHA Map: N/A - new Must not be specified when 'focal=true' for this insurance." /> <mustSupport value="true" /> </element> <element id="Claim.item"> <path value="Claim.item" /> <comment value="Usage Note: Only a single item may be submitted per claim" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.sequence"> <path value="Claim.item.sequence" /> <comment value="Usage Note: This is expected to be a value of "1" 32 bit number; for values larger than this, use decimal" /> <mustSupport value="true" /> </element> <element id="Claim.item.productOrService"> <path value="Claim.item.productOrService" /> <comment value="Usage Note: This is the service code that is being charge. Adjudicator-specific Psuedo DINs - Adjudicator specific. Each adjudicator will provide the "Code system" associated with their set of codes that are expected for Professional services. Once established this specificaiton can be updated to include CPHA Map: DIN/GP#/PIN/UNLISTED COMPOUND If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'." /> <mustSupport value="true" /> </element> <element id="Claim.item.productOrService.coding"> <path value="Claim.item.productOrService.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.productOrService.coding.system"> <path value="Claim.item.productOrService.coding.system" /> <comment value="Usage Note: Differentiates between code systems CPHA Map; N/A - New 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." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.productOrService.coding.code"> <path value="Claim.item.productOrService.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.productOrService.text"> <path value="Claim.item.productOrService.text" /> <comment value="Usage Note: May be used to convey the description of the compound (eg Magic Mouthwash) Very often the text is the same as a displayName of one of the codings." /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier"> <path value="Claim.item.modifier" /> <comment value="Usage Note: Provides codes which detail intervention procedures taken or identify that special coverage and payment rules are being claimed. Conformance Rule: This supports up to 10 intervention codes CPHA Map: INTERVENTION CODES D.65.03. Limt of two for CPHA; limit of 10 or FHIR. As FHIR allows more, only two intervention codes should be sent if the claim is going to an adjudicator who supports CPHA. Note: As a general rule, the vendor submitting the claim will submit it in the format supported by the adjudication system. For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or outside of office hours." /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding"> <path value="Claim.item.modifier.coding" /> <slicing> <discriminator> <type value="value" /> <path value="system" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding.system"> <path value="Claim.item.modifier.coding.system" /> <min value="1" /> <fixedUri value="http://pharmacyeclaims.ca/FHIR/CodeSystem/intervention-codes" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding.code"> <path value="Claim.item.modifier.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding:SpecialServiceCode"> <path value="Claim.item.modifier.coding" /> <sliceName value="SpecialServiceCode" /> <comment value="Usage: This is present for backward compatibility and should be replaced by a Professional Services claim. This is infrequently used. Note: This is not in the dispense message CPHA Mapping: SSC D.57.03 Limited to 3 Usage Note: This has increased to allow for 10 codes in the future. This may be configurable and may vary by adjudicator 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." /> <max value="10" /> </element> <element id="Claim.item.modifier.coding:SpecialServiceCode.system"> <path value="Claim.item.modifier.coding.system" /> <min value="1" /> <fixedUri value="http://pharmacyeclaims.ca/FHIR/CodeSystem/special-service-codes" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding:SpecialServiceCode.code"> <path value="Claim.item.modifier.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding:InterventionCode"> <path value="Claim.item.modifier.coding" /> <sliceName value="InterventionCode" /> <comment value="CPHA Mapping: Intervention and Exception CodesD.65.03 This field provides codes which detail DUR intervention procedures taken or identify that special coverage and payment rules are being claimed 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." /> <max value="10" /> </element> <element id="Claim.item.modifier.coding:InterventionCode.system"> <path value="Claim.item.modifier.coding.system" /> <min value="1" /> <fixedUri value="http://pharmacyeclaims.ca/FHIR/CodeSystem/intervention-codes" /> <mustSupport value="true" /> </element> <element id="Claim.item.modifier.coding:InterventionCode.code"> <path value="Claim.item.modifier.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.serviced[x]"> <path value="Claim.item.serviced[x]" /> <comment value="Usage note: Date on which prescription and/or professional service is provided. Established by the provider in accordance with the official time in the zone where the provider is located CPHA Map: B.22.03 - Provider Transaction Date" /> <min value="1" /> <type> <code value="date" /> </type> <mustSupport value="true" /> </element> <element id="Claim.item.detail"> <path value="Claim.item.detail" /> <slicing> <discriminator> <type value="value" /> <path value="productOrService.coding.code" /> </discriminator> <rules value="open" /> </slicing> <comment value="Usage Note: Details are used to specify each component pertaining to the item being claimed For each, a sequence number, code and net amount will be specified." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail.sequence"> <path value="Claim.item.detail.sequence" /> <comment value="Usage Note: This is a sequential number assigned for each detail 32 bit number; for values larger than this, use decimal" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail.productOrService"> <path value="Claim.item.detail.productOrService" /> <comment value="Usage: This will identify the professional service being provided. If this is an actual service or product line, i.e. not a Group, then use code to indicate the Professional Service or Product supplied (e.g. CTP, HCPCS, USCLS, ICD10, NCPDP, DIN, RxNorm, ACHI, CCI). If a grouping item then use a group code to indicate the type of thing being grouped e.g. 'glasses' or 'compound'." /> <mustSupport value="true" /> <binding> <strength value="extensible" /> <valueSet value="http://pharmacyeclaims.ca/FHIR/ValueSet/pharma-service" /> </binding> </element> <element id="Claim.item.detail.productOrService.coding"> <path value="Claim.item.detail.productOrService.coding" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail.productOrService.coding.system"> <path value="Claim.item.detail.productOrService.coding.system" /> <min value="1" /> <fixedUri value="http://pharmacyeclaims.ca/FHIR/CodeSystem/pharma-service" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail.productOrService.coding.code"> <path value="Claim.item.detail.productOrService.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail.net"> <path value="Claim.item.detail.net" /> <comment value="Conformance Rule: The amount being charged for the service. For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied." /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee"> <path value="Claim.item.detail" /> <sliceName value="ProfessionalFee" /> <comment value="Usage Note: Pharmacist's fee for professional and technical activities associated with providing the prescribed medication and service. This is a fee to compensate the pharacist for professional services associated with the dispensing of a prescription. Unless a plan, or agreement between a provider and a payor, contains provisions for including compensation for compounding or special services in the professional fee, compensation for these services will be claimed separately as a "Compounding Charge" ( D.70.03) and a "Special Services Fee" (D.72.03). CPHA Mapping: D.66.03 Drug Cost" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee.sequence"> <path value="Claim.item.detail.sequence" /> <comment value="Usage Note: When item is specified, the next availabe sequence number will be assigned. eg 1,2,3 32 bit number; for values larger than this, use decimal" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee.productOrService"> <path value="Claim.item.detail.productOrService" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee.productOrService.coding"> <path value="Claim.item.detail.productOrService.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee.productOrService.coding.code"> <path value="Claim.item.detail.productOrService.coding.code" /> <min value="1" /> <fixedCode value="D.68.03" /> <mustSupport value="true" /> </element> <element id="Claim.item.detail:ProfessionalFee.net"> <path value="Claim.item.detail.net" /> <min value="1" /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>