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
43
44
45
46

/*
 * Stedi Payers
 *
 * 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::payers::models;
use serde::{Deserialize, Serialize};

/// Matches : Shows which properties in the payer record match the search query. This information helps you understand why Stedi returned this payer and which parts of the payer record matched the search terms. It's also especially useful for debugging search queries and building user interfaces that display matching text. - Matching text is wrapped in `<b>` HTML tags for highlighting. - This object only contains properties with matching text. For example, if none of the payer's aliases matched the search query, this object will not include the `aliases` property.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct Matches {
    /// The parts of the payer's aliases that match the search query. Each alias that contains matching text is included as a separate entry, with matching portions wrapped in `<b>` tags. For example, searching for `XYZ` might return: [`<b>XYZ</b>123`, `ABC<b>XYZ</b>`].
    #[serde(rename = "aliases", skip_serializing_if = "Option::is_none")]
    pub aliases: Option<Vec<String>>,
    /// The part of the payer's display name that matched the search query. For example, searching for `Blue` might return: `Blue Cross <b>Blue</b> Shield`.
    #[serde(rename = "displayName", skip_serializing_if = "Option::is_none")]
    pub display_name: Option<String>,
    /// The parts of the payer's other names that match the search query. Each name that contains matching text is included as a separate entry, with matching portions wrapped in `<b>` tags. For example, searching for `Health` might return: [`Community <b>Health</b> Plan`, `<b>Health</b> Partners`].
    #[serde(rename = "names", skip_serializing_if = "Option::is_none")]
    pub names: Option<Vec<String>>,
    /// The part of the primary payer ID that matched the search query. For example, if you search for '12345', the results for a payer with primary payer ID `12345ABC` would return: `<b>12345</b>ABC`.
    #[serde(rename = "primaryPayerId", skip_serializing_if = "Option::is_none")]
    pub primary_payer_id: Option<String>,
    /// The part of the payer's Stedi payer ID that matched the search query. Stedi payer IDs only support exact substring matching (no prefix or fuzzy matching). For example, if you search for `KRP`, the results for a payer with Stedi payer ID 'KRPCH' would be: `<b>KRP</b>CH`.
    #[serde(rename = "stediId", skip_serializing_if = "Option::is_none")]
    pub stedi_id: Option<String>,
}

impl Matches {
    /// Shows which properties in the payer record match the search query. This information helps you understand why Stedi returned this payer and which parts of the payer record matched the search terms. It's also especially useful for debugging search queries and building user interfaces that display matching text. - Matching text is wrapped in `<b>` HTML tags for highlighting. - This object only contains properties with matching text. For example, if none of the payer's aliases matched the search query, this object will not include the `aliases` property.
    pub fn new() -> Matches {
        Matches {
            aliases: None,
            display_name: None,
            names: None,
            primary_payer_id: None,
            stedi_id: None,
        }
    }
}