/*
* Stedi Enrollment
*
* The Stedi Enrollment Service manages provider enrollments with healthcare payers. It tracks enrollment status, provider details, and supports batch enrollment processing to ensure providers have the necessary credentials before processing healthcare transactions.
*
* The version of the OpenAPI document: 2024-09-01
* Contact: healthcare@stedi.com
* Generated by: https://openapi-generator.tech
*/
use crate::enrollment::models;
use serde::{Deserialize, Serialize};
/// ProviderContact : The contact information for the provider. These contacts appear as prepopulated options for contact information when creating enrollment requests for this provider in the Stedi portal. They aren't automatically added to enrollment requests. These contacts should specify where payers should send communications about the enrollment, if needed. - Either `organizationName` _or_ `firstName` and `lastName` are required. - The name and address should match exactly what the payer has on file for the provider. Some payers reject enrollment requests with addresses that don't match their records. - If you're submitting enrollment requests on a provider's behalf, you may want to set the phone number and email to your own contact details. Do this when you want the payer to contact you about the enrollment status instead of the provider directly. - These contacts are for convenience only. You can specify different contacts on enrollment requests as needed.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct ProviderContact {
/// The contact's city. This should match exactly what the payer has on file for the provider.
#[serde(rename = "city")]
pub city: String,
/// The contact's email address. Set this to where you want the payer to send communications regarding the enrollment. This can be different from the provider's email if needed.
#[serde(rename = "email")]
pub email: String,
/// The contact's first name. This should match exactly what the payer has on file for the provider.
#[serde(rename = "firstName", skip_serializing_if = "Option::is_none")]
pub first_name: Option<String>,
/// The contact's last name. This should match exactly what the payer has on file for the provider.
#[serde(rename = "lastName", skip_serializing_if = "Option::is_none")]
pub last_name: Option<String>,
/// The contact's business name. This should match exactly what the payer has on file for the provider.
#[serde(rename = "organizationName", skip_serializing_if = "Option::is_none")]
pub organization_name: Option<String>,
/// The contact's phone number. Set this to where you want the payer to direct communications regarding the enrollment. This can be different from the provider's phone number if needed.
#[serde(rename = "phone")]
pub phone: String,
/// The contact's two-letter state abbreviation. For example, `PA`, or `MD`. This should match exactly what the payer has on file for the provider.
#[serde(rename = "state")]
pub state: models::UsState,
/// The contact's street address, including the street number, name, and any suite or apartment number. This should match exactly what the payer has on file for the provider.
#[serde(rename = "streetAddress1")]
pub street_address1: String,
/// The contact's street address continued. This should match exactly what the payer has on file for the provider.
#[serde(rename = "streetAddress2", skip_serializing_if = "Option::is_none")]
pub street_address2: Option<String>,
/// The contact's five-digit ZIP code. This should match exactly what the payer has on file for the provider.
#[serde(rename = "zipCode")]
pub zip_code: String,
}
impl ProviderContact {
/// The contact information for the provider. These contacts appear as prepopulated options for contact information when creating enrollment requests for this provider in the Stedi portal. They aren't automatically added to enrollment requests. These contacts should specify where payers should send communications about the enrollment, if needed. - Either `organizationName` _or_ `firstName` and `lastName` are required. - The name and address should match exactly what the payer has on file for the provider. Some payers reject enrollment requests with addresses that don't match their records. - If you're submitting enrollment requests on a provider's behalf, you may want to set the phone number and email to your own contact details. Do this when you want the payer to contact you about the enrollment status instead of the provider directly. - These contacts are for convenience only. You can specify different contacts on enrollment requests as needed.
pub fn new(city: String, email: String, phone: String, state: models::UsState, street_address1: String, zip_code: String) -> ProviderContact {
ProviderContact {
city,
email,
first_name: None,
last_name: None,
organization_name: None,
phone,
state,
street_address1,
street_address2: None,
zip_code,
}
}
}