Generated Narrative: StructureDefinition adt-notification-coverage Name Flags Card. Type Description & Constraints Coverage 0..* USCoreCoverageProfile(7.0.0) Insurance or medical plan or a payment agreement This profile also complies with the profile US Core Coverage Profile (6.1.0) beneficiary 1..1 Reference(US Core Patient Profile(7.0.0)) {b} Plan beneficiary Documentation for this format
Da Vinci Admit/Discharge/Transfer Notification Coverage Profile
HL7 International / Infrastructure And Messaging
The Da Vinci Admit/Discharge/Transfer Notification Coverage Profile is based on the [HRex Coverage Profile](http://build.fhir.org/ig/HL7/davinci-ehrx/StructureDefinition-hrex-coverage.html) and constrains the Patient resource referenced by the `Coverage.beneficiary` element to be found in the same message Bundle. The Da Vinci Admit/Discharge/Transfer Notification Coverage Profile is based on the US Core Coverage Profile and complies with US Core versions 6.1.0, and 7.0.0. It constrains the resources referenced by the `Coverage.beneficiary` element to the US Core Patient Profile. It also constrains the referenced resource to be an entry in the message Bundle that it populates.
Used by permission of HL7 International, all rights reserved Creative Commons License
Canadian Dental Association eclaims standard
Canadian Pharmacy Associaiton eclaims standard
Insurance or medical plan or a payment agreement
Financial instrument which may be used to reimburse or pay for health care products and services. Includes both insurance and self-payment.
The Coverage resource contains the insurance card level information, which is customary to provide on claims and other communications between providers and insurers.
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
Member Id in Coverage.identifier or Coverage.subscriberId SHALL be present
identifier.type.coding.where(system='http://terminology.hl7.org/CodeSystem/v2-0203' and code='MB').exists() or subscriberId.exists()
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.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. 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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
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).
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 coverage.
The main (and possibly only) identifier for the coverage - often referred to as a Member Id, Certificate number, Personal Health Number or Case ID. May be constructed as the concatenation of the Coverage.SubscriberID and the Coverage.dependant.
Allows coverages to be distinguished and referenced.
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
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
The `Coverage.status` alone does not indicate whether an individual's coverage is terminated or that the individual is not covered. The `Coverage.period` needs to be considered as well.
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 labelled 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.
Coverage category such as medical or accident
The type of coverage: social program, medical plan, accident coverage (workers compensation, auto), group health or payment by an individual or organization.
Identifies if the coverage is PPO, HMO, POS, etc.
The order of application of coverages is dependent on the types of coverage.
US Public Health Data Consortium Source of Payment Codes
The party who 'owns' the insurance policy.
For example: may be an individual, corporation or the subscriber's employer.
This provides employer information in the case of Worker's Compensation and other policies.
IN1-16, 18, 19-name of insured, address, date of birth
The party who has signed-up for or 'owns' the contractual relationship to the policy or to whom the benefit of the policy for services rendered to them or their family is due.
May be self or a parent in the case of dependants.
This is the party who is entitled to the benfits under the policy.
The insurer assigned ID for the Subscriber.
The identifier assigned by the Payer on the subscriber's ID card
The insurer requires this identifier on correspondance and claims (digital and otherwise).
The party who benefits from the insurance coverage; the patient when products and/or services are provided.
Identifier for a member assigned by the Payer.
This is the party who receives treatment for which the costs are reimbursed under the coverage.
A unique identifier for a dependent under the coverage.
Periodically the member number is constructed from the subscriberId and the dependant number.
For some coverages a single identifier is issued to the Subscriber and then a unique dependent number is issued to each beneficiary.
- No exact HL7 v2 equivalent concept seems to exist;
Beneficiary relationship to the subscriber
The relationship of beneficiary (patient) to the subscriber.
Relationship of the member to the person insured (subscriber)
To determine relationship between the patient and the subscriber to determine coordination of benefits.
Time period during which the coverage is in force. A missing start date indicates the start date isn't known, a missing end date means the coverage is continuing to be in force.
Date that the contract became effective and Date that the contract was terminated or coverage changed.
Some insurers require the submission of the coverage term.
The program or plan underwriter or payor including both insurance and non-insurance agreements, such as patient-pay agreements.
Need to identify the issuer to target for claim processing and for coordination of benefit processing.
A suite of underwriter specific classifiers.
For example may be used to identify a class of coverage or employer group, Policy, Plan.
The codes provided on the health card which identify or confirm the specific policy for the insurer.
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
The type of classification for which an insurer-specific class label or number and optional name is provided, for example may be used to identify a class of coverage or employer group, Policy, Plan.
The insurer issued label for a specific health card value.
The policy classifications, eg. Group, Plan, Class, etc.
The alphanumeric string value associated with the insurer issued label.
The insurer issued label and value are necessary to identify the specific policy.
Human readable description of the type and value
Used to provide a meaningful description in correspondence to the patient.
Business concept used by a health plan to describe its benefit offerings
Name of the health plan benefit offering assigned to the Plan Identifier
The order of applicability of this coverage relative to other coverages which are currently in force. Note, there may be gaps in the numbering and this does not imply primary, secondary etc. as the specific positioning of coverages depends upon the episode of care.
Used in managing the coordination of benefits.
The insurer-specific identifier for the insurer-defined network of providers to which the beneficiary may seek treatment which will be covered at the 'in-network' rate, otherwise 'out of network' terms and conditions apply.
Used in referral for treatment and in claims processing.
A suite of codes indicating the cost category and associated amount which have been detailed in the policy and may have been included on the health card.
For example by knowing the patient visit co-pay, the provider can collect the amount prior to undertaking treatment.
Required by providers to manage financial transaction with the patient.
The category of patient centric costs associated with treatment.
For example visit, specialist visits, emergency, inpatient care, etc.
Needed to identify the category associated with the amount for the patient.
The types of services to which patient copayments are specified.
The amount or percentage due from the beneficiary
The amount due from the patient for the cost category.
Amount may be expressed as a percentage of the service/product cost or a fixed amount of currency.
Needed to identify the amount for the patient associated with the category.
A suite of codes indicating exceptions or reductions to patient costs and their effective periods.
Needed to identify the exception associated with the amount for the patient.
The types of exceptions from the part or full value of financial obligations such as copays.
The timeframe during when the exception is in force.
Needed to identify the applicable timeframe for the exception for the correct calculation of patient costs.
When 'subrogation=true' this insurance instance has been included not for adjudication but to provide insurers with the details to recover costs.
Typically, automotive and worker's compensation policies would be flagged with 'subrogation=true' to enable healthcare payors to collect against accident claims.
The policy(s) which constitute this insurance coverage.
To reference the legally binding contract between the policy holder and the insurer.