Generated Narrative: StructureDefinition davinci-pct-gfe-professional Name Flags Card. Type Description & Constraints Claim Claim #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:gfeServiceLinkingInfo S 0..1 (Complex) GFE Service Linking Information URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/gfeServiceLinkingInfo #xD; extension:providerEventMethodology S 0..1 string Provider event collection methodology URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/providerEventMethodology #xD; extension:gfeDisclaimer S 0..* string Disclaimers the patient should be made aware of regarding the providers estimate, e.g. application of sliding scale for self-pay/uninsured patients URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/gfeDisclaimer #xD; Slices for identifier 1..* Identifier Business Identifier for claim Slice: Unordered, Open by value:type #xD; identifier:PLAC 1..1 Identifier Provider Assigned Identifier for GFE Claim #xD; type 1..1 CodeableConcept Description of identifier Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: PLAC #xD; display 1..1 string Representation defined by the system Fixed Value: Placer Identifier #xD; system S 0..1 uri The namespace for the identifier value #xD; value 1..1 string The value that is unique #xD; type 1..1 CodeableConcept Category or discipline Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/claim-type #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: professional #xD; use 1..1 code claim | preauthorization | predetermination Required Pattern: predetermination #xD; patient 1..1 Reference(US Core Patient Profile(7.0.0)) The recipient of the products and services #xD; insurer 0..1 Reference(PCT Organization) Target #xD; provider 1..1 Reference(PCT Organization | PCT Practitioner) Billing provider - party responsible for the GFE #xD; extension 1..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:providerTaxonomy 1..1 CodeableConcept Provider taxonomy codes consisting of NUCC Health Care Provider Taxonomy Code Set for providers URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/providerTaxonomy Binding: US Core Provider Role (NUCC) (extensible) #xD; extension:consentForBalanceBilling S 0..1 boolean Extension URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/gfeConsentForBalanceBilling #xD; priority 1..1 CodeableConcept Desired processing ugency Binding: ProcessPriorityCodes (required) #xD; payee S 0..1 BackboneElement Recipient of benefits payable #xD; party 0..1 Reference(PCT Practitioner | PCT Organization) Recipient reference #xD; referral #xD; extension 1..* Extension Extension #xD; Slices for extension Content/Rules for all slices #xD; extension:referralNumber 1..1 string Referral Number URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/referralNumber #xD; Slices for careTeam S 0..* BackboneElement Members of the care team Slice: Unordered, Open by value:role #xD; careTeam:All Slices Content/Rules for all slices #xD; provider 1..1 Reference(PCT Practitioner | PCT Organization) Practitioner or organization #xD; role 1..1 CodeableConcept Function within the team Binding: PCT Care Team Role Value Set (required) #xD; qualification 0..1 CodeableConcept Practitioner credential or specialization Binding: US Core Provider Role (NUCC) (required) #xD; careTeam:rendering S 0..* BackboneElement Members of the care team #xD; role 1..1 CodeableConcept Function within the team Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/claimcareteamrole #xD; version 1..1 string Version of the system - if relevant Fixed Value: 1.0.1 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: rendering #xD; qualification 1..1 CodeableConcept Practitioner credential or specialization - must provide a taxonomy code for the Professional case #xD; careTeam:referring S 0..1 BackboneElement Members of the care team #xD; role 1..1 CodeableConcept Function within the team Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/claimcareteamrole #xD; version 1..1 string Version of the system - if relevant Fixed Value: 1.0.1 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: referring #xD; Slices for supportingInfo S 0..* BackboneElement Supporting information Slice: Unordered, Open by value:category #xD; supportingInfo:All Slices Content/Rules for all slices #xD; category 1..1 CodeableConcept Classification of the supplied information Binding: PCT Supporting Info Type Value Set (extensible) #xD; supportingInfo:serviceFacility S 0..1 BackboneElement Service Facility #xD; category 1..1 CodeableConcept Classification of the supplied information Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTSupportingInfoType #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: servicefacility #xD; Slices for value[x] 1..1 Reference(Resource) Data to be provided Slice: Unordered, Open by type:$this #xD; value[x]:valueReference 1..1 Reference(PCT Organization) Data to be provided #xD; supportingInfo:claimFrequency S 0..1 BackboneElement Claim Frequency component of the UB-04 Type of Bill Code (4th digit of the UB-04 Type of Bill code). #xD; category 1..1 CodeableConcept Classification of the supplied information Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTSupportingInfoType #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: claimFrequency #xD; code 1..1 CodeableConcept Type of information Binding: PCT GFE NUBC Uniform Billing (UB-04) Type of Bill Value Set (required) #xD; Slices for diagnosis S 0..* BackboneElement Pertinent diagnosis information Slice: Unordered, Open by value:type #xD; diagnosis:All Slices Content/Rules for all slices #xD; type S 0..* CodeableConcept Timing or nature of the diagnosis Binding: Diagnosis Type Codes (required) #xD; diagnosis:principal S 0..1 BackboneElement Principal Diagnosis - Must Support means the information source SHALL be capable of populating and SHALL populate if available and permitted. #xD; sequence 1..1 positiveInt Diagnosis instance identifier Required Pattern: 1 #xD; diagnosis[x] 1..1 CodeableConcept Nature of illness or problem Binding: PCT ICD-10 Diagnostic Codes (required) #xD; type 1..1 CodeableConcept Timing or nature of the diagnosis Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/diagnosistype #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: principal #xD; diagnosis:other S 0..11 BackboneElement Pertinent diagnosis information #xD; diagnosis[x] 1..1 CodeableConcept Nature of illness or problem Binding: PCT ICD-10 Diagnostic Codes (required) #xD; type 1..1 CodeableConcept Timing or nature of the diagnosis Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/diagnosistype #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: secondary #xD; Slices for procedure S 0..* BackboneElement Clinical procedures performed Slice: Unordered, Open by value:type #xD; procedure:All Slices Content/Rules for all slices #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:serviceDescription 1..1 string Service Description URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/serviceDescription #xD; type S 0..* CodeableConcept Category of Procedure Binding: PCT Procedure Type Value Set (required) #xD; procedure:anesthesiaRelated S 0..2 BackboneElement Clinical procedures performed #xD; Slices for extension Content/Rules for all slices #xD; extension:serviceDescription 1..1 string Service Description URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/serviceDescription #xD; type 1..1 CodeableConcept Category of Procedure Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTProcedureType #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: procedureRequiringAnesthesia #xD; procedure[x] 1..1 CodeableConcept Specific clinical procedure Binding: PCT CMS HCPCS and AMA CPT Procedure Surgical Codes (required) #xD; procedure:other S 0..24 BackboneElement Clinical procedures performed #xD; Slices for extension Content/Rules for all slices #xD; extension:serviceDescription 1..1 string Service Description URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/serviceDescription #xD; type 1..1 CodeableConcept Category of Procedure Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTProcedureType #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: other #xD; procedure[x] 1..1 CodeableConcept Specific clinical procedure Binding: PCT CMS HCPCS and AMA CPT Procedure Surgical Codes (required) #xD; insurance #xD; coverage 1..1 Reference(PCT Coverage) Insurance information #xD; Slices for extension Content/Rules for all slices #xD; extension:dataAbsentReason S 0..1 code Coverage may be not applicable if estimate is for self-pay or uninsured URL: http://hl7.org/fhir/StructureDefinition/data-absent-reason Binding: DataAbsentReason (required) #xD; preAuthRef 0..2 string Prior authorization reference number #xD; accident #xD; location[x] 0..1 Address Where the event occurred #xD; country 0..1 string Country (e.g. can be ISO 3166 2 or 3 letter code) Binding: Iso3166-1-2 (required) #xD; item 1..50 BackboneElement Product or service provided #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:referralNumber S 0..11 string Referral Number URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/referralNumber #xD; extension:gfeBillingProviderLineItemCtrlNum S 0..1 Identifier Extension URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/gfeBillingProviderLineItemCtrlNum #xD; extension:serviceDescription 1..1 string Service Description URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/serviceDescription #xD; extension:ProviderEventMethodology S 0..1 string Provider Event Methodology URL: http://hl7.org/fhir/us/davinci-pct/StructureDefinition/providerEventMethodology #xD; careTeamSequence S 0..* positiveInt Applicable careTeam members #xD; productOrService 1..1 CodeableConcept Billing, service, product, or drug code Binding: Claim Medical Product or Service Value Set (required) #xD; coding <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( pct-cpt-display )">C 0..* Coding Code defined by a terminology system Constraints: pct-cpt-display #xD; modifier S 0..4 CodeableConcept Product or service billing modifiers Binding: PCT GFE Item CPT - HCPCS Value Set (required) #xD; coding <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R4/conformance-rules.html#constraints" title="This element has or is affected by constraints ( pct-cpt-display )">C 0..* Coding Code defined by a terminology system Constraints: pct-cpt-display #xD; serviced[x] S 1..1 date, Period This is the planned or estimated date(s)s of service #xD; location[x] 1..1 CodeableConcept Place of service or where product was supplied Binding: PCT GFE CMS Place of Service Value Set (required) #xD; quantity 1..1 SimpleQuantity(4.0.1) Count of products or services #xD; unitPrice 1..1 Money Fee, charge or cost per item #xD; net 1..1 Money Total charge amount for the service line #xD; detail S 0..* BackboneElement Drug Identification Information #xD; productOrService 1..1 CodeableConcept Billing, service, product, or drug code Binding: Claim Medical Product or Service Value Set (required) #xD; quantity S 0..1 SimpleQuantity(4.0.1) Count of products or services #xD; total 1..1 Money Total GFE Charges Submitted #xD; Documentation for this format
HL7 International / Financial Management
PCT Good Faith Estimate Professional is a profile for an professional provider to capture estimation for items and services for the patient or, optionally, to submit to a payer (for patients using insurance). If submitting to a payer, this includes the data needed to be processed by a payer for the creation of an Advanced EOB. This profile is used for a professional GFE submission.
Claim, Pre-determination or Pre-authorization
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.
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
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()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
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()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
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.
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
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.
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.
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
This extension is used to provide the GFE Service Linking Information. This allows implementers to have the same identifier on multiple GFEs that are part of one period of care's services. This would be needed for some of the workflow options that businesses may decide to use.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
How the provider determined the number of claims and the number and type of billing providers to include in the GFE. Examples include provider episodes of care experience, PACES, order set based on clinical guidelines, payor suggested grouping, or some other method of determination. The extension definition contains additional detail.
Disclaimers the patient should be made aware of regarding the providers estimate, e.g. application of sliding scale for self-pay/uninsured patients
Disclaimers the patient should be made aware of regarding the providers estimate including any additional assumptions and requirements. Noting that that the information provided is only an estimate based on the items and services reasonably expected, at the time of scheduling (or requesting) the item or service, to be furnished and is subject to change.
These disclaimers may include, but are not limited to things such as: provider discounts (e.g. application of sliding fee scale), limitations, preconditions, requirements, assumptions (e.g. diagnostic vs. preventative), information known to be missing in the estimate, conditions that may affect the estimate, or anything that may affect the interpretation of the estimate.
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).
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.
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
A unique identifier assigned to this claim.
Allows claims to be distinguished and referenced.
Provider Assigned Identifier for GFE Claim
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
active | cancelled | draft | entered-in-error
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
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'.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
A code specifying the state of the resource instance.
The category of claim, e.g. oral, pharmacy, vision, institutional, professional.
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.
Claim type determine the general sets of business rules applied for information requirements and adjudication.
The type or discipline-style of the claim.
A finer grained suite of claim type codes which may convey additional information such as Inpatient vs Outpatient and/or a specialty service.
This may contain the local bill type codes, for example the US UB-04 bill type code or the CMS bill type.
Some jurisdictions need a finer grained claim type for routing and adjudication.
claim | preauthorization | predetermination
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.
This element is required to understand the nature of the request for adjudication.
The purpose of the Claim: predetermination, preauthorization, claim.
The recipient of the products and services
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.
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.
The period for which charges are being submitted.
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.
A number jurisdictions required the submission of the billing period when submitting claims for example for hospital stays or long-term care.
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.
Need to record a timestamp for use by both the recipient and the issuer.
Individual who created the claim, predetermination or preauthorization.
Some jurisdictions require the contact information for personnel completing claims.
The Insurer who is target of the request.
Billing provider - party responsible for the GFE
The provider which is responsible for the claim, predetermination or preauthorization.
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.
Provider taxonomy codes consisting of NUCC Health Care Provider Taxonomy Code Set for providers
This extension is used to indicate the taxonomy code of the provider.
If the provider has received a written consent form indicating a patient has agreed to waive their protections and pay up to the full cost for the out-of-network item or service, this will be “true”. If the provider has not received written consent, this will be “false”. This is an attestation only. The billing provider is legally required to maintain the written notice and consent form.
Literal reference, Relative, internal or absolute URL
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.
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.
Type the reference refers to (e.g. "Patient")
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).
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.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
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.
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).
Plain text narrative that identifies the resource in addition to the resource reference.
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.
The provider-required urgency of processing the request. Typical values include: stat, routine deferred.
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.
The provider may need to indicate their processing requirements so that the processor can indicate if they are unable to comply.
A code to indicate whether and for whom funds are to be reserved for future claims.
This field is only used for preauthorizations.
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.
For whom funds are to be reserved: (Patient, Provider, None).
Other claims which are related to this claim such as prior submissions or claims for related services or for the same event.
For example, for the original treatment and follow-up exams.
For workplace or other accidents it is common to relate separate claims arising from the same event.
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
A code to convey how the claims are related.
Some insurers need a declaration of the type of relationship.
Relationship of this claim to a related Claim.
An alternate organizational reference to the case or file to which this particular claim pertains.
For example, Property/Casualty insurer claim # or Workers Compensation case # .
In cases where an event-triggered claim is being submitted to an insurer which requires a reference number to be specified on all exchanges.
Prescription authorizing services and products
Prescription to support the dispensing of pharmacy, device or vision products.
Required to authorize the dispensing of controlled substances and devices.
Original prescription if superseded by fulfiller
Original prescription which has been superseded by this prescription to support the dispensing of pharmacy services, medications or products.
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'.
Often required when a fulfiller varies what is fulfilled from that authorized on the original prescription.
The party to be reimbursed for cost of the products and services according to the terms of the policy.
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.
The provider needs to specify who they wish to be reimbursed and the claims processor needs express who they will reimburse.
Type of Party to be reimbursed: subscriber, provider, other.
Need to know who should receive payment with the most common situations being the Provider (assignment of benefits) or the Subscriber.
Reference to the individual or organization to whom any payment will be made.
Not required if the payee is 'subscriber' or 'provider'.
Need to provide demographics if the payee is not 'subscriber' nor 'provider'.
The referral resource which lists the date, practitioner, reason and other supporting information.
Some insurers require proof of referral to pay for services or to pay specialist rates for services.
This extension is used to provide the Referral Number.
Facility where the services were provided.
Insurance adjudication can be dependant on where services were delivered.
The members of the team who provided the products and services.
Common to identify the responsible and supporting practitioners.
A number to uniquely identify care team entries.
Necessary to maintain the order of the care team and provide a mechanism to link individuals to claim details.
Member of the team who provided the product or service.
Often a regulatory requirement to specify the responsible provider.
The party who is billing and/or responsible for the claimed products or services.
Responsible might not be required when there is only a single provider listed.
When multiple parties are present it is required to distinguish the lead or responsible individual.
The lead, assisting or supervising practitioner and their discipline if a multidisciplinary team.
Role might not be required when there is only a single provider listed.
When multiple parties are present it is required to distinguish the roles performed by each member.
Practitioner credential or specialization
The qualification of the practitioner which is applicable for this service.
Need to specify which qualification a provider is delivering the product or service under.
Practitioner credential or specialization - must provide a taxonomy code for the Professional case
Additional information codes regarding exceptions, special considerations, the condition, situation, prior or concurrent issues.
Often there are multiple jurisdiction specific valuesets which are required.
Typically these information codes are required to support the services rendered or the adjudication of the services rendered.
Attachments Exception Codes Occurrence Codes Value codes
A number to uniquely identify supporting information entries.
Necessary to maintain the order of the supporting information items and provide a mechanism to link to claim details.
Classification of the supplied information
The general class of the information supplied: information; exception; accident, employment; onset, etc.
This may contain a category for the local bill type codes.
Required to group or associate information items with common characteristics. For example: admission information or prior treatments.
System and code pertaining to the specific information regarding special conditions relating to the setting, treatment or patient for which care is sought.
Required to identify the kind of additional information.
The valuset used for additional information codes.
The date when or period to which this information refers.
Additional data or information such as resources, documents, images etc. including references to the data or the actual inclusion of the data.
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.
To convey the data content to be provided when the information is more than a simple code or period.
Provides the reason in the situation where a reason code is required in addition to the content.
For example: the reason for the additional stay, or why a tooth is missing.
Needed when the supporting information has both a date and amount/value and requires explanation.
Service Facility Location information conveys the name, full address and identifier of the facility where services were rendered when that is different from the Billing/Performing Provider.
Claim Frequency component of the UB-04 Type of Bill Code (4th digit of the UB-04 Type of Bill code).
For the purposes of Patient Cost Transparency Estimates, this field may be used to modify or replace a GFE claim estimate within the same GFE Packet submission. This specification does not support the modification of Claim resources outside of the GFE Packet and client systems SHALL NOT expect the inclusion of the frequency code to affect the use or interpretation of any Claim outside of the GFE Packet.
Information about diagnoses relevant to the claim items.
Required for the adjudication by provided context for the services and product listed.
A number to uniquely identify diagnosis entries.
Diagnosis are presented in list order to their expected importance: primary, secondary, etc.
Necessary to maintain the order of the diagnosis items and provide a mechanism to link to claim details.
The nature of illness or problem in a coded form or as a reference to an external defined Condition.
Provides health context for the evaluation of the products and/or services.
When the condition was observed or the relative ranking.
For example: admitting, primary, secondary, discharge.
Often required to capture a particular diagnosis, for example: primary or discharge.
Indication of whether the diagnosis was present on admission to a facility.
Many systems need to understand for adjudication if the diagnosis was present a time of admission.
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.
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.
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.
The DRG codes associated with the diagnosis.
Principal Diagnosis - Must Support means the information source SHALL be capable of populating and SHALL populate if available and permitted.
If the Principal Diagnosis code is known, it is important that it be shared in the GFE, particularly when the GFE is being sent to a payer for an insured patient. Payers very often need the diagnosis to be able to provide an estimate. Without the diagnosis, payers may assume the service is diagnostic and thus the patient responsibility may be higher or not covered at all than the diagnosis, such as for preventative services, would otherwise indicate. It is understood that in certain situations, such as scheduled services or GFE requests prior to orders, diagnosis is not needed or may not yet be known. However, when it is known, it is important that this information be shared to ensure the best possible estimate is provided to the patient.
Procedures performed on the patient relevant to the billing items with the claim.
The specific clinical invention are sometimes required to be provided to justify billing a greater than customary amount for a service.
This extension is used to communicate a plain language description of the procedure, product, or service.
A number to uniquely identify procedure entries.
Necessary to provide a mechanism to link to claim details.
Date and optionally time the procedure was performed.
The code or reference to a Procedure resource which identifies the clinical intervention performed.
This identifies the actual clinical procedure.
Unique Device Identifiers associated with this line item.
The UDI code allows the insurer to obtain device level information on the product supplied.
Financial instruments for reimbursement for the health care products and services specified on the claim.
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.
At least one insurer is required for a claim to be a claim.
A number to uniquely identify insurance entries and provide a sequence of coverages to convey coordination of benefit order.
A flag to indicate that this Coverage is to be used for adjudication of this claim when set to true.
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.
To identify which coverage in the list is being used to adjudicate this claim.
The business identifier to be used when the claim is sent for adjudication against this insurance policy.
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'.
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.
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.
Required to allow the adjudicator to locate the correct policy and history within their information system.
Coverage may be not applicable if estimate is for self-pay or uninsured
Provides a reason why the expected value or elements in the element that is extended are missing.
A business agreement number established between the provider and the insurer for special business processing purposes.
Providers may have multiple business arrangements with a given insurer and must supply the specific contract number for adjudication.
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.
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.
Providers must quote previously issued authorization reference numbers in order to obtain adjudication as previously advised on the Preauthorization.
The result of the adjudication of the line items for the Coverage specified in this insurance.
Must not be specified when 'focal=true' for this insurance.
An insurer need the adjudication results from prior insurers to determine the outstanding balance remaining by item for the items in the curent claim.
Details of an accident which resulted in injuries which required the products and services listed in the claim.
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.
Date of an accident event related to the products and services contained in the claim.
The date of the accident has to precede the dates of the products and services but within a reasonable timeframe.
Required for audit purposes and adjudication.
The type or context of the accident event for the purposes of selection of potential insurance coverages and determination of coordination between insurers.
Coverage may be dependant on the type of accident.
Type of accident: work place, auto, etc.
The physical location of the accident event.
Required for audit purposes and determination of applicable insurance liability.
home | work | temp | old | billing - purpose of this address
Applications can assume that an address is current unless it explicitly says that it is temporary or old.
Allows an appropriate address to be chosen from a list of many.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.
The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the [Location](http://hl7.org/fhir/R4/location.html#) resource).
The type of an address (physical / postal).
Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.
Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.
XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
Street name, number, direction & P.O. Box etc.
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.
The order in which lines should appear in an address label
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
The name of the city, town, suburb, village or other community or delivery center.
The name of the administrative area (county).
District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.
Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).
A postal code designating a region defined by the postal service.
Country (e.g. can be ISO 3166 2 or 3 letter code)
Country - a nation as commonly understood or generally accepted.
ISO 3166 3 letter codes can be used in place of a human readable country name.
Allows addresses to be placed in historical context.
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.
The items to be processed for adjudication.
This extension is used by the provider to assign a unique identifier to this item. The intent of this element is to allow the provider to assign something other than 'line number' for their purposes (e.g. tracking and troubleshooting).
This extension is used for indicating the method a provider used to group services, and those providing such services, beyond what may be indicated through DRGs that the payer or patient may find helpful (e.g. grouping services by a standardized episode of care definition). This is provider generated text and should not be modified by the payer.
The method a provider used to group services. The extension definition contains additional detail.
A number to uniquely identify item entries.
Necessary to provide a mechanism to link to items from within the claim and within the adjudication details of the ClaimResponse.
CareTeam members related to this service or product.
Need to identify the individuals and their roles in the provision of the product or service.
Diagnosis applicable for this service or product.
Need to related the product or service to the associated diagnoses.
Procedures applicable for this service or product.
Need to provide any listed specific procedures to support the product or service being claimed.
Applicable exception and supporting information
Exceptions, special conditions and supporting information applicable for this service or product.
Need to reference the supporting information items that relate directly to this product or service.
The type of revenue or cost center providing the product and/or service.
Needed in the processing of institutional claims.
Codes for the revenue or cost centers supplying the service and/or products.
Code to identify the general type of benefits under which products and services are provided.
Examples include Medical Care, Periodontics, Renal Dialysis, Vision Coverage.
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.
Benefit categories such as: oral-basic, major, glasses.
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.
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'.
Necessary to state what was provided or done.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
CPT codes require a display value (CPT Consumer Friendly Descriptors recommended)
system = 'http://www.ama-assn.org/go/cpt' implies display.exists()
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Item typification or modifiers codes to convey additional context for the product or service.
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.
To support inclusion of the item for adjudication or to charge an elevated fee.
Program the product or service is provided under
Identifies the program under which this may be recovered.
For example: Neonatal program, child dental program or drug users recovery program.
Commonly used in in the identification of publicly provided program focused on population segments or disease classifications.
This is the planned or estimated date(s)s of service
This is the planned or estimated dates of service. Use Revenue code to determine inpatient stays if needed for adjudication
Needed to determine whether the service or product was provided during the term of the insurance coverage.
Place of service or where product was supplied
Where the product or service was provided.
The location can alter whether the item was acceptable for insurance purposes or impact the determination of the benefit amount.
The number of repetitions of a service or product.
Required when the product or service code does not convey the quantity provided.
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.
The amount charged to the patient by the provider for a single unit.
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.
To show a 10% senior's discount, the value entered is: 0.90 (1.00 - 0.10).
When discounts are provided to a patient (example: Senior's discount) then this must be documented for adjudication.
Total charge amount for the service line
The quantity times the unit price for an additional service or product or charge.
For example, the formula: quantity * unitPrice * factor = net. Quantity and factor are assumed to be 1 if not supplied.
Provides the total amount claimed for the group (if a grouper) or the line item.
Physical service site on the patient (limb, tooth, etc.).
For example: Providing a tooth code, allows an insurer to identify a provider performing a filling on a tooth that was previously removed.
Allows insurer to validate specific procedures.
The code for the teeth, quadrant, sextant and arch.
A region or surface of the bodySite, e.g. limb region or tooth surface(s).
The code for the tooth surface and surface combinations.
The Encounters during which this Claim was created or to which the creation of this record is tightly associated.
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.
Used in some jurisdictions to link clinical events to claim items.
A claim detail line. Either a simple (a product or service) or a 'group' of sub-details which are simple items.
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.
Item type or modifiers codes, eg for Oral whether the treatment is cosmetic or associated with TMJ, or an appliance was lost or stolen.
The total value of the all the items in the claim.