Struct AccountProcedure

pub struct AccountProcedure {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub sequence: Option<NonZero<u32>>,
    pub sequence_ext: Option<FieldExtension>,
    pub code: CodeableReference,
    pub code_ext: Option<FieldExtension>,
    pub date_of_service: Option<DateTime>,
    pub date_of_service_ext: Option<FieldExtension>,
    pub type: Vec<Option<CodeableConcept>>,
    pub type_ext: Vec<Option<FieldExtension>>,
    pub package_code: Vec<Option<CodeableConcept>>,
    pub package_code_ext: Vec<Option<FieldExtension>>,
    pub device: Vec<Option<Reference>>,
    pub device_ext: Vec<Option<FieldExtension>>,
}

Sub-fields of the procedure field in Account

Fields

id: Option<String>

Unique id for inter-element referencing

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

extension: Vec<Extension>

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

modifier_extension: Vec<Extension>

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

sequence: Option<NonZero<u32>>

Ranking of the procedure (for each type)

Ranking of the procedure (for each type).

sequence_ext: Option<FieldExtension>

Extension field.

code: CodeableReference

; The procedure relevant to the account

The procedure relevant to the account.

code_ext: Option<FieldExtension>

Extension field.

date_of_service: Option<DateTime>

Date of the procedure (when coded procedure)

Date of the procedure when using a coded procedure. If using a reference to a procedure, then the date on the procedure should be used.

date_of_service_ext: Option<FieldExtension>

Extension field.

type: Vec<Option<CodeableConcept>>

procedure-type; How this procedure value should be used in charging the account

How this procedure value should be used in charging the account.

type_ext: Vec<Option<FieldExtension>>

Extension field.

package_code: Vec<Option<CodeableConcept>>

procedure-package-code; Package Code specific for billing

The package code can be used to group procedures that may be priced or delivered as a single product. Such as DRGs.

package_code_ext: Vec<Option<FieldExtension>>

Extension field.

device: Vec<Option<Reference>>

Any devices that were associated with the procedure

Any devices that were associated with the procedure relevant to the account.

device_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl AccountProcedure

pub fn builder() -> AccountProcedureBuilder

Start building a new instance

Trait Implementations

impl Clone for AccountProcedure

fn clone(&self) -> AccountProcedure

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AccountProcedure

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for AccountProcedure

fn deserialize<__D>( __deserializer: __D, ) -> Result<AccountProcedure, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for AccountProcedure

fn eq(&self, other: &AccountProcedure) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for AccountProcedure

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for AccountProcedure