Struct CoverageBuilder

Source

pub struct CoverageBuilder { /* private fields */ }

Expand description

Builder for CoverageInner.

Implementations§

Source §

impl CoverageBuilder

Source

pub fn id(self, value: String) -> CoverageBuilder

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

Source

pub fn meta(self, value: Meta) -> CoverageBuilder

Metadata about the resource

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.

Source

pub fn implicit_rules(self, value: String) -> CoverageBuilder

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 its narrative along with other profiles, value sets, etc.

Source

pub fn language(self, value: String) -> CoverageBuilder

Language; Language of the resource content

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).

Source

pub fn text(self, value: Narrative) -> CoverageBuilder

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 a 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.

Source

pub fn contained(self, value: Vec<Resource>) -> CoverageBuilder

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

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.

Source

pub fn extension(self, value: Vec<Extension>) -> CoverageBuilder

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 managable, 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.

Source

pub fn modifier_extension(self, value: Vec<Extension>) -> CoverageBuilder

Extensions that cannot be ignored

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 managable, 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.

Source

pub fn identifier(self, value: Vec<Option<Identifier>>) -> CoverageBuilder

Business identifier(s) for this coverage

The identifier of the coverage as issued by the insurer.

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. Note that not all insurers issue unique member IDs therefore searches may result in multiple responses.

Source

pub fn identifier_ext( self, value: Vec<Option<FieldExtension>>, ) -> CoverageBuilder

Extension field.

Source

pub fn status(self, value: String) -> CoverageBuilder

CoverageStatus; active | cancelled | draft | entered-in-error

The status of the resource instance.

This element is labeled as a modifier because the status contains the code entered-in-error that marks the coverage as not currently valid.

Source

pub fn status_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn kind(self, value: Kind) -> CoverageBuilder

CoverageKind; insurance | self-pay | other

The nature of the coverage be it insurance, or cash payment such as self-pay.

Source

pub fn kind_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn payment_by( self, value: Vec<Option<CoveragePaymentBy>>, ) -> CoverageBuilder

Self-pay parties and responsibility

Link to the paying party and optionally what specifically they will be responsible to pay.

Source

pub fn payment_by_ext( self, value: Vec<Option<FieldExtension>>, ) -> CoverageBuilder

Extension field.

Source

pub fn type(self, value: CodeableConcept) -> CoverageBuilder

CoverageType; 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.

Source

pub fn type_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn policy_holder(self, value: Reference) -> CoverageBuilder

Owner of the policy

The party who ‘owns’ the insurance policy.

For example: may be an individual, corporation or the subscriber’s employer.

Source

pub fn policy_holder_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn subscriber(self, value: Reference) -> CoverageBuilder

Subscriber to the policy

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. A subscriber is only required on certain types of policies not all policies and that it is appropriate to have just a policyholder and a beneficiary when not other party can join that policy instance.

Source

pub fn subscriber_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn subscriber_id(self, value: Vec<Option<Identifier>>) -> CoverageBuilder

ID assigned to the subscriber

The insurer assigned ID for the Subscriber.

Source

pub fn subscriber_id_ext( self, value: Vec<Option<FieldExtension>>, ) -> CoverageBuilder

Extension field.

Source

pub fn beneficiary(self, value: Reference) -> CoverageBuilder

Plan beneficiary

The party who benefits from the insurance coverage; the patient when products and/or services are provided.

Source

pub fn beneficiary_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn dependent(self, value: String) -> CoverageBuilder

Dependent number

A designator for a dependent under the coverage.

Sometimes the member number is constructed from the subscriberId and the dependant number.

Source

pub fn dependent_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn relationship(self, value: CodeableConcept) -> CoverageBuilder

Relationship; Beneficiary relationship to the subscriber

The relationship of beneficiary (patient) to the subscriber.

Typically, an individual uses policies which are theirs (relationship=‘self’) before policies owned by others.

Source

pub fn relationship_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn period(self, value: Period) -> CoverageBuilder

Coverage start and end dates

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.

Source

pub fn period_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn insurer(self, value: Reference) -> CoverageBuilder

Issuer of the policy

The program or plan underwriter, payor, insurance company.

May provide multiple identifiers such as insurance company identifier or business identifier (BIN number).

Source

pub fn insurer_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn class(self, value: Vec<Option<CoverageClass>>) -> CoverageBuilder

Additional coverage classifications

A suite of underwriter specific classifiers.

For example, class may be used to identify a class of coverage or employer group, policy, or plan.

Source

pub fn class_ext(self, value: Vec<Option<FieldExtension>>) -> CoverageBuilder

Extension field.

Source

pub fn order(self, value: NonZero<u32>) -> CoverageBuilder

Relative order of the coverage

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. For example; a patient might have (0) auto insurance (1) their own health insurance and (2) spouse’s health insurance. When claiming for treatments which were not the result of an auto accident then only coverages (1) and (2) above would be applicatble and would apply in the order specified in parenthesis.

Source

pub fn order_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn network(self, value: String) -> CoverageBuilder

Insurer network

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.

Source

pub fn network_ext(self, value: FieldExtension) -> CoverageBuilder

Extension field.

Source

pub fn cost_to_beneficiary( self, value: Vec<Option<CoverageCostToBeneficiary>>, ) -> CoverageBuilder

Patient payments for services/products

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.

Source

pub fn cost_to_beneficiary_ext( self, value: Vec<Option<FieldExtension>>, ) -> CoverageBuilder

Extension field.

Source

pub fn subrogation(self, value: bool) -> CoverageBuilder

Reimbursement to insurer

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.

Source