autogen-stedi 0.3.2

Auto-generated, strongly-typed Rust client for the Stedi APIs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

/*
 * Stedi Healthcare
 *
 * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 *
 * The version of the OpenAPI document: 2024-04-01
 * Contact: healthcare@stedi.com
 * Generated by: https://openapi-generator.tech
 */

use crate::healthcare::models;
use serde::{Deserialize, Serialize};

/// CobDependent : A dependent for which you want to check coordination of benefits. - An individual qualifies as a dependent when they are listed as a dependent on the subscriber's insurance plan AND the payer cannot uniquely identify them through information outside the subscriber's policy. For example, if the dependent has their own member ID number, you should identify them in the `subscriber` object instead. - The demographic information you provide **must** patch the payer's data exactly. For example, if the payer has the dependent's name as `Jonathan Doe`, a COB request for `Jon Doe` will fail because the name doesn't match the payer's records.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct CobDependent {
    /// The dependent's date of birth.
    #[serde(rename = "dateOfBirth")]
    pub date_of_birth: String,
    /// The dependent's first name.
    #[serde(rename = "firstName")]
    pub first_name: String,
    /// The dependent's last name.
    #[serde(rename = "lastName")]
    pub last_name: String,
    /// The dependent's Social Security Number (SSN).
    #[serde(rename = "ssn", skip_serializing_if = "Option::is_none")]
    pub ssn: Option<String>,
}

impl CobDependent {
    /// A dependent for which you want to check coordination of benefits. - An individual qualifies as a dependent when they are listed as a dependent on the subscriber's insurance plan AND the payer cannot uniquely identify them through information outside the subscriber's policy. For example, if the dependent has their own member ID number, you should identify them in the `subscriber` object instead. - The demographic information you provide **must** patch the payer's data exactly. For example, if the payer has the dependent's name as `Jonathan Doe`, a COB request for `Jon Doe` will fail because the name doesn't match the payer's records.
    pub fn new(date_of_birth: String, first_name: String, last_name: String) -> CobDependent {
        CobDependent {
            date_of_birth,
            first_name,
            last_name,
            ssn: None,
        }
    }
}