This page is part of the Da Vinci Prior Authorization Support (PAS) FHIR IG (v0.1.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions
Definitions for the profile-claim Profile.
1. Claim | |
Definition | A provider issued list of professional services and products which have been provided, or are to be provided, to a patient which is sent to an insurer for reimbursement. |
Control | 0..* |
Alternate Names | Adjudication Request, Preauthorization Request, Predetermination Request |
Comments | 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. |
Invariants | Defined on this element dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource (: 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()) dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated (: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) dom-5: If a resource is contained in another resource, it SHALL NOT have a security label (: contained.meta.security.empty()) dom-6: A resource should have narrative for robust management (: text.div.exists()) |
2. Claim.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Control | 0..1 |
Type | id |
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. |
3. Claim.meta | |
Definition | 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. |
Control | 0..1 |
Type | Meta |
4. Claim.implicitRules | |
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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
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. 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. |
5. Claim.language | |
Definition | The base language in which the resource is written. |
Control | 0..1 |
Binding | A human language. The codes SHOULD be taken from CommonLanguages Max Binding: AllLanguages |
Type | code |
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). |
6. Claim.text | |
Definition | 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. |
Control | 0..1 |
Type | Narrative |
Alternate Names | narrative, html, xhtml, display |
Comments | 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. |
7. Claim.contained | |
Definition | 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. |
Control | 0..* |
Type | Resource |
Alternate Names | inline resources, anonymous resources, contained resources |
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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
8. Claim.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices on Claim.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
9. Claim.extension:InstitutionalEncounter | |
SliceName | InstitutionalEncounter |
Definition | Used to provide information about admission to a facility. |
Control | 0..1 This element is affected by the following invariants: ele-1 |
Type | Extension(InstitutionalEncounter) (Extension Type: Reference) |
Must Support | true |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
10. Claim.modifierExtension | |
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 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
11. Claim.identifier | |
Definition | A unique identifier assigned to this claim. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Must Support | true |
Requirements | Allows claims to be distinguished and referenced. |
Alternate Names | Claim Number |
12. Claim.status | |
Definition | The status of the resource instance. |
Control | 1..1 |
Binding | A code specifying the state of the resource instance. The codes SHALL be taken from FinancialResourceStatusCodes |
Type | code |
Is Modifier | true |
Must Support | true |
Requirements | Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'. |
Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
13. Claim.type | |
Definition | The category of claim, e.g. oral, pharmacy, vision, institutional, professional. |
Control | 1..1 |
Binding | The type or discipline-style of the claim. The codes SHALL be taken from ClaimTypeCodes; other codes may be used where these codes are not suitable |
Type | CodeableConcept |
Must Support | true |
Requirements | Claim type determine the general sets of business rules applied for information requirements and adjudication. |
Comments | 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. |
14. Claim.subType | |
Definition | A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service. |
Control | 0..1 |
Binding | A more granular claim typecode. For example codes, see ExampleClaimSubTypeCodes |
Type | CodeableConcept |
Requirements | Some jurisdictions need a finer grained claim type for routing and adjudication. |
Comments | This may contain the local bill type codes, for example the US UB-04 bill type code or the CMS bill type. |
15. Claim.use | |
Definition | A code to indicate whether the nature of the request is: to request adjudication of products and services previously rendered; or requesting authorization and adjudication for provision in the future; or requesting the non-binding adjudication of the listed products and services which could be provided in the future. |
Control | 1..1 |
Binding | The purpose of the Claim: predetermination, preauthorization, claim. The codes SHALL be taken from Use |
Type | code |
Must Support | true |
Requirements | This element is required to understand the nature of the request for adjudication. |
Fixed Value | preauthorization |
16. Claim.use.id | |
Definition | unique id for the element within a resource (for internal references) |
Control | 0..1 |
Type | string |
17. Claim.use.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices on Claim.use.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
18. Claim.use.extension:CertificationType | |
SliceName | CertificationType |
Definition | The type of the pre-authorization that is being requested. |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(CertificationType) (Extension Type: code) |
Must Support | true |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
19. Claim.use.value | |
Definition | Primitive value for code |
Control | 0..1 |
20. Claim.patient | |
Definition | The party to whom the professional services and/or products have been supplied or are being considered and for whom actual or forecast reimbursement is sought. |
Control | 1..1 |
Type | Reference(Patient) |
Must Support | true |
Requirements | The patient must be supplied to the insurer so that confirmation of coverage and service history may be considered as part of the authorization and/or adjudiction. |
21. Claim.billablePeriod | |
Definition | The period for which charges are being submitted. |
Control | 0..1 |
Type | Period |
Requirements | A number jurisdictions required the submission of the billing period when submitting claims for example for hospital stays or long-term care. |
Comments | Typically this would be today or in the past for a claim, and today or in the future for preauthorizations and predeterminations. Typically line item dates of service should fall within the billing period if one is specified. |
22. Claim.created | |
Definition | The date this resource was created. |
Control | 1..1 |
Type | dateTime |
Must Support | true |
Requirements | Need to record a timestamp for use by both the recipient and the issuer. |
Comments | 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. |
23. Claim.enterer | |
Definition | Individual who created the claim, predetermination or preauthorization. |
Control | 0..1 |
Type | Reference(Practitioner | PractitionerRole) |
Requirements | Some jurisdictions require the contact information for personnel completing claims. |
24. Claim.insurer | |
Definition | The Insurer who is target of the request. |
Control | 0..1 |
Type | Reference(UMOOrganization) |
Must Support | true |
25. Claim.provider | |
Definition | The provider which is responsible for the claim, predetermination or preauthorization. |
Control | 1..1 |
Type | Reference(RequestorPractitionerRole | RequestorOrganization) |
Must Support | true |
Comments | Typically this field would be 1..1 where this party is responsible for the claim but not necessarily professionally responsible for the provision of the individual products and services listed below. |
26. Claim.priority | |
Definition | The provider-required urgency of processing the request. Typical values include: stat, routine deferred. |
Control | 1..1 |
Binding | The timeliness with which processing is required: stat, normal, deferred. For example codes, see ProcessPriorityCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | The provider may need to indicate their processing requirements so that the processor can indicate if they are unable to comply. |
Comments | If a claim processor is unable to complete the processing as per the priority then they should generate and error and not process the request. |
27. Claim.fundsReserve | |
Definition | A code to indicate whether and for whom funds are to be reserved for future claims. |
Control | 0..1 |
Binding | For whom funds are to be reserved: (Patient, Provider, None). For example codes, see Funds Reservation Codes |
Type | CodeableConcept |
Requirements | In the case of a Pre-Determination/Pre-Authorization the provider may request that funds in the amount of the expected Benefit be reserved ('Patient' or 'Provider') to pay for the Benefits determined on the subsequent claim(s). 'None' explicitly indicates no funds reserving is requested. |
Alternate Names | Fund pre-allocation |
Comments | This field is only used for preauthorizations. |
28. Claim.related | |
Definition | Other claims which are related to this claim such as prior submissions or claims for related services or for the same event. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | For workplace or other accidents it is common to relate separate claims arising from the same event. |
Comments | For example, for the original treatment and follow-up exams. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
29. Claim.related.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
30. Claim.related.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
31. Claim.related.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
32. Claim.related.claim | |
Definition | Reference to a related claim. |
Control | 0..1 |
Type | Reference(Claim) |
Requirements | For workplace or other accidents it is common to relate separate claims arising from the same event. |
33. Claim.related.relationship | |
Definition | A code to convey how the claims are related. |
Control | 0..1 |
Binding | Relationship of this claim to a related Claim. For example codes, see ExampleRelatedClaimRelationshipCodes |
Type | CodeableConcept |
Requirements | Some insurers need a declaration of the type of relationship. |
Comments | For example, prior claim or umbrella. |
34. Claim.related.reference | |
Definition | An alternate organizational reference to the case or file to which this particular claim pertains. |
Control | 0..1 |
Type | Identifier |
Must Support | true |
Requirements | In cases where an event-triggered claim is being submitted to an insurer which requires a reference number to be specified on all exchanges. |
Comments | For example, Property/Casualty insurer claim # or Workers Compensation case # . |
35. Claim.prescription | |
Definition | Prescription to support the dispensing of pharmacy, device or vision products. |
Control | 0..1 |
Type | Reference(DeviceRequest | MedicationRequest | VisionPrescription) |
Must Support | true |
Requirements | Required to authorize the dispensing of controlled substances and devices. |
36. Claim.prescription.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
37. Claim.prescription.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | This element introduces a set of slices on Claim.prescription.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
38. Claim.prescription.extension:RequestedService | |
SliceName | RequestedService |
Definition | Provides specific information about a service being requested. |
Control | 0..* |
Type | Extension(RequestedService) (Extension Type: Reference) |
Must Support | true |
39. Claim.prescription.extension:RequestedService.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
40. Claim.prescription.extension:RequestedService.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Slicing | This element introduces a set of slices on Claim.prescription.extension.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
41. Claim.prescription.extension:RequestedService.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Control | 1..1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-requestedService |
42. Claim.prescription.extension:RequestedService.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). |
Control | 0..1 |
Type | Reference |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Slicing | This element introduces a set of slices on Claim.prescription.extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
43. Claim.prescription.extension:RequestedService.value[x]:valueReference | |
SliceName | valueReference |
Definition | Value of extension - must be one of a constrained set of the data types (see Extensibility for a list). |
Control | 0..1 |
Type | Reference(ServiceRequest) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
44. Claim.prescription.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Control | 0..1 This element is affected by the following invariants: ref-1 |
Type | string |
Comments | Using 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. |
45. Claim.prescription.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Control | 0..1 |
Binding | Aa resource (or, for logical models, the URI of the logical model). The codes SHALL be taken from ResourceType; other codes may be used where these codes are not suitable |
Type | uri |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
46. Claim.prescription.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..1 |
Type | Identifier |
Comments | 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). |
47. Claim.prescription.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 |
Type | string |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
48. Claim.originalPrescription | |
Definition | Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products. |
Control | 0..1 |
Type | Reference(DeviceRequest | MedicationRequest | VisionPrescription) |
Requirements | Often required when a fulfiller varies what is fulfilled from that authorized on the original prescription. |
Comments | 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'. |
49. Claim.payee | |
Definition | The party to be reimbursed for cost of the products and services according to the terms of the policy. |
Control | 0..1 |
Type | BackboneElement |
Requirements | The provider needs to specify who they wish to be reimbursed and the claims processor needs express who they will reimburse. |
Comments | 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. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
50. Claim.payee.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
51. Claim.payee.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
52. Claim.payee.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
53. Claim.payee.type | |
Definition | Type of Party to be reimbursed: subscriber, provider, other. |
Control | 1..1 |
Binding | A code for the party to be reimbursed. For example codes, see Claim Payee Type Codes |
Type | CodeableConcept |
Requirements | Need to know who should receive payment with the most common situations being the Provider (assignment of benefits) or the Subscriber. |
54. Claim.payee.party | |
Definition | Reference to the individual or organization to whom any payment will be made. |
Control | 0..1 |
Type | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson) |
Requirements | Need to provide demographics if the payee is not 'subscriber' nor 'provider'. |
Comments | Not required if the payee is 'subscriber' or 'provider'. |
55. Claim.referral | |
Definition | A reference to a referral resource. |
Control | 0..1 |
Type | Reference(ServiceRequest) |
Requirements | Some insurers require proof of referral to pay for services or to pay specialist rates for services. |
Comments | The referral resource which lists the date, practitioner, reason and other supporting information. |
56. Claim.facility | |
Definition | Facility where the services were provided. |
Control | 0..1 |
Type | Reference(Location) |
Must Support | true |
Requirements | Insurance adjudication can be dependant on where services were delivered. |
57. Claim.careTeam | |
Definition | The members of the team who provided the products and services. |
Control | 0..* |
Type | BackboneElement |
Requirements | Common to identify the responsible and supporting practitioners. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
58. Claim.careTeam.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
59. Claim.careTeam.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
60. Claim.careTeam.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
61. Claim.careTeam.sequence | |
Definition | A number to uniquely identify care team entries. |
Control | 1..1 |
Type | positiveInt |
Requirements | Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details. |
62. Claim.careTeam.provider | |
Definition | Member of the team who provided the product or service. |
Control | 1..1 |
Type | Reference(Practitioner | PractitionerRole | Organization) |
Requirements | Often a regulatory requirement to specify the responsible provider. |
63. Claim.careTeam.responsible | |
Definition | The party who is billing and/or responsible for the claimed products or services. |
Control | 0..1 |
Type | boolean |
Requirements | When multiple parties are present it is required to distinguish the lead or responsible individual. |
Comments | Responsible might not be required when there is only a single provider listed. |
64. Claim.careTeam.role | |
Definition | The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team. |
Control | 0..1 |
Binding | The role codes for the care team members. For example codes, see ClaimCareTeamRoleCodes |
Type | CodeableConcept |
Requirements | When multiple parties are present it is required to distinguish the roles performed by each member. |
Comments | Role might not be required when there is only a single provider listed. |
65. Claim.careTeam.qualification | |
Definition | The qualification of the practitioner which is applicable for this service. |
Control | 0..1 |
Binding | Provider professional qualifications. For example codes, see ExampleProviderQualificationCodes |
Type | CodeableConcept |
Requirements | Need to specify which qualification a provider is delivering the product or service under. |
66. Claim.supportingInfo | |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
Slicing | This element introduces a set of slices on Claim.supportingInfo. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
67. Claim.supportingInfo.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
68. Claim.supportingInfo.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
69. Claim.supportingInfo.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
70. Claim.supportingInfo.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
71. Claim.supportingInfo.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The type of supporting information that is being sent The codes SHALL be taken from PASSupportingInfoType |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
72. Claim.supportingInfo.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
73. Claim.supportingInfo.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
74. Claim.supportingInfo.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
75. Claim.supportingInfo.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
76. Claim.supportingInfo:RelatedCauses | |
SliceName | RelatedCauses |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
77. Claim.supportingInfo:RelatedCauses.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
78. Claim.supportingInfo:RelatedCauses.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
79. Claim.supportingInfo:RelatedCauses.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
80. Claim.supportingInfo:RelatedCauses.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
81. Claim.supportingInfo:RelatedCauses.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="relatedCauses"/> </coding> </valueCodeableConcept> |
82. Claim.supportingInfo:RelatedCauses.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to identify the kind of additional information. |
83. Claim.supportingInfo:RelatedCauses.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
84. Claim.supportingInfo:RelatedCauses.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
85. Claim.supportingInfo:RelatedCauses.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
86. Claim.supportingInfo:CurrentHealthCondition | |
SliceName | CurrentHealthCondition |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
87. Claim.supportingInfo:CurrentHealthCondition.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
88. Claim.supportingInfo:CurrentHealthCondition.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
89. Claim.supportingInfo:CurrentHealthCondition.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
90. Claim.supportingInfo:CurrentHealthCondition.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
91. Claim.supportingInfo:CurrentHealthCondition.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="currentHealthCondition"/> </coding> </valueCodeableConcept> |
92. Claim.supportingInfo:CurrentHealthCondition.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
93. Claim.supportingInfo:CurrentHealthCondition.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
94. Claim.supportingInfo:CurrentHealthCondition.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
95. Claim.supportingInfo:CurrentHealthCondition.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
96. Claim.supportingInfo:PatientPrognosis | |
SliceName | PatientPrognosis |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
97. Claim.supportingInfo:PatientPrognosis.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
98. Claim.supportingInfo:PatientPrognosis.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
99. Claim.supportingInfo:PatientPrognosis.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
100. Claim.supportingInfo:PatientPrognosis.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
101. Claim.supportingInfo:PatientPrognosis.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="patientPrognosis"/> </coding> </valueCodeableConcept> |
102. Claim.supportingInfo:PatientPrognosis.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
103. Claim.supportingInfo:PatientPrognosis.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
104. Claim.supportingInfo:PatientPrognosis.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
105. Claim.supportingInfo:PatientPrognosis.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
106. Claim.supportingInfo:ReleaseOfInformation | |
SliceName | ReleaseOfInformation |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
107. Claim.supportingInfo:ReleaseOfInformation.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
108. Claim.supportingInfo:ReleaseOfInformation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
109. Claim.supportingInfo:ReleaseOfInformation.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
110. Claim.supportingInfo:ReleaseOfInformation.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
111. Claim.supportingInfo:ReleaseOfInformation.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="releaseOfInformation"/> </coding> </valueCodeableConcept> |
112. Claim.supportingInfo:ReleaseOfInformation.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
113. Claim.supportingInfo:ReleaseOfInformation.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
114. Claim.supportingInfo:ReleaseOfInformation.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
115. Claim.supportingInfo:ReleaseOfInformation.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
116. Claim.supportingInfo:DelayReason | |
SliceName | DelayReason |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
117. Claim.supportingInfo:DelayReason.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
118. Claim.supportingInfo:DelayReason.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
119. Claim.supportingInfo:DelayReason.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
120. Claim.supportingInfo:DelayReason.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
121. Claim.supportingInfo:DelayReason.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="delayReason"/> </coding> </valueCodeableConcept> |
122. Claim.supportingInfo:DelayReason.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
123. Claim.supportingInfo:DelayReason.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
124. Claim.supportingInfo:DelayReason.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
125. Claim.supportingInfo:DelayReason.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
126. Claim.supportingInfo:LastMenstrualPeriod | |
SliceName | LastMenstrualPeriod |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
127. Claim.supportingInfo:LastMenstrualPeriod.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
128. Claim.supportingInfo:LastMenstrualPeriod.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
129. Claim.supportingInfo:LastMenstrualPeriod.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
130. Claim.supportingInfo:LastMenstrualPeriod.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
131. Claim.supportingInfo:LastMenstrualPeriod.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="lastMenstrualPeriod"/> </coding> </valueCodeableConcept> |
132. Claim.supportingInfo:LastMenstrualPeriod.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
133. Claim.supportingInfo:LastMenstrualPeriod.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | date |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
134. Claim.supportingInfo:LastMenstrualPeriod.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
135. Claim.supportingInfo:LastMenstrualPeriod.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
136. Claim.supportingInfo:EstimatedBirthDate | |
SliceName | EstimatedBirthDate |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
137. Claim.supportingInfo:EstimatedBirthDate.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
138. Claim.supportingInfo:EstimatedBirthDate.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
139. Claim.supportingInfo:EstimatedBirthDate.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
140. Claim.supportingInfo:EstimatedBirthDate.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
141. Claim.supportingInfo:EstimatedBirthDate.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="estimatedBirthDate"/> </coding> </valueCodeableConcept> |
142. Claim.supportingInfo:EstimatedBirthDate.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
143. Claim.supportingInfo:EstimatedBirthDate.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | date |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
144. Claim.supportingInfo:EstimatedBirthDate.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
145. Claim.supportingInfo:EstimatedBirthDate.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
146. Claim.supportingInfo:OnsetOfSymptoms | |
SliceName | OnsetOfSymptoms |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
147. Claim.supportingInfo:OnsetOfSymptoms.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
148. Claim.supportingInfo:OnsetOfSymptoms.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
149. Claim.supportingInfo:OnsetOfSymptoms.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
150. Claim.supportingInfo:OnsetOfSymptoms.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
151. Claim.supportingInfo:OnsetOfSymptoms.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="onsetOfSymptoms"/> </coding> </valueCodeableConcept> |
152. Claim.supportingInfo:OnsetOfSymptoms.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
153. Claim.supportingInfo:OnsetOfSymptoms.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
154. Claim.supportingInfo:OnsetOfSymptoms.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
155. Claim.supportingInfo:OnsetOfSymptoms.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
156. Claim.supportingInfo:PatientEvent | |
SliceName | PatientEvent |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
157. Claim.supportingInfo:PatientEvent.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
158. Claim.supportingInfo:PatientEvent.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
159. Claim.supportingInfo:PatientEvent.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
160. Claim.supportingInfo:PatientEvent.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
161. Claim.supportingInfo:PatientEvent.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="patientEvent"/> </coding> </valueCodeableConcept> |
162. Claim.supportingInfo:PatientEvent.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
163. Claim.supportingInfo:PatientEvent.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
164. Claim.supportingInfo:PatientEvent.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
165. Claim.supportingInfo:PatientEvent.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
166. Claim.supportingInfo:AdmissionReview | |
SliceName | AdmissionReview |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
167. Claim.supportingInfo:AdmissionReview.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
168. Claim.supportingInfo:AdmissionReview.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
169. Claim.supportingInfo:AdmissionReview.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
170. Claim.supportingInfo:AdmissionReview.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
171. Claim.supportingInfo:AdmissionReview.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="admissionReview"/> </coding> </valueCodeableConcept> |
172. Claim.supportingInfo:AdmissionReview.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
173. Claim.supportingInfo:AdmissionReview.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
174. Claim.supportingInfo:AdmissionReview.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Choice of: boolean, string, Quantity, Attachment, Reference(Resource) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
175. Claim.supportingInfo:AdmissionReview.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
176. Claim.supportingInfo:AdditionalInformation | |
SliceName | AdditionalInformation |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
177. Claim.supportingInfo:AdditionalInformation.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
178. Claim.supportingInfo:AdditionalInformation.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
179. Claim.supportingInfo:AdditionalInformation.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
180. Claim.supportingInfo:AdditionalInformation.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
181. Claim.supportingInfo:AdditionalInformation.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="additionalInformation"/> </coding> </valueCodeableConcept> |
182. Claim.supportingInfo:AdditionalInformation.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to identify the kind of additional information. |
183. Claim.supportingInfo:AdditionalInformation.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
184. Claim.supportingInfo:AdditionalInformation.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | Reference(DocumentReference) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
185. Claim.supportingInfo:AdditionalInformation.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
186. Claim.supportingInfo:FreeFormMessage | |
SliceName | FreeFormMessage |
Definition | Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Typically these information codes are required to support the services rendered or the adjudication of the services rendered. |
Alternate Names | Attachments Exception Codes Occurrence Codes Value codes |
Comments | Often there are multiple jurisdiction specific valuesets which are required. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
187. Claim.supportingInfo:FreeFormMessage.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
188. Claim.supportingInfo:FreeFormMessage.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
189. Claim.supportingInfo:FreeFormMessage.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
190. Claim.supportingInfo:FreeFormMessage.sequence | |
Definition | A number to uniquely identify supporting information entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details. |
191. Claim.supportingInfo:FreeFormMessage.category | |
Definition | The general class of the information supplied: information; exception; accident, employment; onset, etc. |
Control | 1..1 |
Binding | The valuset used for additional information category codes. For example codes, see ClaimInformationCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Required to group or associate information items with common characteristics. For example: admission information or prior treatments. |
Comments | This may contain a category for the local bill type codes. |
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://hl7.org/us/davinci-pas/CodeSystem/PASSupportingInfoType"/> <code value="freeFormMessage"/> </coding> </valueCodeableConcept> |
192. Claim.supportingInfo:FreeFormMessage.code | |
Definition | System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought. |
Control | 0..1 |
Binding | The valuset used for additional information codes. For example codes, see ExceptionCodes |
Type | CodeableConcept |
Requirements | Required to identify the kind of additional information. |
193. Claim.supportingInfo:FreeFormMessage.timing[x] | |
Definition | The date when or period to which this information refers. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
194. Claim.supportingInfo:FreeFormMessage.value[x] | |
Definition | Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data. |
Control | 0..1 |
Type | string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | To convey the data content to be provided when the information is more than a simple code or period. |
Comments | 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. |
195. Claim.supportingInfo:FreeFormMessage.reason | |
Definition | Provides the reason in the situation where a reason code is required in addition to the content. |
Control | 0..1 |
Binding | Reason codes for the missing teeth. For example codes, see MissingToothReasonCodes |
Type | CodeableConcept |
Requirements | Needed when the supporting information has both a date and amount/value and requires explanation. |
Comments | For example: the reason for the additional stay, or why a tooth is missing. |
196. Claim.diagnosis | |
Definition | Information about diagnoses relevant to the claim items. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | Required for the adjudication by provided context for the services and product listed. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
197. Claim.diagnosis.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
198. Claim.diagnosis.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
199. Claim.diagnosis.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
200. Claim.diagnosis.sequence | |
Definition | A number to uniquely identify diagnosis entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details. |
Comments | Diagnosis are presented in list order to their expected importance: primary, secondary, etc. |
201. Claim.diagnosis.diagnosis[x] | |
Definition | The nature of illness or problem in a coded form or as a reference to an external defined Condition. |
Control | 1..1 |
Type | Reference |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Provides health context for the evaluation of the products and/or services. |
Slicing | This element introduces a set of slices on Claim.diagnosis.diagnosis[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
202. Claim.diagnosis.diagnosis[x]:diagnosisReference | |
SliceName | diagnosisReference |
Definition | The nature of illness or problem in a coded form or as a reference to an external defined Condition. |
Control | 1..1 |
Type | Reference(Condition) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | Provides health context for the evaluation of the products and/or services. |
203. Claim.diagnosis.type | |
Definition | When the condition was observed or the relative ranking. |
Control | 0..* |
Binding | The type of the diagnosis: admitting, principal, discharge. For example codes, see ExampleDiagnosisTypeCodes |
Type | CodeableConcept |
Requirements | Often required to capture a particular diagnosis, for example: primary or discharge. |
Comments | For example: admitting, primary, secondary, discharge. |
204. Claim.diagnosis.onAdmission | |
Definition | Indication of whether the diagnosis was present on admission to a facility. |
Control | 0..1 |
Binding | Present on admission. For example codes, see ExampleDiagnosisOnAdmissionCodes |
Type | CodeableConcept |
Requirements | Many systems need to understand for adjudication if the diagnosis was present a time of admission. |
205. Claim.diagnosis.packageCode | |
Definition | A package billing code or bundle code used to group products and services to a particular health condition (such as heart attack) which is based on a predetermined grouping code system. |
Control | 0..1 |
Binding | The DRG codes associated with the diagnosis. For example codes, see ExampleDiagnosisRelatedGroupCodes |
Type | CodeableConcept |
Requirements | Required to relate the current diagnosis to a package billing code that is then referenced on the individual claim items which are specific to the health condition covered by the package code. |
Comments | For example DRG (Diagnosis Related Group) or a bundled billing code. A patient may have a diagnosis of a Myocardial Infarction and a DRG for HeartAttack would be assigned. The Claim item (and possible subsequent claims) would refer to the DRG for those line items that were for services related to the heart attack event. |
206. Claim.procedure | |
Definition | Procedures performed on the patient relevant to the billing items with the claim. |
Control | 0..* |
Type | BackboneElement |
Requirements | The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
207. Claim.procedure.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
208. Claim.procedure.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
209. Claim.procedure.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
210. Claim.procedure.sequence | |
Definition | A number to uniquely identify procedure entries. |
Control | 1..1 |
Type | positiveInt |
Requirements | Necessary to provide a mechanism to link to claim details. |
211. Claim.procedure.type | |
Definition | When the condition was observed or the relative ranking. |
Control | 0..* |
Binding | Example procedure type codes. For example codes, see ExampleProcedureTypeCodes |
Type | CodeableConcept |
Requirements | Often required to capture a particular diagnosis, for example: primary or discharge. |
Comments | For example: primary, secondary. |
212. Claim.procedure.date | |
Definition | Date and optionally time the procedure was performed. |
Control | 0..1 |
Type | dateTime |
Requirements | Required for auditing purposes. |
213. Claim.procedure.procedure[x] | |
Definition | The code or reference to a Procedure resource which identifies the clinical intervention performed. |
Control | 1..1 |
Binding | Example ICD10 Procedure codes. For example codes, see ICD-10ProcedureCodes |
Type | Choice of: CodeableConcept, Reference(Procedure) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | This identifies the actual clinical procedure. |
214. Claim.procedure.udi | |
Definition | Unique Device Identifiers associated with this line item. |
Control | 0..* |
Type | Reference(Device) |
Requirements | The UDI code allows the insurer to obtain device level information on the product supplied. |
215. Claim.insurance | |
Definition | Financial instruments for reimbursement for the health care products and services specified on the claim. |
Control | 1..1 |
Type | BackboneElement |
Must Support | true |
Requirements | At least one insurer is required for a claim to be a claim. |
Comments | 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. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
216. Claim.insurance.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
217. Claim.insurance.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
218. Claim.insurance.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
219. Claim.insurance.sequence | |
Definition | A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | To maintain order of the coverages. |
Fixed Value | 1 |
220. Claim.insurance.focal | |
Definition | A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true. |
Control | 1..1 |
Type | boolean |
Must Support | true |
Requirements | To identify which coverage in the list is being used to adjudicate this claim. |
Comments | A patient may (will) have multiple insurance policies which provide reimbursement for healthcare services and products. For example a person may also be covered by their spouse's policy and both appear in the list (and may be from the same insurer). This flag will be set to true for only one of the listed policies and that policy will be used for adjudicating this claim. Other claims would be created to request adjudication against the other listed policies. |
Fixed Value | true |
221. Claim.insurance.identifier | |
Definition | The business identifier to be used when the claim is sent for adjudication against this insurance policy. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..1 |
Type | Identifier |
Requirements | This will be the claim number should it be necessary to create this claim in the future. This is provided so that payors may forward claims to other payors in the Coordination of Benefit for adjudication rather than the provider being required to initiate each adjudication. |
Comments | Only required in jurisdictions where insurers, rather than the provider, are required to send claims to insurers that appear after them in the list. This element is not required when 'subrogation=true'. |
222. Claim.insurance.coverage | |
Definition | Reference to the insurance card level information contained in the Coverage resource. The coverage issuing insurer will use these details to locate the patient's actual coverage within the insurer's information system. |
Control | 1..1 |
Type | Reference(Coverage) |
Must Support | true |
Requirements | Required to allow the adjudicator to locate the correct policy and history within their information system. |
223. Claim.insurance.businessArrangement | |
Definition | A business agreement number established between the provider and the insurer for special business processing purposes. |
Control | 0..1 |
Type | string |
Requirements | Providers may have multiple business arrangements with a given insurer and must supply the specific contract number for adjudication. |
224. Claim.insurance.preAuthRef | |
Definition | Reference numbers previously provided by the insurer to the provider to be quoted on subsequent claims containing services or products related to the prior authorization. |
Control | 0..* |
Type | string |
Requirements | Providers must quote previously issued authorization reference numbers in order to obtain adjudication as previously advised on the Preauthorization. |
Comments | This value is an alphanumeric string that may be provided over the phone, via text, via paper, or within a ClaimResponse resource and is not a FHIR Identifier. |
225. Claim.insurance.claimResponse | |
Definition | The result of the adjudication of the line items for the Coverage specified in this insurance. |
Control | 0..1 |
Type | Reference(ClaimResponse) |
Requirements | An insurer need the adjudication results from prior insurers to determine the outstanding balance remaining by item for the items in the curent claim. |
Comments | Must not be specified when 'focal=true' for this insurance. |
226. Claim.accident | |
Definition | Details of an accident which resulted in injuries which required the products and services listed in the claim. |
Control | 0..1 |
Type | BackboneElement |
Must Support | true |
Requirements | When healthcare products and services are accident related, benefits may be payable under accident provisions of policies, such as automotive, etc before they are payable under normal health insurance. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
227. Claim.accident.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
228. Claim.accident.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
229. Claim.accident.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
230. Claim.accident.date | |
Definition | Date of an accident event related to the products and services contained in the claim. |
Control | 1..1 |
Type | date |
Must Support | true |
Requirements | Required for audit purposes and adjudication. |
Comments | The date of the accident has to precede the dates of the products and services but within a reasonable timeframe. |
231. Claim.accident.type | |
Definition | The type or context of the accident event for the purposes of selection of potential insurance coverages and determination of coordination between insurers. |
Control | 0..1 |
Binding | Type of accident: work place, auto, etc. The codes SHALL be taken from V3 Value SetActIncidentCode; other codes may be used where these codes are not suitable |
Type | CodeableConcept |
Requirements | Coverage may be dependant on the type of accident. |
232. Claim.accident.location[x] | |
Definition | The physical location of the accident event. |
Control | 0..1 |
Type | Choice of: Address, Reference(Location) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Required for audit purposes and determination of applicable insurance liability. |
233. Claim.item | |
Definition | A claim line. Either a simple product or service or a 'group' of details which can each be a simple items or groups of sub-details. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | The items to be processed for adjudication. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
234. Claim.item.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
235. Claim.item.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices on Claim.item.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
236. Claim.item.extension:ItemRequestedService | |
SliceName | ItemRequestedService |
Definition | Provides specific information about a service being requested. |
Control | 0..* This element is affected by the following invariants: ele-1 |
Type | Extension(RequestedService) (Extension Type: Reference) |
Must Support | true |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
237. Claim.item.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
238. Claim.item.sequence | |
Definition | A number to uniquely identify item entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to provide a mechanism to link to items from within the claim and within the adjudication details of the ClaimResponse. |
239. Claim.item.careTeamSequence | |
Definition | CareTeam members related to this service or product. |
Control | 0..* |
Type | positiveInt |
Requirements | Need to identify the individuals and their roles in the provision of the product or service. |
240. Claim.item.diagnosisSequence | |
Definition | Diagnosis applicable for this service or product. |
Control | 0..* |
Type | positiveInt |
Must Support | true |
Requirements | Need to related the product or service to the associated diagnoses. |
241. Claim.item.procedureSequence | |
Definition | Procedures applicable for this service or product. |
Control | 0..* |
Type | positiveInt |
Requirements | Need to provide any listed specific procedures to support the product or service being claimed. |
242. Claim.item.informationSequence | |
Definition | Exceptions, special conditions and supporting information applicable for this service or product. |
Control | 0..* |
Type | positiveInt |
Must Support | true |
Requirements | Need to reference the supporting information items that relate directly to this product or service. |
243. Claim.item.revenue | |
Definition | The type of revenue or cost center providing the product and/or service. |
Control | 0..1 |
Binding | Codes for the revenue or cost centers supplying the service and/or products. For example codes, see ExampleRevenueCenterCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Needed in the processing of institutional claims. |
244. Claim.item.category | |
Definition | Code to identify the general type of benefits under which products and services are provided. |
Control | 0..1 |
Binding | Benefit categories such as: oral-basic, major, glasses. For example codes, see BenefitCategoryCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Needed in the processing of institutional claims as this allows the insurer to determine whether a facial X-Ray is for dental, orthopedic, or facial surgery purposes. |
Comments | Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage. |
245. Claim.item.productOrService | |
Definition | When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. |
Control | 1..1 |
Binding | Allowable service and product codes. For example codes, see USCLSCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Necessary to state what was provided or done. |
Alternate Names | Drug Code, Bill Code, Service Code |
Comments | 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'. |
246. Claim.item.modifier | |
Definition | Item typification or modifiers codes to convey additional context for the product or service. |
Control | 0..* |
Binding | Item type or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or an appliance was lost or stolen. For example codes, see ModifierTypeCodes |
Type | CodeableConcept |
Requirements | To support inclusion of the item for adjudication or to charge an elevated fee. |
Comments | 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. |
247. Claim.item.programCode | |
Definition | Identifies the program under which this may be recovered. |
Control | 0..* |
Binding | Program specific reason codes. For example codes, see ExampleProgramReasonCodes |
Type | CodeableConcept |
Requirements | Commonly used in in the identification of publicly provided program focused on population segments or disease classifications. |
Comments | For example: Neonatal program, child dental program or drug users recovery program. |
248. Claim.item.serviced[x] | |
Definition | The date or dates when the service or product was supplied, performed or completed. |
Control | 0..1 |
Type | Choice of: date, Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Needed to determine whether the service or product was provided during the term of the insurance coverage. |
249. Claim.item.location[x] | |
Definition | Where the product or service was provided. |
Control | 0..1 |
Type | Reference |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | The location can alter whether the item was acceptable for insurance purposes or impact the determination of the benefit amount. |
Slicing | This element introduces a set of slices on Claim.item.location[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
|
250. Claim.item.location[x]:locationReference | |
SliceName | locationReference |
Definition | Where the product or service was provided. |
Control | 0..1 |
Type | Reference(Location) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Must Support | true |
Requirements | The location can alter whether the item was acceptable for insurance purposes or impact the determination of the benefit amount. |
251. Claim.item.quantity | |
Definition | The number of repetitions of a service or product. |
Control | 0..1 |
Type | Quantity(SimpleQuantity) |
Requirements | Required when the product or service code does not convey the quantity provided. |
252. Claim.item.unitPrice | |
Definition | If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. |
Control | 0..1 |
Type | Money |
Requirements | The amount charged to the patient by the provider for a single unit. |
253. Claim.item.factor | |
Definition | A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. |
Control | 0..1 |
Type | decimal |
Requirements | When discounts are provided to a patient (example: Senior's discount) then this must be documented for adjudication. |
Comments | To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10). |
254. Claim.item.net | |
Definition | The quantity times the unit price for an additional service or product or charge. |
Control | 0..1 |
Type | Money |
Requirements | Provides the total amount claimed for the group (if a grouper) or the line item. |
Comments | For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied. |
255. Claim.item.udi | |
Definition | Unique Device Identifiers associated with this line item. |
Control | 0..* |
Type | Reference(Device) |
Requirements | The UDI code allows the insurer to obtain device level information on the product supplied. |
256. Claim.item.bodySite | |
Definition | Physical service site on the patient (limb, tooth, etc.). |
Control | 0..1 |
Binding | The code for the teeth, quadrant, sextant and arch. For example codes, see OralSiteCodes |
Type | CodeableConcept |
Requirements | Allows insurer to validate specific procedures. |
Comments | For example: Providing a tooth code, allows an insurer to identify a provider performing a filling on a tooth that was previously removed. |
257. Claim.item.subSite | |
Definition | A region or surface of the bodySite, e.g. limb region or tooth surface(s). |
Control | 0..* |
Binding | The code for the tooth surface and surface combinations. For example codes, see SurfaceCodes |
Type | CodeableConcept |
Requirements | Allows insurer to validate specific procedures. |
258. Claim.item.encounter | |
Definition | The Encounters during which this Claim was created or to which the creation of this record is tightly associated. |
Control | 0..* |
Type | Reference(Encounter) |
Requirements | Used in some jurisdictions to link clinical events to claim items. |
Comments | This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
259. Claim.item.detail | |
Definition | A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. |
Control | 0..* |
Type | BackboneElement |
Must Support | true |
Requirements | The items to be processed for adjudication. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
260. Claim.item.detail.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
261. Claim.item.detail.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
262. Claim.item.detail.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
263. Claim.item.detail.sequence | |
Definition | A number to uniquely identify item entries. |
Control | 1..1 |
Type | positiveInt |
Must Support | true |
Requirements | Necessary to provide a mechanism to link to items from within the claim and within the adjudication details of the ClaimResponse. |
264. Claim.item.detail.revenue | |
Definition | The type of revenue or cost center providing the product and/or service. |
Control | 0..1 |
Binding | Codes for the revenue or cost centers supplying the service and/or products. For example codes, see ExampleRevenueCenterCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Needed in the processing of institutional claims. |
265. Claim.item.detail.category | |
Definition | Code to identify the general type of benefits under which products and services are provided. |
Control | 0..1 |
Binding | Benefit categories such as: oral-basic, major, glasses. For example codes, see BenefitCategoryCodes |
Type | CodeableConcept |
Requirements | Needed in the processing of institutional claims as this allows the insurer to determine whether a facial X-Ray is for dental, orthopedic, or facial surgery purposes. |
Comments | Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage. |
266. Claim.item.detail.productOrService | |
Definition | When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. |
Control | 1..1 |
Binding | Allowable service and product codes. For example codes, see USCLSCodes |
Type | CodeableConcept |
Must Support | true |
Requirements | Necessary to state what was provided or done. |
Alternate Names | Drug Code, Bill Code, Service Code |
Comments | 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'. |
267. Claim.item.detail.modifier | |
Definition | Item typification or modifiers codes to convey additional context for the product or service. |
Control | 0..* |
Binding | Item type or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or an appliance was lost or stolen. For example codes, see ModifierTypeCodes |
Type | CodeableConcept |
Requirements | To support inclusion of the item for adjudication or to charge an elevated fee. |
Comments | For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or out of office hours. |
268. Claim.item.detail.programCode | |
Definition | Identifies the program under which this may be recovered. |
Control | 0..* |
Binding | Program specific reason codes. For example codes, see ExampleProgramReasonCodes |
Type | CodeableConcept |
Requirements | Commonly used in in the identification of publicly provided program focused on population segments or disease classifications. |
Comments | For example: Neonatal program, child dental program or drug users recovery program. |
269. Claim.item.detail.quantity | |
Definition | The number of repetitions of a service or product. |
Control | 0..1 |
Type | Quantity(SimpleQuantity) |
Must Support | true |
Requirements | Required when the product or service code does not convey the quantity provided. |
270. Claim.item.detail.unitPrice | |
Definition | If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. |
Control | 0..1 |
Type | Money |
Must Support | true |
Requirements | The amount charged to the patient by the provider for a single unit. |
271. Claim.item.detail.factor | |
Definition | A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. |
Control | 0..1 |
Type | decimal |
Requirements | When discounts are provided to a patient (example: Senior's discount) then this must be documented for adjudication. |
Comments | To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10). |
272. Claim.item.detail.net | |
Definition | The quantity times the unit price for an additional service or product or charge. |
Control | 0..1 |
Type | Money |
Requirements | Provides the total amount claimed for the group (if a grouper) or the line item. |
Comments | For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied. |
273. Claim.item.detail.udi | |
Definition | Unique Device Identifiers associated with this line item. |
Control | 0..* |
Type | Reference(Device) |
Requirements | The UDI code allows the insurer to obtain device level information on the product supplied. |
274. Claim.item.detail.subDetail | |
Definition | A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items. |
Control | 0..* |
Type | BackboneElement |
Requirements | The items to be processed for adjudication. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
275. Claim.item.detail.subDetail.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
276. Claim.item.detail.subDetail.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
277. Claim.item.detail.subDetail.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Requirements | 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. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
278. Claim.item.detail.subDetail.sequence | |
Definition | A number to uniquely identify item entries. |
Control | 1..1 |
Type | positiveInt |
Requirements | Necessary to provide a mechanism to link to items from within the claim and within the adjudication details of the ClaimResponse. |
279. Claim.item.detail.subDetail.revenue | |
Definition | The type of revenue or cost center providing the product and/or service. |
Control | 0..1 |
Binding | Codes for the revenue or cost centers supplying the service and/or products. For example codes, see ExampleRevenueCenterCodes |
Type | CodeableConcept |
Requirements | Needed in the processing of institutional claims. |
280. Claim.item.detail.subDetail.category | |
Definition | Code to identify the general type of benefits under which products and services are provided. |
Control | 0..1 |
Binding | Benefit categories such as: oral-basic, major, glasses. For example codes, see BenefitCategoryCodes |
Type | CodeableConcept |
Requirements | Needed in the processing of institutional claims as this allows the insurer to determine whether a facial X-Ray is for dental, orthopedic, or facial surgery purposes. |
Comments | Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage. |
281. Claim.item.detail.subDetail.productOrService | |
Definition | When the value is a group code then this item collects a set of related claim details, otherwise this contains the product, service, drug or other billing code for the item. |
Control | 1..1 |
Binding | Allowable service and product codes. For example codes, see USCLSCodes |
Type | CodeableConcept |
Requirements | Necessary to state what was provided or done. |
Comments | 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'. |
282. Claim.item.detail.subDetail.modifier | |
Definition | Item typification or modifiers codes to convey additional context for the product or service. |
Control | 0..* |
Binding | Item type or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or an appliance was lost or stolen. For example codes, see ModifierTypeCodes |
Type | CodeableConcept |
Requirements | To support inclusion of the item for adjudication or to charge an elevated fee. |
Comments | For example in Oral whether the treatment is cosmetic or associated with TMJ, or for Medical whether the treatment was outside the clinic or out of office hours. |
283. Claim.item.detail.subDetail.programCode | |
Definition | Identifies the program under which this may be recovered. |
Control | 0..* |
Binding | Program specific reason codes. For example codes, see ExampleProgramReasonCodes |
Type | CodeableConcept |
Requirements | Commonly used in in the identification of publicly provided program focused on population segments or disease classifications. |
Comments | For example: Neonatal program, child dental program or drug users recovery program. |
284. Claim.item.detail.subDetail.quantity | |
Definition | The number of repetitions of a service or product. |
Control | 0..1 |
Type | Quantity(SimpleQuantity) |
Requirements | Required when the product or service code does not convey the quantity provided. |
285. Claim.item.detail.subDetail.unitPrice | |
Definition | If the item is not a group then this is the fee for the product or service, otherwise this is the total of the fees for the details of the group. |
Control | 0..1 |
Type | Money |
Requirements | The amount charged to the patient by the provider for a single unit. |
286. Claim.item.detail.subDetail.factor | |
Definition | A real number that represents a multiplier used in determining the overall value of services delivered and/or goods received. The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. |
Control | 0..1 |
Type | decimal |
Requirements | When discounts are provided to a patient (example: Senior's discount) then this must be documented for adjudication. |
Comments | To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10). |
287. Claim.item.detail.subDetail.net | |
Definition | The quantity times the unit price for an additional service or product or charge. |
Control | 0..1 |
Type | Money |
Requirements | Provides the total amount claimed for the group (if a grouper) or the line item. |
Comments | For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied. |
288. Claim.item.detail.subDetail.udi | |
Definition | Unique Device Identifiers associated with this line item. |
Control | 0..* |
Type | Reference(Device) |
Requirements | The UDI code allows the insurer to obtain device level information on the product supplied. |
289. Claim.total | |
Definition | The total value of the all the items in the claim. |
Control | 0..1 |
Type | Money |
Requirements | Used for control total purposes. |