haste_fhir_generated_ops/

generated.rs

#![allow(non_snake_case)]
#![doc = " @generated by `bash scripts/operation_build.sh` - do not edit."]
#[doc = "This operation is used to search for and return notifications that have been previously triggered by"]
#[doc = "a topic-based Subscription in R4."]
pub mod BackportSubscriptionEvents {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "events";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"backport-subscription-events","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>URL: [base]/Subscription/[id]/$events</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>eventsSinceNumber</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>The starting event number, inclusive of this event (lower bound).</p>\n</div></td></tr><tr><td>IN</td><td>eventsUntilNumber</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>The ending event number, inclusive of this event (upper bound).</p>\n</div></td></tr><tr><td>IN</td><td>content</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#code\">code</a></td><td/><td><div><p>Requested content style of returned data. Codes from backport-content-value-set (e.g., empty, id-only, full-resource). This is a hint to the server what a client would prefer, and MAY be ignored.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/bundle.html\">Bundle</a></td><td/><td><div><p>The operation returns a valid notification bundle, with the first entry being the subscription status information resource. The bundle type is &quot;history&quot;.</p>\n</div></td></tr></table></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-wg","valueCode":"fhir"}],"url":"http://hl7.org/fhir/uv/subscriptions-backport/OperationDefinition/backport-subscription-events","version":"1.2.0-ballot","name":"R5SubscriptionEvents","title":"Subscription Events Operation","status":"active","kind":"operation","date":"2020-11-30","publisher":"HL7 International / FHIR Infrastructure","contact":[{"name":"HL7 International / FHIR Infrastructure","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/fiwg"}]},{"name":"Gino Canessa","telecom":[{"system":"email","value":"mailto:gino.canessa@microsoft.com"}]}],"description":"This operation is used to search for and return notifications that have been previously triggered by a topic-based Subscription in R4.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"affectsState":false,"code":"events","resource":["Subscription"],"system":false,"type":false,"instance":true,"parameter":[{"name":"eventsSinceNumber","use":"in","min":0,"max":"1","documentation":"The starting event number, inclusive of this event (lower bound).","type":"string"},{"name":"eventsUntilNumber","use":"in","min":0,"max":"1","documentation":"The ending event number, inclusive of this event (upper bound).","type":"string"},{"name":"content","use":"in","min":0,"max":"1","documentation":"Requested content style of returned data. Codes from backport-content-value-set (e.g., empty, id-only, full-resource). This is a hint to the server what a client would prefer, and MAY be ignored.","type":"code"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The operation returns a valid notification bundle, with the first entry being the subscription status information resource. The bundle type is \"history\".","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The starting event number, inclusive of this event (lower bound)."]
        pub eventsSinceNumber: Option<FHIRString>,
        #[doc = "The ending event number, inclusive of this event (upper bound)."]
        pub eventsUntilNumber: Option<FHIRString>,
        #[doc = "Requested content style of returned data. Codes from backport-content-value-set (e.g., empty,"]
        #[doc = "id-only, full-resource). This is a hint to the server what a client would prefer, and MAY be"]
        #[doc = "ignored."]
        pub content: Option<FHIRCode>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The operation returns a valid notification bundle, with the first entry being the subscription"]
        #[doc = "status information resource. The bundle type is \"history\"."]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "This operation is used to get a token for a websocket client to use in order to bind to one or more"]
#[doc = "subscriptions."]
pub mod BackportSubscriptionGetWsBindingToken {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRDateTime, FHIRId, FHIRString, FHIRUrl};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "get-ws-binding-token";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"backport-subscription-get-ws-binding-token","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>URL: [base]/Subscription/$get-ws-binding-token</p><p>URL: [base]/Subscription/[id]/$get-ws-binding-token</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>id</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#id\">id</a></td><td/><td><div><p>At the Instance level, this parameter is ignored. At the Resource level, one or more parameters containing a FHIR id for a Subscription to get a token for. In the absense of any specified ids, the server may either return a token for all Subscriptions available to the caller with a channel-type of websocket or fail the request.</p>\n</div></td></tr><tr><td>OUT</td><td>token</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>An access token that a client may use to show authorization during a websocket connection.</p>\n</div></td></tr><tr><td>OUT</td><td>expiration</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date and time this token is valid until.</p>\n</div></td></tr><tr><td>OUT</td><td>subscription</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>The subscriptions this token is valid for.</p>\n</div></td></tr><tr><td>OUT</td><td>websocket-url</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#url\">url</a></td><td/><td><div><p>The URL the client should use to connect to Websockets.</p>\n</div></td></tr></table></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-wg","valueCode":"fhir"}],"url":"http://hl7.org/fhir/uv/subscriptions-backport/OperationDefinition/backport-subscription-get-ws-binding-token","version":"1.2.0-ballot","name":"R5SubscriptionGetWsBindingToken","title":"Get WS Binding Token for Subscription Operation","status":"active","kind":"operation","date":"2020-11-30","publisher":"HL7 International / FHIR Infrastructure","contact":[{"name":"HL7 International / FHIR Infrastructure","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/fiwg"}]},{"name":"Gino Canessa","telecom":[{"system":"email","value":"mailto:gino.canessa@microsoft.com"}]}],"description":"This operation is used to get a token for a websocket client to use in order to bind to one or more subscriptions.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"affectsState":false,"code":"get-ws-binding-token","resource":["Subscription"],"system":false,"type":true,"instance":true,"parameter":[{"name":"id","use":"in","min":0,"max":"*","documentation":"At the Instance level, this parameter is ignored. At the Resource level, one or more parameters containing a FHIR id for a Subscription to get a token for. In the absense of any specified ids, the server may either return a token for all Subscriptions available to the caller with a channel-type of websocket or fail the request.","type":"id"},{"name":"token","use":"out","min":1,"max":"1","documentation":"An access token that a client may use to show authorization during a websocket connection.","type":"string"},{"name":"expiration","use":"out","min":1,"max":"1","documentation":"The date and time this token is valid until.","type":"dateTime"},{"name":"subscription","use":"out","min":0,"max":"*","documentation":"The subscriptions this token is valid for.","type":"string"},{"name":"websocket-url","use":"out","min":1,"max":"1","documentation":"The URL the client should use to connect to Websockets.","type":"url"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "At the Instance level, this parameter is ignored. At the Resource level, one or more parameters"]
        #[doc = "containing a FHIR id for a Subscription to get a token for. In the absense of any specified ids, the"]
        #[doc = "server may either return a token for all Subscriptions available to the caller with a channel-type"]
        #[doc = "of websocket or fail the request."]
        pub id: Option<Vec<FHIRId>>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "An access token that a client may use to show authorization during a websocket connection."]
        pub token: FHIRString,
        #[doc = "The date and time this token is valid until."]
        pub expiration: FHIRDateTime,
        #[doc = "The subscriptions this token is valid for."]
        pub subscription: Option<Vec<FHIRString>>,
        #[doc = "The URL the client should use to connect to Websockets."]
        #[parameter_rename = "websocket-url"]
        pub websocket_url: FHIRUrl,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation is used to resend notifications that have been previously triggered by a topic-based"]
#[doc = "Subscription in R4."]
pub mod BackportSubscriptionResend {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRInstant, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "resend";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"backport-subscription-resend","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>URL: [base]/Subscription/[id]/$resend</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>eventsSinceNumber</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>The starting event number, inclusive of this event (lower bound).</p>\n</div></td></tr><tr><td>IN</td><td>eventsUntilNumber</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#string\">string</a></td><td/><td><div><p>The ending event number, inclusive of this event (upper bound).</p>\n</div></td></tr><tr><td>IN</td><td>eventsSinceInstant</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#instant\">instant</a></td><td/><td><div><p>The starting event date/time, inclusive of this instant (lower bound).</p>\n</div></td></tr><tr><td>IN</td><td>eventsUntilInstant</td><td/><td>0..1</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#instant\">instant</a></td><td/><td><div><p>The ending event date/time, inclusive of this instant (upper bound).</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/operationoutcome.html\">OperationOutcome</a></td><td/><td><div><p>Outcome of this request.</p>\n</div></td></tr></table></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-wg","valueCode":"fhir"}],"url":"http://hl7.org/fhir/uv/subscriptions-backport/OperationDefinition/backport-subscription-resend","version":"1.2.0-ballot","name":"SubscriptionResend","title":"Subscription Resend Operation","status":"active","kind":"operation","date":"2020-11-30","publisher":"HL7 International / FHIR Infrastructure","contact":[{"name":"HL7 International / FHIR Infrastructure","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/fiwg"}]},{"name":"Gino Canessa","telecom":[{"system":"email","value":"mailto:gino.canessa@microsoft.com"}]}],"description":"This operation is used to resend notifications that have been previously triggered by a topic-based Subscription in R4.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"affectsState":false,"code":"resend","resource":["Subscription"],"system":false,"type":false,"instance":true,"parameter":[{"name":"eventsSinceNumber","use":"in","min":0,"max":"1","documentation":"The starting event number, inclusive of this event (lower bound).","type":"string"},{"name":"eventsUntilNumber","use":"in","min":0,"max":"1","documentation":"The ending event number, inclusive of this event (upper bound).","type":"string"},{"name":"eventsSinceInstant","use":"in","min":0,"max":"1","documentation":"The starting event date/time, inclusive of this instant (lower bound).","type":"instant"},{"name":"eventsUntilInstant","use":"in","min":0,"max":"1","documentation":"The ending event date/time, inclusive of this instant (upper bound).","type":"instant"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Outcome of this request.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The starting event number, inclusive of this event (lower bound)."]
        pub eventsSinceNumber: Option<FHIRString>,
        #[doc = "The ending event number, inclusive of this event (upper bound)."]
        pub eventsUntilNumber: Option<FHIRString>,
        #[doc = "The starting event date/time, inclusive of this instant (lower bound)."]
        pub eventsSinceInstant: Option<FHIRInstant>,
        #[doc = "The ending event date/time, inclusive of this instant (upper bound)."]
        pub eventsUntilInstant: Option<FHIRInstant>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "Outcome of this request."]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "This operation is used to return the current status information about one or more topic-based"]
#[doc = "Subscriptions in R4."]
pub mod BackportSubscriptionStatus {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRId};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "status";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"backport-subscription-status","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>URL: [base]/Subscription/$status</p><p>URL: [base]/Subscription/[id]/$status</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>id</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#id\">id</a></td><td/><td><div><p>At the Instance level, this parameter is ignored.  At the Resource level, one or more parameters containing a FHIR id for a Subscription to get status information for. In the absence of any specified ids, the server returns the status for all Subscriptions available to the caller. Multiple values are joined via OR (e.g., &quot;id1&quot; OR &quot;id2&quot;).</p>\n</div></td></tr><tr><td>IN</td><td>status</td><td/><td>0..*</td><td><a href=\"http://hl7.org/fhir/R4B/datatypes.html#code\">code</a></td><td/><td><div><p>At the Instance level, this parameter is ignored. At the Resource level, a Subscription status to filter by (e.g., &quot;active&quot;). In the absence of any specified status values, the server does not filter contents based on the status. Multiple values are joined via OR (e.g., &quot;error&quot; OR &quot;off&quot;).</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4B/bundle.html\">Bundle</a></td><td/><td><div><p>The operation returns a bundle containing one or more subscription status resources, one per Subscription being queried. The Bundle type is &quot;searchset&quot;.</p>\n</div></td></tr></table></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-wg","valueCode":"fhir"}],"url":"http://hl7.org/fhir/uv/subscriptions-backport/OperationDefinition/backport-subscription-status","version":"1.2.0-ballot","name":"R5SubscriptionStatus","title":"Subscription Status Operation","status":"active","kind":"operation","date":"2020-11-30","publisher":"HL7 International / FHIR Infrastructure","contact":[{"name":"HL7 International / FHIR Infrastructure","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/fiwg"}]},{"name":"Gino Canessa","telecom":[{"system":"email","value":"mailto:gino.canessa@microsoft.com"}]}],"description":"This operation is used to return the current status information about one or more topic-based Subscriptions in R4.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"affectsState":false,"code":"status","resource":["Subscription"],"system":false,"type":true,"instance":true,"parameter":[{"name":"id","use":"in","min":0,"max":"*","documentation":"At the Instance level, this parameter is ignored.  At the Resource level, one or more parameters containing a FHIR id for a Subscription to get status information for. In the absence of any specified ids, the server returns the status for all Subscriptions available to the caller. Multiple values are joined via OR (e.g., \"id1\" OR \"id2\").","type":"id"},{"name":"status","use":"in","min":0,"max":"*","documentation":"At the Instance level, this parameter is ignored. At the Resource level, a Subscription status to filter by (e.g., \"active\"). In the absence of any specified status values, the server does not filter contents based on the status. Multiple values are joined via OR (e.g., \"error\" OR \"off\").","type":"code"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The operation returns a bundle containing one or more subscription status resources, one per Subscription being queried. The Bundle type is \"searchset\".","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "At the Instance level, this parameter is ignored. At the Resource level, one or more parameters"]
        #[doc = "containing a FHIR id for a Subscription to get status information for. In the absence of any"]
        #[doc = "specified ids, the server returns the status for all Subscriptions available to the caller. Multiple"]
        #[doc = "values are joined via OR (e.g., \"id1\" OR \"id2\")."]
        pub id: Option<Vec<FHIRId>>,
        #[doc = "At the Instance level, this parameter is ignored. At the Resource level, a Subscription status to"]
        #[doc = "filter by (e.g., \"active\"). In the absence of any specified status values, the server does not"]
        #[doc = "filter contents based on the status. Multiple values are joined via OR (e.g., \"error\" OR \"off\")."]
        pub status: Option<Vec<FHIRCode>>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The operation returns a bundle containing one or more subscription status resources, one per"]
        #[doc = "Subscription being queried. The Bundle type is \"searchset\"."]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "Get Project resource for the current project."]
pub mod ProjectInformation {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Project, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "current-project";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"project-information","url":"https://haste.health/OperationDefinition/project-information","version":"4.0.1","name":"Current Project Information","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Get Project resource for the current project.","code":"current-project","system":true,"type":false,"instance":false,"parameter":[{"name":"project","use":"out","min":1,"max":"1","documentation":"Users current project.","type":"Project"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Users current project."]
        pub project: Project,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Get tenant information for the current tenant."]
pub mod TenantInformation {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "current-tenant";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"tenant-information","url":"https://haste.health/OperationDefinition/tenant-information","version":"4.0.1","name":"Current Tenant Information","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Get tenant information for the current tenant.","code":"current-tenant","system":true,"type":false,"instance":false,"parameter":[{"name":"id","use":"out","min":1,"max":"1","documentation":"tenant id","type":"string"},{"name":"subscription","use":"out","min":1,"max":"1","documentation":"tenant subscription level","type":"code"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "tenant id"]
        pub id: FHIRString,
        #[doc = "tenant subscription level"]
        pub subscription: FHIRCode,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Get tenant endpoint information for the current tenant."]
pub mod TenantEndpointInformation {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRUri;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "endpoints";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"tenant-endpoint-information","url":"https://haste.health/OperationDefinition/tenant-endpoint-information","version":"4.0.1","name":"Current Tenant Endpoint Information","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Get tenant endpoint information for the current tenant.","code":"endpoints","system":true,"type":false,"instance":false,"parameter":[{"name":"fhir-r4-base-url","use":"out","min":1,"max":"1","documentation":"FHIR R4 Endpoint URL.","type":"uri"},{"name":"fhir-r4-capabilities-url","use":"out","min":1,"max":"1","documentation":"FHIR R4 Capabilities URL.","type":"uri"},{"name":"oidc-discovery-url","use":"out","min":1,"max":"1","documentation":"OIDC Discovery URL.","type":"uri"},{"name":"oidc-token-endpoint","use":"out","min":1,"max":"1","documentation":"OIDC Token Endpoint.","type":"uri"},{"name":"oidc-authorize-endpoint","use":"out","min":1,"max":"1","documentation":"OIDC Authorize Endpoint.","type":"uri"},{"name":"oidc-jwks-endpoint","use":"out","min":1,"max":"1","documentation":"OIDC JWKS Endpoint.","type":"uri"},{"name":"mcp-endpoint","use":"out","min":1,"max":"1","documentation":"Model context protocol endpoint.","type":"uri"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "FHIR R4 Endpoint URL."]
        #[parameter_rename = "fhir-r4-base-url"]
        pub fhir_r4_base_url: FHIRUri,
        #[doc = "FHIR R4 Capabilities URL."]
        #[parameter_rename = "fhir-r4-capabilities-url"]
        pub fhir_r4_capabilities_url: FHIRUri,
        #[doc = "OIDC Discovery URL."]
        #[parameter_rename = "oidc-discovery-url"]
        pub oidc_discovery_url: FHIRUri,
        #[doc = "OIDC Token Endpoint."]
        #[parameter_rename = "oidc-token-endpoint"]
        pub oidc_token_endpoint: FHIRUri,
        #[doc = "OIDC Authorize Endpoint."]
        #[parameter_rename = "oidc-authorize-endpoint"]
        pub oidc_authorize_endpoint: FHIRUri,
        #[doc = "OIDC JWKS Endpoint."]
        #[parameter_rename = "oidc-jwks-endpoint"]
        pub oidc_jwks_endpoint: FHIRUri,
        #[doc = "Model context protocol endpoint."]
        #[parameter_rename = "mcp-endpoint"]
        pub mcp_endpoint: FHIRUri,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Evaluate an Access Policy."]
pub mod HasteHealthEvaluatePolicy {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::Reference;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "evaluate-policy";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-evaluate-policy","url":"https://haste.health/OperationDefinition/evaluate-policy","version":"4.0.1","name":"EvaluateAccessPolicy","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Evaluate an Access Policy.","code":"evaluate-policy","resource":["AccessPolicyV2"],"system":false,"type":false,"instance":true,"parameter":[{"name":"user","use":"in","min":0,"max":"1","documentation":"The user to evaluate the policy against. Defaults to logged in user if not present.","type":"Reference"},{"name":"request","use":"in","min":1,"max":"1","documentation":"The requests to evaluate against the policy.","type":"Bundle"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the policy evaluation.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The user to evaluate the policy against. Defaults to logged in user if not present."]
        pub user: Option<Reference>,
        #[doc = "The requests to evaluate against the policy."]
        pub request: Bundle,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the policy evaluation."]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "Parse `HL7v2` messages."]
pub mod Hl7v2Parse {
    use haste_fhir_model::r4::generated::resources::{
        HL7V2, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "hl7v2-parse";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"hl7v2-parse","url":"https://haste.health/OperationDefinition/hl7v2-parse","version":"4.0.1","name":"HL7v2 Parse","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Parse HL7v2 messages.","code":"hl7v2-parse","system":true,"type":false,"instance":false,"parameter":[{"name":"hl7v2","use":"in","min":1,"max":"1","documentation":"HL7v2 message to be parsed.","type":"string"},{"name":"hl7v2","use":"out","min":1,"max":"1","documentation":"Parsed HL7v2 message.","type":"HL7V2"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "`HL7v2` message to be parsed."]
        pub hl7v2: FHIRString,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Parsed `HL7v2` message."]
        pub hl7v2: HL7V2,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Get the registration information for an identity provider."]
pub mod HasteHealthIdpRegistrationInfo {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "registration-info";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-idp-registration-info","url":"https://haste.health/OperationDefinition/identity-provider-registration-info","version":"4.0.1","name":"IdentityProviderRegistrationInformation","status":"draft","kind":"operation","publisher":"HasteHealth","description":"Get the registration information for an identity provider.","code":"registration-info","resource":["IdentityProvider"],"system":false,"type":false,"instance":true,"parameter":[{"name":"information","use":"out","min":0,"max":"*","documentation":"IdentityProviders registration information.","part":[{"name":"name","use":"out","min":1,"max":"1","documentation":"The name of the property.","type":"string"},{"name":"value","use":"out","min":1,"max":"1","documentation":"the value of the property.","type":"string"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputInformation {
        #[doc = "The name of the property."]
        pub name: FHIRString,
        #[doc = "the value of the property."]
        pub value: FHIRString,
    }
    impl From<OutputInformation> for Resource {
        fn from(value: OutputInformation) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "`IdentityProviders` registration information."]
        #[parameter_nested]
        pub information: Option<Vec<OutputInformation>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Install FHIR packages (implementation guides) into the current project: their profiles, extensions,"]
#[doc = "`ValueSets`, `CodeSystems`, `ConceptMaps`, `NamingSystems` and `SearchParameters`. Name a package to"]
#[doc = "fetch it from the package registry, or upload its .tgz. Each installed package is recorded as an"]
#[doc = "`ImplementationGuide` whose id is the package name. Installing a package that is already installed"]
#[doc = "replaces it with the version given. Everything is written in one transaction."]
pub mod HasteHealthImplementationguideInstall {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        FHIRBase64Binary, FHIRBoolean, FHIRCode, FHIRInteger, FHIRString,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "install";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-implementationguide-install","url":"https://haste.health/OperationDefinition/implementationguide-install","version":"4.0.1","name":"Install Implementation Guide","status":"draft","kind":"operation","date":"2026-10-30T22:00:00+00:00","publisher":"HasteHealth","description":"Install FHIR packages (implementation guides) into the current project: their profiles, extensions, ValueSets, CodeSystems, ConceptMaps, NamingSystems and SearchParameters. Name a package to fetch it from the package registry, or upload its .tgz. Each installed package is recorded as an ImplementationGuide whose id is the package name. Installing a package that is already installed replaces it with the version given. Everything is written in one transaction.","affectsState":true,"code":"install","resource":["ImplementationGuide"],"system":false,"type":true,"instance":false,"parameter":[{"name":"package","use":"in","min":0,"max":"*","documentation":"A package to fetch from the package registry: 'name@version' (or 'name#version'), 'name@6.1.x' for the newest patch, or 'name' alone for the latest version. Example: 'hl7.fhir.us.core@6.1.0'.","type":"string"},{"name":"npmContent","use":"in","min":0,"max":"*","documentation":"A package tarball (.tgz), base64 encoded. Its dependencies are taken from the other uploaded tarballs first, then from the package registry.","type":"base64Binary"},{"name":"dependencies","use":"in","min":0,"max":"1","documentation":"Also install the packages these depend on (default true). A dependency that is already installed, in any version, is left as it is. The FHIR core packages are built in, and the server skips the large terminology packages (hl7.terminology, VSAC, PHIN VADS) unless they are named directly.","type":"boolean"},{"name":"examples","use":"in","min":0,"max":"1","documentation":"Also install the example resources of the packages named or uploaded (default false). Dependencies' examples are never installed.","type":"boolean"},{"name":"package","use":"out","min":0,"max":"*","documentation":"One for each package considered: the ones asked for and their dependencies.","part":[{"name":"name","use":"out","min":1,"max":"1","documentation":"The package name.","type":"string"},{"name":"version","use":"out","min":1,"max":"1","documentation":"The version installed, or for a skipped package the version asked for.","type":"string"},{"name":"status","use":"out","min":1,"max":"1","documentation":"installed (it was not installed before), updated (it replaced an installed version) or skipped (see reason).","type":"code"},{"name":"previousVersion","use":"out","min":0,"max":"1","documentation":"For updated, the version it replaced.","type":"string"},{"name":"resources","use":"out","min":0,"max":"1","documentation":"How many of its resources were written.","type":"integer"},{"name":"reason","use":"out","min":0,"max":"1","documentation":"Why a package was skipped.","type":"string"}]},{"name":"outcome","use":"out","min":0,"max":"1","documentation":"Warnings about resources that were not installed, for example a resource that could not be read or whose id is taken by a resource the package did not install.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A package to fetch from the package registry: 'name@version' (or 'name#version'), 'name@6.1.x' for"]
        #[doc = "the newest patch, or `name` alone for the latest version. Example: 'hl7.fhir.us.core@6.1.0'."]
        pub package: Option<Vec<FHIRString>>,
        #[doc = "A package tarball (.tgz), base64 encoded. Its dependencies are taken from the other uploaded"]
        #[doc = "tarballs first, then from the package registry."]
        pub npmContent: Option<Vec<FHIRBase64Binary>>,
        #[doc = "Also install the packages these depend on (default true). A dependency that is already installed, in"]
        #[doc = "any version, is left as it is. The FHIR core packages are built in, and the server skips the large"]
        #[doc = "terminology packages (hl7.terminology, VSAC, PHIN VADS) unless they are named directly."]
        pub dependencies: Option<FHIRBoolean>,
        #[doc = "Also install the example resources of the packages named or uploaded (default false). Dependencies'"]
        #[doc = "examples are never installed."]
        pub examples: Option<FHIRBoolean>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputPackage {
        #[doc = "The package name."]
        pub name: FHIRString,
        #[doc = "The version installed, or for a skipped package the version asked for."]
        pub version: FHIRString,
        #[doc = "installed (it was not installed before), updated (it replaced an installed version) or skipped (see"]
        #[doc = "reason)."]
        pub status: FHIRCode,
        #[doc = "For updated, the version it replaced."]
        pub previousVersion: Option<FHIRString>,
        #[doc = "How many of its resources were written."]
        pub resources: Option<FHIRInteger>,
        #[doc = "Why a package was skipped."]
        pub reason: Option<FHIRString>,
    }
    impl From<OutputPackage> for Resource {
        fn from(value: OutputPackage) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "One for each package considered: the ones asked for and their dependencies."]
        #[parameter_nested]
        pub package: Option<Vec<OutputPackage>>,
        #[doc = "Warnings about resources that were not installed, for example a resource that could not be read or"]
        #[doc = "whose id is taken by a resource the package did not install."]
        pub outcome: Option<OperationOutcome>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Uninstall a package that $install installed in the current project: delete the resources it"]
#[doc = "installed and its `ImplementationGuide` record. Packages it depends on stay installed."]
pub mod HasteHealthImplementationguideUninstall {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "uninstall";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-implementationguide-uninstall","url":"https://haste.health/OperationDefinition/implementationguide-uninstall","version":"4.0.1","name":"Uninstall Implementation Guide","status":"draft","kind":"operation","date":"2026-10-30T22:00:00+00:00","publisher":"HasteHealth","description":"Uninstall a package that $install installed in the current project: delete the resources it installed and its ImplementationGuide record. Packages it depends on stay installed.","affectsState":true,"code":"uninstall","resource":["ImplementationGuide"],"system":false,"type":true,"instance":false,"parameter":[{"name":"name","use":"in","min":1,"max":"1","documentation":"The package name, for example 'hl7.fhir.us.core'.","type":"string"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The installed version. When given and another version is installed, nothing is uninstalled.","type":"string"},{"name":"return","use":"out","min":1,"max":"1","documentation":"What was uninstalled.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The package name, for example 'hl7.fhir.us.core'."]
        pub name: FHIRString,
        #[doc = "The installed version. When given and another version is installed, nothing is uninstalled."]
        pub version: Option<FHIRString>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "What was uninstalled."]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "Show resources that failed search indexing for the current tenant and project."]
pub mod HasteHealthIndexingErrors {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        FHIRBoolean, FHIRCode, FHIRDateTime, FHIRId, FHIRInteger, FHIRString,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "indexing-errors";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-indexing-errors","url":"https://haste.health/OperationDefinition/indexing-errors","version":"4.0.1","name":"Show Indexing Errors","status":"draft","kind":"operation","date":"2026-08-14T22:29:23+00:00","publisher":"HasteHealth","description":"Show resources that failed search indexing for the current tenant and project.","code":"indexing-errors","system":true,"type":false,"instance":false,"parameter":[{"name":"resolve","use":"in","min":0,"max":"1","documentation":"If true, mark the indexing errors as resolved.","type":"boolean"},{"name":"errors","use":"out","min":0,"max":"*","documentation":"The resources that failed search indexing.","part":[{"name":"id","use":"out","min":1,"max":"1","documentation":"Version id of the resource that failed to index.","type":"id"},{"name":"version_id","use":"out","min":1,"max":"1","documentation":"Version id of the resource that failed to index.","type":"id"},{"name":"resource_type","use":"out","min":1,"max":"1","documentation":"FHIR resource type of the resource that failed to index.","type":"code"},{"name":"fhir_method","use":"out","min":1,"max":"1","documentation":"The operation (create, update or delete) that failed to index.","type":"code"},{"name":"sequence","use":"out","min":1,"max":"1","documentation":"Sequence position of the resource in the indexing stream.","type":"integer"},{"name":"attempt_count","use":"out","min":1,"max":"1","documentation":"Number of times indexing has been attempted for this resource.","type":"integer"},{"name":"error_message","use":"out","min":1,"max":"1","documentation":"The error that occurred while indexing.","type":"string"},{"name":"first_failed_at","use":"out","min":1,"max":"1","documentation":"When this resource first failed indexing.","type":"dateTime"},{"name":"last_failed_at","use":"out","min":1,"max":"1","documentation":"When this resource most recently failed indexing.","type":"dateTime"},{"name":"resolved_at","use":"out","min":0,"max":"1","documentation":"When this failure was marked resolved, if it has been.","type":"dateTime"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "If true, mark the indexing errors as resolved."]
        pub resolve: Option<FHIRBoolean>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputErrors {
        #[doc = "Version id of the resource that failed to index."]
        pub id: FHIRId,
        #[doc = "Version id of the resource that failed to index."]
        pub version_id: FHIRId,
        #[doc = "FHIR resource type of the resource that failed to index."]
        pub resource_type: FHIRCode,
        #[doc = "The operation (create, update or delete) that failed to index."]
        pub fhir_method: FHIRCode,
        #[doc = "Sequence position of the resource in the indexing stream."]
        pub sequence: FHIRInteger,
        #[doc = "Number of times indexing has been attempted for this resource."]
        pub attempt_count: FHIRInteger,
        #[doc = "The error that occurred while indexing."]
        pub error_message: FHIRString,
        #[doc = "When this resource first failed indexing."]
        pub first_failed_at: FHIRDateTime,
        #[doc = "When this resource most recently failed indexing."]
        pub last_failed_at: FHIRDateTime,
        #[doc = "When this failure was marked resolved, if it has been."]
        pub resolved_at: Option<FHIRDateTime>,
    }
    impl From<OutputErrors> for Resource {
        fn from(value: OutputErrors) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The resources that failed search indexing."]
        #[parameter_nested]
        pub errors: Option<Vec<OutputErrors>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Delete refresh token from the user for the client."]
pub mod HasteHealthDeleteRefreshToken {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRId, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "delete-refresh-token";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-delete-refresh-token","url":"https://haste.health/OperationDefinition/delete-refresh-tokens","version":"4.0.1","name":"Delete refresh token","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Delete refresh token from the user for the client.","affectsState":true,"code":"delete-refresh-token","system":true,"type":false,"instance":false,"parameter":[{"name":"client_id","use":"in","min":1,"max":"1","documentation":"Client id for refresh token to delete.","type":"id"},{"name":"user_agent","use":"in","min":0,"max":"1","documentation":"User agent of the refresh token to delete.","type":"string"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Result of the delete operation.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Client id for refresh token to delete."]
        pub client_id: FHIRId,
        #[doc = "User agent of the refresh token to delete."]
        pub user_agent: Option<FHIRString>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "Result of the delete operation."]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "Show list of users refresh tokens."]
pub mod HasteHealthListRefreshTokens {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRDateTime, FHIRId, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "refresh-tokens";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-list-refresh-tokens","url":"https://haste-health.app/OperationDefinition/list-refresh-tokens","version":"4.0.1","name":"Show Refresh Tokens","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Show list of users refresh tokens.","code":"refresh-tokens","system":true,"type":false,"instance":false,"parameter":[{"name":"refresh-tokens","use":"out","min":0,"max":"*","documentation":"The result of the operation.","part":[{"name":"client_id","use":"out","min":1,"max":"1","documentation":"Client for refresh token.","type":"id"},{"name":"user_agent","use":"out","min":1,"max":"1","documentation":"User agent of the refresh token.","type":"string"},{"name":"created_at","use":"out","min":1,"max":"1","documentation":"When the refresh token was created.","type":"dateTime"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputRefreshTokens {
        #[doc = "Client for refresh token."]
        pub client_id: FHIRId,
        #[doc = "User agent of the refresh token."]
        pub user_agent: FHIRString,
        #[doc = "When the refresh token was created."]
        pub created_at: FHIRDateTime,
    }
    impl From<OutputRefreshTokens> for Resource {
        fn from(value: OutputRefreshTokens) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The result of the operation."]
        #[parameter_rename = "refresh-tokens"]
        #[parameter_nested]
        pub refresh_tokens: Option<Vec<OutputRefreshTokens>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Delete scope from user accepted scopes for the client."]
pub mod HasteHealthDeleteScope {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRId;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "delete-scope";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-delete-scope","url":"https://haste.health/OperationDefinition/delete-scopes","version":"4.0.1","name":"Delete Scope","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Delete scope from user accepted scopes for the client.","affectsState":true,"code":"delete-scope","system":true,"type":false,"instance":false,"parameter":[{"name":"client_id","use":"in","min":1,"max":"1","documentation":"Client for which scopes are being shown.","type":"id"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Result of the delete operation.","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Client for which scopes are being shown."]
        pub client_id: FHIRId,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "Result of the delete operation."]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "Show list of user accepted scopes for apps."]
pub mod HasteHealthListScopes {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRDateTime, FHIRId, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "scopes";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-list-scopes","url":"https://haste.health/OperationDefinition/list-scopes","version":"4.0.1","name":"Show Scopes","status":"draft","kind":"operation","date":"2023-11-15T22:29:23+00:00","publisher":"HasteHealth","description":"Show list of user accepted scopes for apps.","code":"scopes","system":true,"type":false,"instance":false,"parameter":[{"name":"scopes","use":"out","min":0,"max":"*","documentation":"The result of the operation.","part":[{"name":"client_id","use":"out","min":1,"max":"1","documentation":"Client for which scopes are being shown.","type":"id"},{"name":"scopes","use":"out","min":1,"max":"1","documentation":"Scopes user accepted.","type":"string"},{"name":"created_at","use":"out","min":1,"max":"1","documentation":"When the scopes were accepted.","type":"dateTime"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputScopes {
        #[doc = "Client for which scopes are being shown."]
        pub client_id: FHIRId,
        #[doc = "Scopes user accepted."]
        pub scopes: FHIRString,
        #[doc = "When the scopes were accepted."]
        pub created_at: FHIRDateTime,
    }
    impl From<OutputScopes> for Resource {
        fn from(value: OutputScopes) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The result of the operation."]
        #[parameter_nested]
        pub scopes: Option<Vec<OutputScopes>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Starts a SMART App Launch EHR launch of this client application for a patient, and optionally one of"]
#[doc = "the patient's encounters. Only a signed-in user can start a launch, and the same user must then"]
#[doc = "authorize the app. Open the returned url to start the app."]
pub mod HasteHealthSmartLaunch {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRString, FHIRUri, Reference};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "launch";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-smart-launch","url":"https://haste.health/OperationDefinition/smart-launch","version":"4.0.1","name":"SMART EHR launch","status":"draft","kind":"operation","date":"2026-10-07T00:00:00+00:00","publisher":"HasteHealth","description":"Starts a SMART App Launch EHR launch of this client application for a patient, and optionally one of the patient's encounters. Only a signed-in user can start a launch, and the same user must then authorize the app. Open the returned url to start the app.","affectsState":true,"code":"launch","resource":["ClientApplication"],"system":false,"type":false,"instance":true,"parameter":[{"name":"patient","use":"in","min":1,"max":"1","documentation":"The patient the app is launched for. The caller must be able to read it.","type":"Reference","targetProfile":["http://hl7.org/fhir/StructureDefinition/Patient"]},{"name":"encounter","use":"in","min":0,"max":"1","documentation":"The encounter the app is launched in. It must be the patient's, and the caller must be able to read it.","type":"Reference","targetProfile":["http://hl7.org/fhir/StructureDefinition/Encounter"]},{"name":"launch","use":"out","min":1,"max":"1","documentation":"The opaque launch value the app passes back at authorization. It expires five minutes after it is created.","type":"string"},{"name":"iss","use":"out","min":1,"max":"1","documentation":"The FHIR base URL the app is launched against.","type":"uri"},{"name":"url","use":"out","min":1,"max":"1","documentation":"The client's launchUri with iss and launch added to its query. Open it to start the app.","type":"uri"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The patient the app is launched for. The caller must be able to read it."]
        pub patient: Reference,
        #[doc = "The encounter the app is launched in. It must be the patient's, and the caller must be able to read"]
        #[doc = "it."]
        pub encounter: Option<Reference>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The opaque launch value the app passes back at authorization. It expires five minutes after it is"]
        #[doc = "created."]
        pub launch: FHIRString,
        #[doc = "The FHIR base URL the app is launched against."]
        pub iss: FHIRUri,
        #[doc = "The client's launchUri with iss and launch added to its query. Open it to start the app."]
        pub url: FHIRUri,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Set display customization for the current tenant, such as its display name and logo."]
pub mod HasteHealthTenantCustomization {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{Attachment, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "tenant-customization";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-tenant-customization","url":"https://haste.health/OperationDefinition/tenant-customization","version":"4.0.1","name":"Tenant Customization","status":"draft","kind":"operation","date":"2026-08-20T22:29:23+00:00","publisher":"HasteHealth","description":"Set display customization for the current tenant, such as its display name and logo.","affectsState":true,"code":"tenant-customization","system":true,"type":false,"instance":false,"parameter":[{"name":"name","use":"in","min":0,"max":"1","documentation":"Display name for the tenant. Omit to clear the tenant's display name.","type":"string"},{"name":"logo","use":"in","min":0,"max":"1","documentation":"Logo for the tenant. Omit to clear the tenant's logo.","type":"Attachment"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Display name for the tenant. Omit to clear the tenant's display name."]
        pub name: Option<FHIRString>,
        #[doc = "Logo for the tenant. Omit to clear the tenant's logo."]
        pub logo: Option<Attachment>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {}
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Get the current tenant's display name and logo, if set."]
pub mod HasteHealthTenantBranding {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{Attachment, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "tenant-branding";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"haste-health-tenant-branding","url":"https://haste.health/OperationDefinition/tenant-branding","version":"4.0.1","name":"Tenant Branding","status":"draft","kind":"operation","date":"2026-08-22T00:00:00+00:00","publisher":"HasteHealth","description":"Get the current tenant's display name and logo, if set.","code":"tenant-branding","system":true,"type":false,"instance":false,"parameter":[{"name":"name","use":"out","min":0,"max":"1","documentation":"Display name for the tenant, if one has been set.","type":"string"},{"name":"logo","use":"out","min":0,"max":"1","documentation":"Logo for the tenant, if one has been set.","type":"Attachment"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Display name for the tenant, if one has been set."]
        pub name: Option<FHIRString>,
        #[doc = "Logo for the tenant, if one has been set."]
        pub logo: Option<Attachment>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The apply operation applies a definition in a specific context"]
pub mod ActivityDefinitionApply {
    use haste_fhir_model::r4::generated::resources::{
        ActivityDefinition, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{CodeableConcept, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "apply";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ActivityDefinition-apply","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Apply</h2><p>OPERATION: Apply</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ActivityDefinition-apply</pre><div><p>The apply operation applies a definition in a specific context</p>\n</div><p>URL: [base]/ActivityDefinition/$apply</p><p>URL: [base]/ActivityDefinition/[id]/$apply</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>activityDefinition</td><td>0..1</td><td><a href=\"activitydefinition.html\">ActivityDefinition</a></td><td/><td><div><p>The activity definition to apply. If the operation is invoked on an instance, this parameter is not allowed. If the operation is invoked at the type level, this parameter is required</p>\n</div></td></tr><tr><td>IN</td><td>subject</td><td>1..*</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The subject(s) that is/are the target of the activity definition to be applied. The subject may be a Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be resolved as the subject of the PlanDefinition based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined</p>\n</div></td></tr><tr><td>IN</td><td>encounter</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The encounter in context, if any</p>\n</div></td></tr><tr><td>IN</td><td>practitioner</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The practitioner in context</p>\n</div></td></tr><tr><td>IN</td><td>organization</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The organization in context</p>\n</div></td></tr><tr><td>IN</td><td>userType</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)</p>\n</div></td></tr><tr><td>IN</td><td>userLanguage</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>Preferred language of the person using the system</p>\n</div></td></tr><tr><td>IN</td><td>userTaskContext</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources</p>\n</div></td></tr><tr><td>IN</td><td>setting</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The current setting of the request (inpatient, outpatient, etc.)</p>\n</div></td></tr><tr><td>IN</td><td>settingContext</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>Additional detail about the setting of the request, if any</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td>Any</td><td/><td><div><p>The resource that is the result of applying the definition</p>\n</div></td></tr></table><div><p>The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource.  If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. In addition, parameters to the $apply operation are available within dynamicValue expressions as context variables, accessible by the name of the parameter, prefixed with a percent (%) symbol. For a more detailed description, refer to the ActivityDefinition resource</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/ActivityDefinition-apply","version":"4.0.1","name":"Apply","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The apply operation applies a definition in a specific context","code":"apply","comment":"The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource.  If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. In addition, parameters to the $apply operation are available within dynamicValue expressions as context variables, accessible by the name of the parameter, prefixed with a percent (%) symbol. For a more detailed description, refer to the ActivityDefinition resource","resource":["ActivityDefinition"],"system":false,"type":true,"instance":true,"parameter":[{"name":"activityDefinition","use":"in","min":0,"max":"1","documentation":"The activity definition to apply. If the operation is invoked on an instance, this parameter is not allowed. If the operation is invoked at the type level, this parameter is required","type":"ActivityDefinition"},{"name":"subject","use":"in","min":1,"max":"*","documentation":"The subject(s) that is/are the target of the activity definition to be applied. The subject may be a Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be resolved as the subject of the `PlanDefinition` based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined","type":"string","searchType":"reference"},{"name":"encounter","use":"in","min":0,"max":"1","documentation":"The encounter in context, if any","type":"string","searchType":"reference"},{"name":"practitioner","use":"in","min":0,"max":"1","documentation":"The practitioner in context","type":"string","searchType":"reference"},{"name":"organization","use":"in","min":0,"max":"1","documentation":"The organization in context","type":"string","searchType":"reference"},{"name":"userType","use":"in","min":0,"max":"1","documentation":"The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)","type":"CodeableConcept"},{"name":"userLanguage","use":"in","min":0,"max":"1","documentation":"Preferred language of the person using the system","type":"CodeableConcept"},{"name":"userTaskContext","use":"in","min":0,"max":"1","documentation":"The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources","type":"CodeableConcept"},{"name":"setting","use":"in","min":0,"max":"1","documentation":"The current setting of the request (inpatient, outpatient, etc.)","type":"CodeableConcept"},{"name":"settingContext","use":"in","min":0,"max":"1","documentation":"Additional detail about the setting of the request, if any","type":"CodeableConcept"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The resource that is the result of applying the definition","type":"Any"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The activity definition to apply. If the operation is invoked on an instance, this parameter is not"]
        #[doc = "allowed. If the operation is invoked at the type level, this parameter is required"]
        pub activityDefinition: Option<ActivityDefinition>,
        #[doc = "The subject(s) that is/are the target of the activity definition to be applied. The subject may be a"]
        #[doc = "Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter"]
        #[doc = "will be resolved as the subject of the `PlanDefinition` based on the type of the subject. If"]
        #[doc = "multiple subjects of the same type are provided, the behavior is implementation-defined"]
        pub subject: Vec<FHIRString>,
        #[doc = "The encounter in context, if any"]
        pub encounter: Option<FHIRString>,
        #[doc = "The practitioner in context"]
        pub practitioner: Option<FHIRString>,
        #[doc = "The organization in context"]
        pub organization: Option<FHIRString>,
        #[doc = "The type of user initiating the request, e.g. patient, healthcare provider, or specific type of"]
        #[doc = "healthcare provider (physician, nurse, etc.)"]
        pub userType: Option<CodeableConcept>,
        #[doc = "Preferred language of the person using the system"]
        pub userLanguage: Option<CodeableConcept>,
        #[doc = "The task the system user is performing, e.g. laboratory results review, medication list review, etc."]
        #[doc = "This information can be used to tailor decision support outputs, such as recommended information"]
        #[doc = "resources"]
        pub userTaskContext: Option<CodeableConcept>,
        #[doc = "The current setting of the request (inpatient, outpatient, etc.)"]
        pub setting: Option<CodeableConcept>,
        #[doc = "Additional detail about the setting of the request, if any"]
        pub settingContext: Option<CodeableConcept>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The resource that is the result of applying the definition"]
        #[parameter_rename = "return"]
        pub return_: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            value.return_
        }
    }
}
#[doc = "The data-requirements operation aggregates and returns the parameters and data requirements for the"]
#[doc = "activity definition and all its dependencies as a single module definition library"]
pub mod ActivityDefinitionDataRequirements {
    use haste_fhir_model::r4::generated::resources::{
        Library, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "data-requirements";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ActivityDefinition-data-requirements","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Data Requirements</h2><p>OPERATION: Data Requirements</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ActivityDefinition-data-requirements</pre><div><p>The data-requirements operation aggregates and returns the parameters and data requirements for the activity definition and all its dependencies as a single module definition library</p>\n</div><p>URL: [base]/ActivityDefinition/[id]/$data-requirements</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"library.html\">Library</a></td><td/><td><div><p>The result of the requirements gathering represented as a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the activity definition</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the activity definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the activity definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/ActivityDefinition-data-requirements","version":"4.0.1","name":"Data Requirements","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The data-requirements operation aggregates and returns the parameters and data requirements for the activity definition and all its dependencies as a single module definition library","code":"data-requirements","comment":"The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the activity definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the activity definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)","resource":["ActivityDefinition"],"system":false,"type":false,"instance":true,"parameter":[{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the requirements gathering represented as a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the activity definition","type":"Library"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the requirements gathering represented as a module-definition Library that describes"]
        #[doc = "the aggregate parameters, data requirements, and dependencies of the activity definition"]
        #[parameter_rename = "return"]
        pub return_: Library,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Library(value.return_)
        }
    }
}
#[doc = "This operation asks the server to check that it implements all the resources, interactions, search"]
#[doc = "parameters, and operations that the client provides in its capability statement. The client provides"]
#[doc = "both capability statements by reference, and must ensure that all the referenced resources are"]
#[doc = "available to the conformance server"]
pub mod CapabilityStatementConforms {
    use haste_fhir_model::r4::generated::resources::{
        CapabilityStatement, OperationDefinition, OperationOutcome, Parameters,
        ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCanonical, FHIRCode};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "conforms";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CapabilityStatement-conforms","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Test if a server implements a client's required operations</h2><p>OPERATION: Test if a server implements a client's required operations</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CapabilityStatement-conforms</pre><div><p>This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations that the client provides in its capability statement. The client provides both capability statements by reference, and must ensure that all the referenced resources are available to the conformance server</p>\n</div><p>URL: [base]/CapabilityStatement/$conforms</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>left</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>A canonical reference to the left-hand system's capability statement</p>\n</div></td></tr><tr><td>IN</td><td>right</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>A canonical reference to the right-hand system's capability statement</p>\n</div></td></tr><tr><td>IN</td><td>mode</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>What kind of comparison to perform - server to server, or client to server (use the codes 'server/server' or 'client/server')</p>\n</div></td></tr><tr><td>OUT</td><td>issues</td><td>1..1</td><td><a href=\"operationoutcome.html\">OperationOutcome</a></td><td/><td><div><p>Outcome of the CapabilityStatement test</p>\n</div></td></tr><tr><td>OUT</td><td>union</td><td>0..1</td><td><a href=\"capabilitystatement.html\">CapabilityStatement</a></td><td/><td><div><p>The intersection of the functionality described by the CapabilityStatement resources</p>\n</div></td></tr><tr><td>OUT</td><td>intersection</td><td>0..1</td><td><a href=\"capabilitystatement.html\">CapabilityStatement</a></td><td/><td><div><p>The union of the functionality described by the CapabilityStatement resources</p>\n</div></td></tr></table><div><p>The operation performs a full comparison of the functionality described by the two capability statements, including the profiles and value sets they reference, and also including concept maps and structure maps.</p>\n<p>The full execution of this operation is still a matter of research, but it is intended to support comparison of systems to see if they will interoperate</p>\n<p>If the capability statements can be successfully compared, then the return value is a 200 OK with an OperationOutcome along with intersection and union capability statements. The operation outcome can contain errors relating to differences between the capability statements. If the capability statements cannot be compared, because dependencies cannot be located, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity &gt;= error</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CapabilityStatement-conforms","version":"4.0.1","name":"Test if a server implements a client's required operations","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations that the client provides in its capability statement. The client provides both capability statements by reference, and must ensure that all the referenced resources are available to the conformance server","code":"conforms","comment":"The operation performs a full comparison of the functionality described by the two capability statements, including the profiles and value sets they reference, and also including concept maps and structure maps.     \n\nThe full execution of this operation is still a matter of research, but it is intended to support comparison of systems to see if they will interoperate    \n\nIf the capability statements can be successfully compared, then the return value is a 200 OK with an OperationOutcome along with intersection and union capability statements. The operation outcome can contain errors relating to differences between the capability statements. If the capability statements cannot be compared, because dependencies cannot be located, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error","resource":["CapabilityStatement"],"system":false,"type":true,"instance":false,"parameter":[{"name":"left","use":"in","min":0,"max":"1","documentation":"A canonical reference to the left-hand system's capability statement","type":"canonical"},{"name":"right","use":"in","min":0,"max":"1","documentation":"A canonical reference to the right-hand system's capability statement","type":"canonical"},{"name":"mode","use":"in","min":0,"max":"1","documentation":"What kind of comparison to perform - server to server, or client to server (use the codes 'server/server' or 'client/server')","type":"code"},{"name":"issues","use":"out","min":1,"max":"1","documentation":"Outcome of the `CapabilityStatement` test","type":"OperationOutcome"},{"name":"union","use":"out","min":0,"max":"1","documentation":"The intersection of the functionality described by the `CapabilityStatement` resources","type":"CapabilityStatement"},{"name":"intersection","use":"out","min":0,"max":"1","documentation":"The union of the functionality described by the `CapabilityStatement` resources","type":"CapabilityStatement"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A canonical reference to the left-hand system's capability statement"]
        pub left: Option<FHIRCanonical>,
        #[doc = "A canonical reference to the right-hand system's capability statement"]
        pub right: Option<FHIRCanonical>,
        #[doc = "What kind of comparison to perform - server to server, or client to server (use the codes"]
        #[doc = "'server/server' or 'client/server')"]
        pub mode: Option<FHIRCode>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Outcome of the `CapabilityStatement` test"]
        pub issues: OperationOutcome,
        #[doc = "The intersection of the functionality described by the `CapabilityStatement` resources"]
        #[parameter_rename = "union"]
        pub union_: Option<CapabilityStatement>,
        #[doc = "The union of the functionality described by the `CapabilityStatement` resources"]
        pub intersection: Option<CapabilityStatement>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation asks the server to check that it implements all the resources, interactions, search"]
#[doc = "parameters, and operations that the client provides in its capability statement. The client provides"]
#[doc = "its capability statement inline, or by referring the server to the canonical URL of its capability"]
#[doc = "statement"]
pub mod CapabilityStatementImplements {
    use haste_fhir_model::r4::generated::resources::{
        CapabilityStatement, OperationDefinition, OperationOutcome, Parameters,
        ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRCanonical;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "implements";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CapabilityStatement-implements","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Test if a server implements a client's required operations</h2><p>OPERATION: Test if a server implements a client's required operations</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CapabilityStatement-implements</pre><div><p>This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations that the client provides in its capability statement. The client provides its capability statement inline, or by referring the server to the canonical URL of its capability statement</p>\n</div><p>URL: [base]/CapabilityStatement/$implements</p><p>URL: [base]/CapabilityStatement/[id]/$implements</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>server</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>A canonical reference to the server capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)</p>\n</div></td></tr><tr><td>IN</td><td>client</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>A canonical reference to the client capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)</p>\n</div></td></tr><tr><td>IN</td><td>resource</td><td>0..1</td><td><a href=\"capabilitystatement.html\">CapabilityStatement</a></td><td/><td><div><p>The client capability statement, provided inline</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"operationoutcome.html\">OperationOutcome</a></td><td/><td><div><p>Outcome of the CapabilityStatement test</p>\n</div></td></tr></table><div><p>The operation does not perform a full conformance check; in particular it does not check that the profiles align. It merely checks that the behaviors the client wishes to use are provided    Technically, this operation is implemented as follows:</p>\n<ul>\n<li>The server's capability statement must have an entry for each resource in the client's capability statement</li>\n<li>The server's resource support must have matching flags for updateCreate, conditionalCreate, conditionalRead, conditionalUpdate, conditionalDelete, searchInclude, searchRevInclude</li>\n<li>The server's capability statement must have a matching interaction for each interaction in the client capability statement (whether or not it is on a resource)</li>\n<li>The server's capability statement must have a search parameter with matching name and definition for any search parameters in the client capability statement</li>\n<li>The server must have an operation definition with a matching reference for any operations in the client capability statement</li>\n</ul>\n<p>If the capability statements match by these rules, then the return value is a 200 OK with an operation outcome that contains no issues with severity &gt;= error. If the capability statement doesn't match, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity &gt;= error</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CapabilityStatement-implements","version":"4.0.1","name":"Test if a server implements a client's required operations","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation asks the server to check that it implements all the resources, interactions, search parameters, and operations that the client provides in its capability statement. The client provides its capability statement inline, or by referring the server to the canonical URL of its capability statement","code":"implements","comment":"The operation does not perform a full conformance check; in particular it does not check that the profiles align. It merely checks that the behaviors the client wishes to use are provided    Technically, this operation is implemented as follows:   \n\n* The server's capability statement must have an entry for each resource in the client's capability statement    \n* The server's resource support must have matching flags for updateCreate, conditionalCreate, conditionalRead, conditionalUpdate, conditionalDelete, searchInclude, searchRevInclude   \n* The server's capability statement must have a matching interaction for each interaction in the client capability statement (whether or not it is on a resource)   \n* The server's capability statement must have a search parameter with matching name and definition for any search parameters in the client capability statement   \n* The server must have an operation definition with a matching reference for any operations in the client capability statement   \n\nIf the capability statements match by these rules, then the return value is a 200 OK with an operation outcome that contains no issues with severity >= error. If the capability statement doesn't match, the return value is a 4xx error, with an OperationOutcome with at least one issue with severity >= error","resource":["CapabilityStatement"],"system":false,"type":true,"instance":true,"parameter":[{"name":"server","use":"in","min":0,"max":"1","documentation":"A canonical reference to the server capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)","type":"canonical"},{"name":"client","use":"in","min":0,"max":"1","documentation":"A canonical reference to the client capability statement - use this if the implements is not invoked on an instance (or on the /metadata end-point)","type":"canonical"},{"name":"resource","use":"in","min":0,"max":"1","documentation":"The client capability statement, provided inline","type":"CapabilityStatement"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Outcome of the `CapabilityStatement` test","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A canonical reference to the server capability statement - use this if the implements is not invoked"]
        #[doc = "on an instance (or on the /metadata end-point)"]
        pub server: Option<FHIRCanonical>,
        #[doc = "A canonical reference to the client capability statement - use this if the implements is not invoked"]
        #[doc = "on an instance (or on the /metadata end-point)"]
        pub client: Option<FHIRCanonical>,
        #[doc = "The client capability statement, provided inline"]
        pub resource: Option<CapabilityStatement>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "Outcome of the `CapabilityStatement` test"]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "This operation asks the server to return a subset of the `CapabilityStatement` resource - just the"]
#[doc = "REST parts that relate to a set of nominated resources - the resources that the client is interested"]
#[doc = "in"]
pub mod CapabilityStatementSubset {
    use haste_fhir_model::r4::generated::resources::{
        CapabilityStatement, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRUri};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "subset";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CapabilityStatement-subset","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch a subset of the CapabilityStatement resource</h2><p>OPERATION: Fetch a subset of the CapabilityStatement resource</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CapabilityStatement-subset</pre><div><p>This operation asks the server to return a subset of the CapabilityStatement resource - just the REST parts that relate to a set of nominated resources - the resources that the client is interested in</p>\n</div><p>URL: [base]/CapabilityStatement/$subset</p><p>URL: [base]/CapabilityStatement/[id]/$subset</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>server</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The canonical URL - use this if the subset is not invoked on an instance (or on the /metadata end-point)</p>\n</div></td></tr><tr><td>IN</td><td>resource</td><td>1..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>A resource that the client would like to include in the return</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"capabilitystatement.html\">CapabilityStatement</a></td><td/><td><div><p>The subsetted CapabilityStatement resource that is returned. This should be tagged with the SUBSETTED code</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CapabilityStatement-subset","version":"4.0.1","name":"Fetch a subset of the CapabilityStatement resource","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation asks the server to return a subset of the `CapabilityStatement` resource - just the REST parts that relate to a set of nominated resources - the resources that the client is interested in","code":"subset","resource":["CapabilityStatement"],"system":false,"type":true,"instance":true,"parameter":[{"name":"server","use":"in","min":0,"max":"1","documentation":"The canonical URL - use this if the subset is not invoked on an instance (or on the /metadata end-point)","type":"uri"},{"name":"resource","use":"in","min":1,"max":"*","documentation":"A resource that the client would like to include in the return","type":"code"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The subsetted `CapabilityStatement` resource that is returned. This should be tagged with the SUBSETTED code","type":"CapabilityStatement"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The canonical URL - use this if the subset is not invoked on an instance (or on the /metadata"]
        #[doc = "end-point)"]
        pub server: Option<FHIRUri>,
        #[doc = "A resource that the client would like to include in the return"]
        pub resource: Vec<FHIRCode>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The subsetted `CapabilityStatement` resource that is returned. This should be tagged with the"]
        #[doc = "SUBSETTED code"]
        #[parameter_rename = "return"]
        pub return_: CapabilityStatement,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::CapabilityStatement(value.return_)
        }
    }
}
#[doc = "Using the [`FHIR Version Mime Type Parameter`](http.html#version-parameter), a server can support"]
#[doc = "[`multiple versions on the same end-point`](versioning.html#mt-version). The only way for client to"]
#[doc = "find out what versions a server supports in this fashion is the $versions operation. The client"]
#[doc = "invokes the operation with no parameters. and the server returns the list of supported versions,"]
#[doc = "along with the default version it will use if no fhirVersion parameter is present"]
pub mod CapabilityStatementVersions {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRCode;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "versions";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CapabilityStatement-versions","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Discover what versions a server supports</h2><p>OPERATION: Discover what versions a server supports</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CapabilityStatement-versions</pre><div><p>Using the <a href=\"http.html#version-parameter\">FHIR Version Mime Type Parameter</a>, a server can support <a href=\"versioning.html#mt-version\">multiple versions on the same end-point</a>. The only way for client to find out what versions a server supports in this fashion is the $versions operation. The client invokes the operation with no parameters. and the server returns the list of supported versions, along with the default version it will use if no fhirVersion parameter is present</p>\n</div><p>URL: [base]/$versions</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>OUT</td><td>version</td><td>1..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>A version supported by the server. Use the major.minor version like 3.0</p>\n</div></td></tr><tr><td>OUT</td><td>default</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The default version for the server. Use the major.minor version like 3.0</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CapabilityStatement-versions","version":"4.0.1","name":"Discover what versions a server supports","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Using the [FHIR Version Mime Type Parameter](http.html#version-parameter), a server can support [multiple versions on the same end-point](versioning.html#mt-version). The only way for client to find out what versions a server supports in this fashion is the $versions operation. The client invokes the operation with no parameters. and the server returns the list of supported versions, along with the default version it will use if no fhirVersion parameter is present","code":"versions","resource":["CapabilityStatement"],"system":true,"type":false,"instance":false,"parameter":[{"name":"version","use":"out","min":1,"max":"*","documentation":"A version supported by the server. Use the major.minor version like 3.0","type":"code"},{"name":"default","use":"out","min":1,"max":"1","documentation":"The default version for the server. Use the major.minor version like 3.0","type":"code"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "A version supported by the server. Use the major.minor version like 3.0"]
        pub version: Vec<FHIRCode>,
        #[doc = "The default version for the server. Use the major.minor version like 3.0"]
        pub default: FHIRCode,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The apply operation applies a definition in a specific context"]
pub mod ChargeItemDefinitionApply {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::Reference;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "apply";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ChargeItemDefinition-apply","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Apply</h2><p>OPERATION: Apply</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ChargeItemDefinition-apply</pre><div><p>The apply operation applies a definition in a specific context</p>\n</div><p>URL: [base]/ChargeItemDefinition/[id]/$apply</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>chargeItem</td><td>1..1</td><td><a href=\"references.html#Reference\">Reference</a></td><td/><td><div><p>The ChargeItem on which the definition is to ba applies</p>\n</div></td></tr><tr><td>IN</td><td>account</td><td>0..1</td><td><a href=\"references.html#Reference\">Reference</a></td><td/><td><div><p>The account in context, if any</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td>Any</td><td/><td><div><p>The resource that is the result of applying the definition</p>\n</div></td></tr></table><div><p>The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource.  If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. For a more detailed description, refer to the ActivityDefinition resource</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/ChargeItemDefinition-apply","version":"4.0.1","name":"Apply","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The apply operation applies a definition in a specific context","code":"apply","comment":"The result of invoking this operation is a resource of the type specified by the activity definition, with all the definitions resolved as appropriate for the type of resource. Any dynamicValue elements will be evaluated (in the order in which they appear in the resource) and the results applied to the returned resource.  If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. For a more detailed description, refer to the ActivityDefinition resource","resource":["ChargeItemDefinition"],"system":false,"type":false,"instance":true,"parameter":[{"name":"chargeItem","use":"in","min":1,"max":"1","documentation":"The `ChargeItem` on which the definition is to ba applies","type":"Reference","targetProfile":["http://hl7.org/fhir/StructureDefinition/ChargeItem"]},{"name":"account","use":"in","min":0,"max":"1","documentation":"The account in context, if any","type":"Reference","targetProfile":["http://hl7.org/fhir/StructureDefinition/Account"]},{"name":"return","use":"out","min":1,"max":"1","documentation":"The resource that is the result of applying the definition","type":"Any"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The `ChargeItem` on which the definition is to ba applies"]
        pub chargeItem: Reference,
        #[doc = "The account in context, if any"]
        pub account: Option<Reference>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The resource that is the result of applying the definition"]
        #[parameter_rename = "return"]
        pub return_: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            value.return_
        }
    }
}
#[doc = "This operation is used to submit a Claim, `Pre-Authorization` or `Pre-Determination` (all instances"]
#[doc = "of Claim resources) for adjudication either as a single Claim resource instance or as a Bundle"]
#[doc = "containing the Claim and other referenced resources, or Bundle containing a batch of Claim"]
#[doc = "resources, either as single Claims resources or Bundle resources, for processing. The only input"]
#[doc = "parameter is the single Claim or Bundle resource and the only output is a single `ClaimResponse`,"]
#[doc = "Bundle of `ClaimResponses` or an `OperationOutcome` resource."]
pub mod ClaimSubmit {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "submit";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Claim-submit","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Submit a Claim resource for adjudication</h2><p>OPERATION: Submit a Claim resource for adjudication</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Claim-submit</pre><div><p>This operation is used to submit a Claim, Pre-Authorization or Pre-Determination (all instances of Claim resources) for adjudication either as a single Claim resource instance or as a Bundle containing the Claim and other referenced resources, or Bundle containing a batch of Claim resources, either as single Claims resources or Bundle resources, for processing. The only input parameter is the single Claim or Bundle resource and the only output is a single ClaimResponse, Bundle of ClaimResponses or an OperationOutcome resource.</p>\n</div><p>URL: [base]/Claim/$submit</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>resource</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>A Claim resource or Bundle of claims, either as individual Claim resources or as Bundles each containing a single Claim plus referenced resources.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>A ClaimResponse resource or Bundle of claim responses, either as individual ClaimResponse resources or as Bundles each containing a single ClaimResponse plus referenced resources.</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Claim-submit","version":"4.0.1","name":"Submit a Claim resource for adjudication","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to submit a Claim, Pre-Authorization or Pre-Determination (all instances of Claim resources) for adjudication either as a single Claim resource instance or as a Bundle containing the Claim and other referenced resources, or Bundle containing a batch of Claim resources, either as single Claims resources or Bundle resources, for processing. The only input parameter is the single Claim or Bundle resource and the only output is a single `ClaimResponse`, Bundle of `ClaimResponses` or an `OperationOutcome` resource.","code":"submit","resource":["Claim"],"system":false,"type":true,"instance":false,"parameter":[{"name":"resource","use":"in","min":1,"max":"1","documentation":"A Claim resource or Bundle of claims, either as individual Claim resources or as Bundles each containing a single Claim plus referenced resources.","type":"Resource"},{"name":"return","use":"out","min":1,"max":"1","documentation":"A `ClaimResponse` resource or Bundle of claim responses, either as individual `ClaimResponse` resources or as Bundles each containing a single `ClaimResponse` plus referenced resources.","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A Claim resource or Bundle of claims, either as individual Claim resources or as Bundles each"]
        #[doc = "containing a single Claim plus referenced resources."]
        pub resource: Resource,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "A `ClaimResponse` resource or Bundle of claim responses, either as individual `ClaimResponse`"]
        #[doc = "resources or as Bundles each containing a single `ClaimResponse` plus referenced resources."]
        #[parameter_rename = "return"]
        pub return_: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Given a set of properties (and text), return one or more possible matching codes"]
#[doc = ""]
#[doc = "This operation takes a set of properties, and examines the code system looking for codes in the code"]
#[doc = "system that match a set of known properties."]
#[doc = ""]
#[doc = "When looking for matches, there are 3 possible types of match:"]
#[doc = "* a complete match - a code that represents all the provided properties correctly"]
#[doc = "* a partial match - a code that represents some of the provided properties correctly, and not others"]
#[doc = "* a possible match - a code that may represent the provided properties closely, but may capture less"]
#[doc = "or more precise information for some of the properties"]
#[doc = ""]
#[doc = "The $find-matches operation can be called in one of 2 modes:"]
#[doc = "* By a human, looking for the best match for a set of properties. In this mode, the server returns a"]
#[doc = "list of complete, possible or partial matches (possibly with comments), so that the user can choose"]
#[doc = "(or not) the most appropriate code"]
#[doc = "* By a machine (typically in a system interface performing a transformation). In this mode, the"]
#[doc = "server returns only a list of complete and partial matches, but no possible matches. The machine can"]
#[doc = "choose a code from the list (or not) based on what properties are not coded"]
#[doc = ""]
#[doc = "These modes are differentiated by the `exact` parameter, so the client can indicate whether it only"]
#[doc = "wants exact matches (including partial matches) or whether potential matches based on text matching"]
#[doc = "are desired"]
#[doc = "The find-matches operation is still preliminary. The interface can be expected to change as more"]
#[doc = "experience is gained from implementations."]
pub mod CodeSystemFindMatches {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, ParametersParameterValueTypeChoice,
        Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        Coding, FHIRBoolean, FHIRCode, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "find-matches";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CodeSystem-find-matches","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Finding codes based on supplied properties</h2><p>OPERATION: Finding codes based on supplied properties</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CodeSystem-find-matches</pre><div><p>Given a set of properties (and text), return one or more possible matching codes</p>\n<p>This operation takes a set of properties, and examines the code system looking for codes in the code system that match a set of known properties.</p>\n<p>When looking for matches, there are 3 possible types of match:</p>\n<ul>\n<li>a complete match - a code that represents all the provided properties correctly</li>\n<li>a partial match - a code that represents some of the provided properties correctly, and not others</li>\n<li>a possible match - a code that may represent the provided properties closely, but may capture less or more precise information for some of the properties</li>\n</ul>\n<p>The $find-matches operation can be called in one of 2 modes:</p>\n<ul>\n<li>By a human, looking for the best match for a set of properties. In this mode, the server returns a list of complete, possible or partial matches (possibly with comments), so that the user can choose (or not) the most appropriate code</li>\n<li>By a machine (typically in a system interface performing a transformation). In this mode, the server returns only a list of complete and partial matches, but no possible matches. The machine can choose a code from the list (or not) based on what properties are not coded</li>\n</ul>\n<p>These modes are differentiated by the 'exact' parameter, so the client can indicate whether it only wants exact matches (including partial matches) or whether potential matches based on text matching are desired</p>\n<p>The find-matches operation is still preliminary. The interface can be expected to change as more experience is gained from implementations.</p>\n</div><p>URL: [base]/CodeSystem/$find-matches</p><p>URL: [base]/CodeSystem/[id]/$find-matches</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The system in which composition is to be performed. This must be provided unless the operation is invoked on a code system instance</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the system for the inferencing to be performed</p>\n</div></td></tr><tr><td>IN</td><td>property</td><td>0..*</td><td></td><td/><td><div><p>One or more properties that contain information to be composed into the code</p>\n</div></td></tr><tr><td>IN</td><td>property.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the property provided</p>\n</div></td></tr><tr><td>IN</td><td>property.value</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The value of the property provided</p>\n</div></td></tr><tr><td>IN</td><td>property.subproperty</td><td>0..*</td><td></td><td/><td><div><p>Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)</p>\n</div></td></tr><tr><td>IN</td><td>property.subproperty.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the sub-property provided</p>\n</div></td></tr><tr><td>IN</td><td>property.subproperty.value</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The value of the sub-property provided</p>\n</div></td></tr><tr><td>IN</td><td>exact</td><td>1..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Whether the operation is being used by a human ('false'), or a machine ('true'). If the operation is being used by a human, the terminology server can return a list of possible matches, with commentary. For a machine, the server returns complete or partial matches, not possible matches. The default value is 'false'</p>\n</div></td></tr><tr><td>IN</td><td>compositional</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Post-coordinated expressions are allowed to be returned in the matching codes (mainly for SNOMED CT). Default = false</p>\n</div></td></tr><tr><td>OUT</td><td>match</td><td>0..*</td><td></td><td/><td><div><p>Concepts returned by the server as a result of the inferencing operation</p>\n</div></td></tr><tr><td>OUT</td><td>match.code</td><td>1..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A code that matches the properties provided</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched</td><td>0..*</td><td></td><td/><td><div><p>One or more properties that contain properties that could not be matched into the code</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the property provided</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched.value</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The value of the property provided</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched.property</td><td>0..*</td><td></td><td/><td><div><p>Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched.property.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the sub-property provided</p>\n</div></td></tr><tr><td>OUT</td><td>match.unmatched.property.value</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The value of the sub-property provided</p>\n</div></td></tr><tr><td>OUT</td><td>match.comment</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Information about the quality of the match, if operation is for a human</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CodeSystem-find-matches","version":"4.0.1","name":"Finding codes based on supplied properties","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Given a set of properties (and text), return one or more possible matching codes\n\nThis operation takes a set of properties, and examines the code system looking for codes in the code system that match a set of known properties. \n\nWhen looking for matches, there are 3 possible types of match:\n* a complete match - a code that represents all the provided properties correctly\n* a partial match - a code that represents some of the provided properties correctly, and not others \n* a possible match - a code that may represent the provided properties closely, but may capture less or more precise information for some of the properties\n\nThe $find-matches operation can be called in one of 2 modes:\n* By a human, looking for the best match for a set of properties. In this mode, the server returns a list of complete, possible or partial matches (possibly with comments), so that the user can choose (or not) the most appropriate code\n* By a machine (typically in a system interface performing a transformation). In this mode, the server returns only a list of complete and partial matches, but no possible matches. The machine can choose a code from the list (or not) based on what properties are not coded\n\nThese modes are differentiated by the 'exact' parameter, so the client can indicate whether it only wants exact matches (including partial matches) or whether potential matches based on text matching are desired\n \nThe find-matches operation is still preliminary. The interface can be expected to change as more experience is gained from implementations.","code":"find-matches","resource":["CodeSystem"],"system":false,"type":true,"instance":true,"parameter":[{"name":"system","use":"in","min":0,"max":"1","documentation":"The system in which composition is to be performed. This must be provided unless the operation is invoked on a code system instance","type":"uri"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The version of the system for the inferencing to be performed","type":"string"},{"name":"property","use":"in","min":0,"max":"*","documentation":"One or more properties that contain information to be composed into the code","part":[{"name":"code","use":"in","min":1,"max":"1","documentation":"Identifies the property provided","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"}],"name":"value","use":"in","min":0,"max":"1","documentation":"The value of the property provided","type":"Element"},{"name":"subproperty","use":"in","min":0,"max":"*","documentation":"Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)","part":[{"name":"code","use":"in","min":1,"max":"1","documentation":"Identifies the sub-property provided","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"}],"name":"value","use":"in","min":1,"max":"1","documentation":"The value of the sub-property provided","type":"Element"}]}]},{"name":"exact","use":"in","min":1,"max":"1","documentation":"Whether the operation is being used by a human ('false'), or a machine ('true'). If the operation is being used by a human, the terminology server can return a list of possible matches, with commentary. For a machine, the server returns complete or partial matches, not possible matches. The default value is 'false'","type":"boolean"},{"name":"compositional","use":"in","min":0,"max":"1","documentation":"Post-coordinated expressions are allowed to be returned in the matching codes (mainly for SNOMED CT). Default = false","type":"boolean"},{"name":"match","use":"out","min":0,"max":"*","documentation":"Concepts returned by the server as a result of the inferencing operation","part":[{"name":"code","use":"out","min":1,"max":"1","documentation":"A code that matches the properties provided","type":"Coding"},{"name":"unmatched","use":"out","min":0,"max":"*","documentation":"One or more properties that contain properties that could not be matched into the code","part":[{"name":"code","use":"out","min":1,"max":"1","documentation":"Identifies the property provided","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"}],"name":"value","use":"out","min":1,"max":"1","documentation":"The value of the property provided","type":"Element"},{"name":"property","use":"out","min":0,"max":"*","documentation":"Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)","part":[{"name":"code","use":"out","min":1,"max":"1","documentation":"Identifies the sub-property provided","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"}],"name":"value","use":"out","min":1,"max":"1","documentation":"The value of the sub-property provided","type":"Element"}]}]},{"name":"comment","use":"out","min":0,"max":"1","documentation":"Information about the quality of the match, if operation is for a human","type":"string"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct InputPropertySubproperty {
        #[doc = "Identifies the sub-property provided"]
        pub code: FHIRCode,
        #[doc = "The value of the sub-property provided"]
        pub value: ParametersParameterValueTypeChoice,
    }
    impl From<InputPropertySubproperty> for Resource {
        fn from(value: InputPropertySubproperty) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct InputProperty {
        #[doc = "Identifies the property provided"]
        pub code: FHIRCode,
        #[doc = "The value of the property provided"]
        pub value: Option<ParametersParameterValueTypeChoice>,
        #[doc = "Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)"]
        #[parameter_nested]
        pub subproperty: Option<Vec<InputPropertySubproperty>>,
    }
    impl From<InputProperty> for Resource {
        fn from(value: InputProperty) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The system in which composition is to be performed. This must be provided unless the operation is"]
        #[doc = "invoked on a code system instance"]
        pub system: Option<FHIRUri>,
        #[doc = "The version of the system for the inferencing to be performed"]
        pub version: Option<FHIRString>,
        #[doc = "One or more properties that contain information to be composed into the code"]
        #[parameter_nested]
        pub property: Option<Vec<InputProperty>>,
        #[doc = "Whether the operation is being used by a human (`false`), or a machine (`true`). If the operation is"]
        #[doc = "being used by a human, the terminology server can return a list of possible matches, with"]
        #[doc = "commentary. For a machine, the server returns complete or partial matches, not possible matches. The"]
        #[doc = "default value is `false`"]
        pub exact: FHIRBoolean,
        #[doc = "Post-coordinated expressions are allowed to be returned in the matching codes (mainly for SNOMED"]
        #[doc = "CT). Default = false"]
        pub compositional: Option<FHIRBoolean>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputMatchUnmatchedProperty {
        #[doc = "Identifies the sub-property provided"]
        pub code: FHIRCode,
        #[doc = "The value of the sub-property provided"]
        pub value: ParametersParameterValueTypeChoice,
    }
    impl From<OutputMatchUnmatchedProperty> for Resource {
        fn from(value: OutputMatchUnmatchedProperty) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputMatchUnmatched {
        #[doc = "Identifies the property provided"]
        pub code: FHIRCode,
        #[doc = "The value of the property provided"]
        pub value: ParametersParameterValueTypeChoice,
        #[doc = "Nested Properties (mainly used for SNOMED CT composition, for relationship Groups)"]
        #[parameter_nested]
        pub property: Option<Vec<OutputMatchUnmatchedProperty>>,
    }
    impl From<OutputMatchUnmatched> for Resource {
        fn from(value: OutputMatchUnmatched) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputMatch {
        #[doc = "A code that matches the properties provided"]
        pub code: Coding,
        #[doc = "One or more properties that contain properties that could not be matched into the code"]
        #[parameter_nested]
        pub unmatched: Option<Vec<OutputMatchUnmatched>>,
        #[doc = "Information about the quality of the match, if operation is for a human"]
        pub comment: Option<FHIRString>,
    }
    impl From<OutputMatch> for Resource {
        fn from(value: OutputMatch) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Concepts returned by the server as a result of the inferencing operation"]
        #[parameter_rename = "match"]
        #[parameter_nested]
        pub match_: Option<Vec<OutputMatch>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Given a code/system, or a Coding, get additional details about the concept, including definition,"]
#[doc = "status, designations, and properties. One of the products of this operation is a full decomposition"]
#[doc = "of a code from a structured terminology."]
#[doc = ""]
#[doc = "When invoking this operation, a client SHALL provide both a system and a code, either using the"]
#[doc = "system+code parameters, or in the coding parameter. Other parameters are optional"]
pub mod CodeSystemLookup {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, ParametersParameterValueTypeChoice,
        Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        Coding, FHIRCode, FHIRDateTime, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "lookup";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CodeSystem-lookup","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Concept Look Up &amp; Decomposition</h2><p>OPERATION: Concept Look Up &amp; Decomposition</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CodeSystem-lookup</pre><div><p>Given a code/system, or a Coding, get additional details about the concept, including definition, status, designations, and properties. One of the products of this operation is a full decomposition of a code from a structured terminology.</p>\n<p>When invoking this operation, a client SHALL provide both a system and a code, either using the system+code parameters, or in the coding parameter. Other parameters are optional</p>\n</div><p>URL: [base]/CodeSystem/$lookup</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>code</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The code that is to be located. If a code is provided, a system must be provided</p>\n</div></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The system for the code that is to be located</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the system, if one was provided in the source data</p>\n</div></td></tr><tr><td>IN</td><td>coding</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A coding to look up</p>\n</div></td></tr><tr><td>IN</td><td>date</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.</p>\n</div></td></tr><tr><td>IN</td><td>displayLanguage</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The requested language for display (see $expand.displayLanguage)</p>\n</div></td></tr><tr><td>IN</td><td>property</td><td>0..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>A property that the client wishes to be returned in the output. If no properties are specified, the server chooses what to return. The following properties are defined for all code systems: url, name, version (code system info) and code information: display, definition, designation, parent and child, and for designations, lang.X where X is a designation language code. Some of the properties are returned explicit in named parameters (when the names match), and the rest (except for lang.X) in the property parameter group</p>\n</div></td></tr><tr><td>OUT</td><td>name</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A display name for the code system</p>\n</div></td></tr><tr><td>OUT</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version that these details are based on</p>\n</div></td></tr><tr><td>OUT</td><td>display</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The preferred display for this concept</p>\n</div></td></tr><tr><td>OUT</td><td>designation</td><td>0..*</td><td></td><td/><td><div><p>Additional representations for this concept</p>\n</div></td></tr><tr><td>OUT</td><td>designation.language</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The language this designation is defined for</p>\n</div></td></tr><tr><td>OUT</td><td>designation.use</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A code that details how this designation would be used</p>\n</div></td></tr><tr><td>OUT</td><td>designation.value</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The text value for this designation</p>\n</div></td></tr><tr><td>OUT</td><td>property</td><td>0..*</td><td></td><td/><td><div><p>One or more properties that contain additional information about the code, including status. For complex terminologies (e.g. SNOMED CT, LOINC, medications), these properties serve to decompose the code</p>\n</div></td></tr><tr><td>OUT</td><td>property.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the property returned</p>\n</div></td></tr><tr><td>OUT</td><td>property.value</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a> | <a href=\"datatypes.html#decimal\">decimal</a></td><td/><td><div><p>The value of the property returned</p>\n</div></td></tr><tr><td>OUT</td><td>property.description</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Human Readable representation of the property value (e.g. display for a code)</p>\n</div></td></tr><tr><td>OUT</td><td>property.subproperty</td><td>0..*</td><td></td><td/><td><div><p>Nested Properties (mainly used for SNOMED CT decomposition, for relationship Groups)</p>\n</div></td></tr><tr><td>OUT</td><td>property.subproperty.code</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Identifies the sub-property returned</p>\n</div></td></tr><tr><td>OUT</td><td>property.subproperty.value</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a> | <a href=\"datatypes.html#Coding\">Coding</a> | <a href=\"datatypes.html#string\">string</a> | <a href=\"datatypes.html#integer\">integer</a> | <a href=\"datatypes.html#boolean\">boolean</a> | <a href=\"datatypes.html#dateTime\">dateTime</a> | <a href=\"datatypes.html#decimal\">decimal</a></td><td/><td><div><p>The value of the sub-property returned</p>\n</div></td></tr><tr><td>OUT</td><td>property.subproperty.description</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Human Readable representation of the property value (e.g. display for a code)</p>\n</div></td></tr></table><div><p>Note that the $lookup operation is more than just a code system search  - the server finds the concept, and gathers the return information from the underlying code system definitions.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/CodeSystem-lookup","version":"4.0.1","name":"Concept Look Up & Decomposition","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Given a code/system, or a Coding, get additional details about the concept, including definition, status, designations, and properties. One of the products of this operation is a full decomposition of a code from a structured terminology.\n\nWhen invoking this operation, a client SHALL provide both a system and a code, either using the system+code parameters, or in the coding parameter. Other parameters are optional","code":"lookup","comment":"Note that the $lookup operation is more than just a code system search  - the server finds the concept, and gathers the return information from the underlying code system definitions.","resource":["CodeSystem"],"system":false,"type":true,"instance":false,"parameter":[{"name":"code","use":"in","min":0,"max":"1","documentation":"The code that is to be located. If a code is provided, a system must be provided","type":"code"},{"name":"system","use":"in","min":0,"max":"1","documentation":"The system for the code that is to be located","type":"uri"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The version of the system, if one was provided in the source data","type":"string"},{"name":"coding","use":"in","min":0,"max":"1","documentation":"A coding to look up","type":"Coding"},{"name":"date","use":"in","min":0,"max":"1","documentation":"The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.","type":"dateTime"},{"name":"displayLanguage","use":"in","min":0,"max":"1","documentation":"The requested language for display (see $expand.displayLanguage)","type":"code"},{"name":"property","use":"in","min":0,"max":"*","documentation":"A property that the client wishes to be returned in the output. If no properties are specified, the server chooses what to return. The following properties are defined for all code systems: url, name, version (code system info) and code information: display, definition, designation, parent and child, and for designations, lang.X where X is a designation language code. Some of the properties are returned explicit in named parameters (when the names match), and the rest (except for lang.X) in the property parameter group","type":"code"},{"name":"name","use":"out","min":1,"max":"1","documentation":"A display name for the code system","type":"string"},{"name":"version","use":"out","min":0,"max":"1","documentation":"The version that these details are based on","type":"string"},{"name":"display","use":"out","min":1,"max":"1","documentation":"The preferred display for this concept","type":"string"},{"name":"designation","use":"out","min":0,"max":"*","documentation":"Additional representations for this concept","part":[{"name":"language","use":"out","min":0,"max":"1","documentation":"The language this designation is defined for","type":"code"},{"name":"use","use":"out","min":0,"max":"1","documentation":"A code that details how this designation would be used","type":"Coding"},{"name":"value","use":"out","min":1,"max":"1","documentation":"The text value for this designation","type":"string"}]},{"name":"property","use":"out","min":0,"max":"*","documentation":"One or more properties that contain additional information about the code, including status. For complex terminologies (e.g. SNOMED CT, LOINC, medications), these properties serve to decompose the code","part":[{"name":"code","use":"out","min":1,"max":"1","documentation":"Identifies the property returned","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"decimal"}],"name":"value","use":"out","min":0,"max":"1","documentation":"The value of the property returned","type":"Element"},{"name":"description","use":"out","min":0,"max":"1","documentation":"Human Readable representation of the property value (e.g. display for a code)","type":"string"},{"name":"subproperty","use":"out","min":0,"max":"*","documentation":"Nested Properties (mainly used for SNOMED CT decomposition, for relationship Groups)","part":[{"name":"code","use":"out","min":1,"max":"1","documentation":"Identifies the sub-property returned","type":"code"},{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"code"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"Coding"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"string"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"integer"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"boolean"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"dateTime"},{"url":"http://hl7.org/fhir/StructureDefinition/operationdefinition-allowed-type","valueUri":"decimal"}],"name":"value","use":"out","min":1,"max":"1","documentation":"The value of the sub-property returned","type":"Element"},{"name":"description","use":"out","min":0,"max":"1","documentation":"Human Readable representation of the property value (e.g. display for a code)","type":"string"}]}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The code that is to be located. If a code is provided, a system must be provided"]
        pub code: Option<FHIRCode>,
        #[doc = "The system for the code that is to be located"]
        pub system: Option<FHIRUri>,
        #[doc = "The version of the system, if one was provided in the source data"]
        pub version: Option<FHIRString>,
        #[doc = "A coding to look up"]
        pub coding: Option<Coding>,
        #[doc = "The date for which the information should be returned. Normally, this is the current conditions"]
        #[doc = "(which is the default value) but under some circumstances, systems need to acccess this information"]
        #[doc = "as it would have been in the past. A typical example of this would be where code selection is"]
        #[doc = "constrained to the set of codes that were available when the patient was treated, not when the"]
        #[doc = "record is being edited. Note that which date is appropriate is a matter for implementation policy."]
        pub date: Option<FHIRDateTime>,
        #[doc = "The requested language for display (see $expand.displayLanguage)"]
        pub displayLanguage: Option<FHIRCode>,
        #[doc = "A property that the client wishes to be returned in the output. If no properties are specified, the"]
        #[doc = "server chooses what to return. The following properties are defined for all code systems: url, name,"]
        #[doc = "version (code system info) and code information: display, definition, designation, parent and child,"]
        #[doc = "and for designations, lang.X where X is a designation language code. Some of the properties are"]
        #[doc = "returned explicit in named parameters (when the names match), and the rest (except for lang.X) in"]
        #[doc = "the property parameter group"]
        pub property: Option<Vec<FHIRCode>>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputDesignation {
        #[doc = "The language this designation is defined for"]
        pub language: Option<FHIRCode>,
        #[doc = "A code that details how this designation would be used"]
        #[parameter_rename = "use"]
        pub use_: Option<Coding>,
        #[doc = "The text value for this designation"]
        pub value: FHIRString,
    }
    impl From<OutputDesignation> for Resource {
        fn from(value: OutputDesignation) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputPropertySubproperty {
        #[doc = "Identifies the sub-property returned"]
        pub code: FHIRCode,
        #[doc = "The value of the sub-property returned"]
        pub value: ParametersParameterValueTypeChoice,
        #[doc = "Human Readable representation of the property value (e.g. display for a code)"]
        pub description: Option<FHIRString>,
    }
    impl From<OutputPropertySubproperty> for Resource {
        fn from(value: OutputPropertySubproperty) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputProperty {
        #[doc = "Identifies the property returned"]
        pub code: FHIRCode,
        #[doc = "The value of the property returned"]
        pub value: Option<ParametersParameterValueTypeChoice>,
        #[doc = "Human Readable representation of the property value (e.g. display for a code)"]
        pub description: Option<FHIRString>,
        #[doc = "Nested Properties (mainly used for SNOMED CT decomposition, for relationship Groups)"]
        #[parameter_nested]
        pub subproperty: Option<Vec<OutputPropertySubproperty>>,
    }
    impl From<OutputProperty> for Resource {
        fn from(value: OutputProperty) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "A display name for the code system"]
        pub name: FHIRString,
        #[doc = "The version that these details are based on"]
        pub version: Option<FHIRString>,
        #[doc = "The preferred display for this concept"]
        pub display: FHIRString,
        #[doc = "Additional representations for this concept"]
        #[parameter_nested]
        pub designation: Option<Vec<OutputDesignation>>,
        #[doc = "One or more properties that contain additional information about the code, including status. For"]
        #[doc = "complex terminologies (e.g. SNOMED CT, LOINC, medications), these properties serve to decompose the"]
        #[doc = "code"]
        #[parameter_nested]
        pub property: Option<Vec<OutputProperty>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Test the subsumption relationship between code/Coding A and code/Coding B given the semantics of"]
#[doc = "subsumption in the underlying code system (see"]
#[doc = "[`hierarchyMeaning`](codesystem-definitions.html#CodeSystem.hierarchyMeaning))."]
#[doc = ""]
#[doc = "When invoking this operation, a client SHALL provide both a and codes, either as code or Coding"]
#[doc = "parameters. The system parameter is required unless the operation is invoked on an instance of a"]
#[doc = "code system resource. Other parameters are optional"]
pub mod CodeSystemSubsumes {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{Coding, FHIRCode, FHIRString, FHIRUri};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "subsumes";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CodeSystem-subsumes","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Subsumption Testing</h2><p>OPERATION: Subsumption Testing</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CodeSystem-subsumes</pre><div><p>Test the subsumption relationship between code/Coding A and code/Coding B given the semantics of subsumption in the underlying code system (see <a href=\"codesystem-definitions.html#CodeSystem.hierarchyMeaning\">hierarchyMeaning</a>).</p>\n<p>When invoking this operation, a client SHALL provide both a and codes, either as code or Coding parameters. The system parameter is required unless the operation is invoked on an instance of a code system resource. Other parameters are optional</p>\n</div><p>URL: [base]/CodeSystem/$subsumes</p><p>URL: [base]/CodeSystem/[id]/$subsumes</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>codeA</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The &quot;A&quot; code that is to be tested. If a code is provided, a system must be provided</p>\n</div></td></tr><tr><td>IN</td><td>codeB</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The &quot;B&quot; code that is to be tested. If a code is provided, a system must be provided</p>\n</div></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The code system in which subsumption testing is to be performed. This must be provided unless the operation is invoked on a code system instance</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the code system, if one was provided in the source data</p>\n</div></td></tr><tr><td>IN</td><td>codingA</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>The &quot;A&quot; Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established</p>\n</div></td></tr><tr><td>IN</td><td>codingB</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>The &quot;B&quot; Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established</p>\n</div></td></tr><tr><td>OUT</td><td>outcome</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td><a href=\"valueset-concept-subsumption-outcome.html\">http://hl7.org/fhir/ValueSet/concept-subsumption-outcome|4.0.1</a> (Required)</td><td><div><p>The subsumption relationship between code/Coding &quot;A&quot; and code/Coding &quot;B&quot;. There are 4 possible codes to be returned (equivalent, subsumes, subsumed-by, and not-subsumed) as defined in the concept-subsumption-outcome value set.  If the server is unable to determine the relationship between the codes/Codings, then it returns an error response with an OperationOutcome.</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/CodeSystem-subsumes","version":"4.0.1","name":"Subsumption Testing","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Test the subsumption relationship between code/Coding A and code/Coding B given the semantics of subsumption in the underlying code system (see [hierarchyMeaning](codesystem-definitions.html#CodeSystem.hierarchyMeaning)).\n\nWhen invoking this operation, a client SHALL provide both a and codes, either as code or Coding parameters. The system parameter is required unless the operation is invoked on an instance of a code system resource. Other parameters are optional","code":"subsumes","resource":["CodeSystem"],"system":false,"type":true,"instance":true,"parameter":[{"name":"codeA","use":"in","min":0,"max":"1","documentation":"The \"A\" code that is to be tested. If a code is provided, a system must be provided","type":"code"},{"name":"codeB","use":"in","min":0,"max":"1","documentation":"The \"B\" code that is to be tested. If a code is provided, a system must be provided","type":"code"},{"name":"system","use":"in","min":0,"max":"1","documentation":"The code system in which subsumption testing is to be performed. This must be provided unless the operation is invoked on a code system instance","type":"uri"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The version of the code system, if one was provided in the source data","type":"string"},{"name":"codingA","use":"in","min":0,"max":"1","documentation":"The \"A\" Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established","type":"Coding"},{"name":"codingB","use":"in","min":0,"max":"1","documentation":"The \"B\" Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established","type":"Coding"},{"name":"outcome","use":"out","min":1,"max":"1","documentation":"The subsumption relationship between code/Coding \"A\" and code/Coding \"B\". There are 4 possible codes to be returned (equivalent, subsumes, subsumed-by, and not-subsumed) as defined in the concept-subsumption-outcome value set.  If the server is unable to determine the relationship between the codes/Codings, then it returns an error response with an `OperationOutcome`.","type":"code","binding":{"strength":"required","valueSet":"http://hl7.org/fhir/ValueSet/concept-subsumption-outcome|4.0.1"}}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The \"A\" code that is to be tested. If a code is provided, a system must be provided"]
        pub codeA: Option<FHIRCode>,
        #[doc = "The \"B\" code that is to be tested. If a code is provided, a system must be provided"]
        pub codeB: Option<FHIRCode>,
        #[doc = "The code system in which subsumption testing is to be performed. This must be provided unless the"]
        #[doc = "operation is invoked on a code system instance"]
        pub system: Option<FHIRUri>,
        #[doc = "The version of the code system, if one was provided in the source data"]
        pub version: Option<FHIRString>,
        #[doc = "The \"A\" Coding that is to be tested. The code system does not have to match the specified"]
        #[doc = "subsumption code system, but the relationships between the code systems must be well established"]
        pub codingA: Option<Coding>,
        #[doc = "The \"B\" Coding that is to be tested. The code system does not have to match the specified"]
        #[doc = "subsumption code system, but the relationships between the code systems must be well established"]
        pub codingB: Option<Coding>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The subsumption relationship between code/Coding \"A\" and code/Coding \"B\". There are 4 possible codes"]
        #[doc = "to be returned (equivalent, subsumes, subsumed-by, and not-subsumed) as defined in the"]
        #[doc = "concept-subsumption-outcome value set. If the server is unable to determine the relationship between"]
        #[doc = "the codes/Codings, then it returns an error response with an `OperationOutcome`."]
        pub outcome: FHIRCode,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Validate that a coded value is in the code system. If the operation is not called at the instance"]
#[doc = "level, one of the parameters \"url\" or \"codeSystem\" must be provided. The operation returns a result"]
#[doc = "(true / false), an error message, and the recommended display for the code."]
#[doc = ""]
#[doc = "When invoking this operation, a client SHALL provide one (and only one) of the parameters"]
#[doc = "(code+system, coding, or codeableConcept). Other parameters (including version and display) are"]
#[doc = "optional"]
pub mod CodeSystemValidateCode {
    use haste_fhir_model::r4::generated::resources::{
        CodeSystem, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        CodeableConcept, Coding, FHIRBoolean, FHIRCode, FHIRDateTime, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "validate-code";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CodeSystem-validate-code","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Code System based Validation</h2><p>OPERATION: Code System based Validation</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CodeSystem-validate-code</pre><div><p>Validate that a coded value is in the code system. If the operation is not called at the instance level, one of the parameters &quot;url&quot; or &quot;codeSystem&quot; must be provided. The operation returns a result (true / false), an error message, and the recommended display for the code.</p>\n<p>When invoking this operation, a client SHALL provide one (and only one) of the parameters (code+system, coding, or codeableConcept). Other parameters (including version and display) are optional</p>\n</div><p>URL: [base]/CodeSystem/$validate-code</p><p>URL: [base]/CodeSystem/[id]/$validate-code</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>CodeSystem URL. The server must know the code system (e.g. it is defined explicitly in the server'scode systems, or it is known implicitly by the server</p>\n</div></td></tr><tr><td>IN</td><td>codeSystem</td><td>0..1</td><td><a href=\"codesystem.html\">CodeSystem</a></td><td/><td><div><p>The codeSystem is provided directly as part of the request. Servers may choose not to accept code systems in this fashion. This parameter is used when the client wants the server to check against a code system that is not stored on the server</p>\n</div></td></tr><tr><td>IN</td><td>code</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The code that is to be validated</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the code system, if one was provided in the source data</p>\n</div></td></tr><tr><td>IN</td><td>display</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name in an extension in the outcome. Whether displays are case sensitive is code system dependent</p>\n</div></td></tr><tr><td>IN</td><td>coding</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A coding to validate. The system must match the specified code system</p>\n</div></td></tr><tr><td>IN</td><td>codeableConcept</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>A full codeableConcept to validate. The server returns true if one of the coding values is in the code system, and may also validate that the codings are not in conflict with each other if more than one is present</p>\n</div></td></tr><tr><td>IN</td><td>date</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.</p>\n</div></td></tr><tr><td>IN</td><td>abstract</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is false, abstract codes are not considered to be valid.</p>\n<p>Note that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in an actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.</p>\n</div></td></tr><tr><td>IN</td><td>displayLanguage</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Specifies the language to be used for description when validating the display property</p>\n</div></td></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>True if the concept details supplied are valid</p>\n</div></td></tr><tr><td>OUT</td><td>message</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Error details, if result = false. If this is provided when result = true, the message carries hints and warnings</p>\n</div></td></tr><tr><td>OUT</td><td>display</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A valid display for the concept if the system wishes to display this to a user</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/CodeSystem-validate-code","version":"4.0.1","name":"Code System based Validation","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Validate that a coded value is in the code system. If the operation is not called at the instance level, one of the parameters \"url\" or \"codeSystem\" must be provided. The operation returns a result (true / false), an error message, and the recommended display for the code.\n\nWhen invoking this operation, a client SHALL provide one (and only one) of the parameters (code+system, coding, or codeableConcept). Other parameters (including version and display) are optional","code":"validate-code","resource":["CodeSystem"],"system":false,"type":true,"instance":true,"parameter":[{"name":"url","use":"in","min":0,"max":"1","documentation":"`CodeSystem` URL. The server must know the code system (e.g. it is defined explicitly in the server'scode systems, or it is known implicitly by the server","type":"uri"},{"name":"codeSystem","use":"in","min":0,"max":"1","documentation":"The codeSystem is provided directly as part of the request. Servers may choose not to accept code systems in this fashion. This parameter is used when the client wants the server to check against a code system that is not stored on the server","type":"CodeSystem"},{"name":"code","use":"in","min":0,"max":"1","documentation":"The code that is to be validated","type":"code"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The version of the code system, if one was provided in the source data","type":"string"},{"name":"display","use":"in","min":0,"max":"1","documentation":"The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name in an extension in the outcome. Whether displays are case sensitive is code system dependent","type":"string"},{"name":"coding","use":"in","min":0,"max":"1","documentation":"A coding to validate. The system must match the specified code system","type":"Coding"},{"name":"codeableConcept","use":"in","min":0,"max":"1","documentation":"A full codeableConcept to validate. The server returns true if one of the coding values is in the code system, and may also validate that the codings are not in conflict with each other if more than one is present","type":"CodeableConcept"},{"name":"date","use":"in","min":0,"max":"1","documentation":"The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.","type":"dateTime"},{"name":"abstract","use":"in","min":0,"max":"1","documentation":"If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is false, abstract codes are not considered to be valid.\n\nNote that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in an actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.","type":"boolean"},{"name":"displayLanguage","use":"in","min":0,"max":"1","documentation":"Specifies the language to be used for description when validating the display property","type":"code"},{"name":"result","use":"out","min":1,"max":"1","documentation":"True if the concept details supplied are valid","type":"boolean"},{"name":"message","use":"out","min":0,"max":"1","documentation":"Error details, if result = false. If this is provided when result = true, the message carries hints and warnings","type":"string"},{"name":"display","use":"out","min":0,"max":"1","documentation":"A valid display for the concept if the system wishes to display this to a user","type":"string"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "`CodeSystem` URL. The server must know the code system (e.g. it is defined explicitly in the"]
        #[doc = "server'scode systems, or it is known implicitly by the server"]
        pub url: Option<FHIRUri>,
        #[doc = "The codeSystem is provided directly as part of the request. Servers may choose not to accept code"]
        #[doc = "systems in this fashion. This parameter is used when the client wants the server to check against a"]
        #[doc = "code system that is not stored on the server"]
        pub codeSystem: Option<CodeSystem>,
        #[doc = "The code that is to be validated"]
        pub code: Option<FHIRCode>,
        #[doc = "The version of the code system, if one was provided in the source data"]
        pub version: Option<FHIRString>,
        #[doc = "The display associated with the code, if provided. If a display is provided a code must be provided."]
        #[doc = "If no display is provided, the server cannot validate the display value, but may choose to return a"]
        #[doc = "recommended display name in an extension in the outcome. Whether displays are case sensitive is code"]
        #[doc = "system dependent"]
        pub display: Option<FHIRString>,
        #[doc = "A coding to validate. The system must match the specified code system"]
        pub coding: Option<Coding>,
        #[doc = "A full codeableConcept to validate. The server returns true if one of the coding values is in the"]
        #[doc = "code system, and may also validate that the codings are not in conflict with each other if more than"]
        #[doc = "one is present"]
        pub codeableConcept: Option<CodeableConcept>,
        #[doc = "The date for which the validation should be checked. Normally, this is the current conditions (which"]
        #[doc = "is the default values) but under some circumstances, systems need to validate that a correct code"]
        #[doc = "was used at some point in the past. A typical example of this would be where code selection is"]
        #[doc = "constrained to the set of codes that were available when the patient was treated, not when the"]
        #[doc = "record is being edited. Note that which date is appropriate is a matter for implementation policy."]
        pub date: Option<FHIRDateTime>,
        #[doc = "If this parameter has a value of true, the client is stating that the validation is being performed"]
        #[doc = "in a context where a concept designated as `abstract` is appropriate/allowed to be used, and the"]
        #[doc = "server should regard abstract codes as valid. If this parameter is false, abstract codes are not"]
        #[doc = "considered to be valid."]
        #[doc = ""]
        #[doc = "Note that. `abstract` is a property defined by many HL7 code systems that indicates that the concept"]
        #[doc = "is a logical grouping concept that is not intended to be used asa `concrete` concept to in an actual"]
        #[doc = "patient/care/process record. This language is borrowed from Object Orienated theory where `asbtract`"]
        #[doc = "objects are never instantiated. However in the general record and terminology eco-system, there are"]
        #[doc = "many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when"]
        #[doc = "editing value sets themselves. This parameter allows a client to indicate to the server that it is"]
        #[doc = "working in such a context."]
        #[parameter_rename = "abstract"]
        pub abstract_: Option<FHIRBoolean>,
        #[doc = "Specifies the language to be used for description when validating the display property"]
        pub displayLanguage: Option<FHIRCode>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "True if the concept details supplied are valid"]
        pub result: FHIRBoolean,
        #[doc = "Error details, if result = false. If this is provided when result = true, the message carries hints"]
        #[doc = "and warnings"]
        pub message: Option<FHIRString>,
        #[doc = "A valid display for the concept if the system wishes to display this to a user"]
        pub display: Option<FHIRString>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "A client can ask a server to generate a fully bundled document from a composition resource. The"]
#[doc = "server takes the composition resource, locates all the referenced resources and other additional"]
#[doc = "resources as configured or requested and either returns a full document bundle, or returns an error."]
#[doc = "Note that since this is a search operation, the document bundle is wrapped inside the search bundle."]
#[doc = "If some of the resources are located on other servers, it is at the discretion of the server whether"]
#[doc = "to retrieve them or return an error. If the correct version of the document that would be generated"]
#[doc = "already exists, then the server can return the existing one."]
pub mod CompositionDocument {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRBoolean, FHIRUri};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "document";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Composition-document","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Generate a Document</h2><p>OPERATION: Generate a Document</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Composition-document</pre><div><p>A client can ask a server to generate a fully bundled document from a composition resource. The server takes the composition resource, locates all the referenced resources and other additional resources as configured or requested and either returns a full document bundle, or returns an error. Note that since this is a search operation, the document bundle is  wrapped inside the search bundle.  If some of the resources are located on other servers, it is at the discretion of the  server whether to retrieve them or return an error. If the correct version of the document  that would be generated already exists, then the server can return the existing one.</p>\n</div><p>URL: [base]/Composition/$document</p><p>URL: [base]/Composition/[id]/$document</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>id</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Identifies the composition to use. This can either be a simple id, which identifies a composition, or it can be a full URL, which identifies a composition on another server.</p>\n<p>Notes:</p>\n<ul>\n<li>GET [base]/Composition/[id]/$document is identical in meaning to GET [base]/Composition/$document?id=[id]</li>\n<li>the id parameter SHALL NOT be used if the operation is requested on a particular composition (e.g.  GET [base]/Composition/[id]/$document?id=[id] is not allowed)</li>\n<li>Servers are not required to support generating documents on Compositions located on another server</li>\n</ul>\n</div></td></tr><tr><td>IN</td><td>persist</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Whether to store the document at the bundle end-point (/Bundle) or not once it is generated. Value = true or false (default is for the server to decide). If the document is stored, it's location can be inferred from the Bundle.id, but it SHOULD be provided explicitly in the HTTP Location header in the response</p>\n</div></td></tr><tr><td>IN</td><td>graph</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a <a href=\"graphdefinition.html\">GraphDefinition</a> that it controls what resources are to be added to the bundle when building the document. The GraphDefinition can also specify profiles that apply to the various resources</p>\n</div></td></tr></table><div><p>Note: this operation definition does not resolve the question how document signatures are created. This is an open issue during the period of trial use, and feedback is requested regarding this question</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Composition-document","version":"4.0.1","name":"Generate a Document","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"A client can ask a server to generate a fully bundled document from a composition resource. The server takes the composition resource, locates all the referenced resources and other additional resources as configured or requested and either returns a full document bundle, or returns an error. Note that since this is a search operation, the document bundle is  wrapped inside the search bundle.  If some of the resources are located on other servers, it is at the discretion of the  server whether to retrieve them or return an error. If the correct version of the document  that would be generated already exists, then the server can return the existing one.","code":"document","comment":"Note: this operation definition does not resolve the question how document signatures are created. This is an open issue during the period of trial use, and feedback is requested regarding this question","resource":["Composition"],"system":false,"type":true,"instance":true,"parameter":[{"name":"id","use":"in","min":0,"max":"1","documentation":"Identifies the composition to use. This can either be a simple id, which identifies a composition, or it can be a full URL, which identifies a composition on another server. \n\nNotes: \n\n* GET [base]/Composition/[id]/$document is identical in meaning to GET [base]/Composition/$document?id=[id]\n* the id parameter SHALL NOT be used if the operation is requested on a particular composition (e.g.  GET [base]/Composition/[id]/$document?id=[id] is not allowed)\n* Servers are not required to support generating documents on Compositions located on another server","type":"uri"},{"name":"persist","use":"in","min":0,"max":"1","documentation":"Whether to store the document at the bundle end-point (/Bundle) or not once it is generated. Value = true or false (default is for the server to decide). If the document is stored, it's location can be inferred from the Bundle.id, but it SHOULD be provided explicitly in the HTTP Location header in the response","type":"boolean"},{"name":"graph","use":"in","min":0,"max":"1","documentation":"Canonical reference to a `GraphDefinition`. If a URL is provided, it is the canonical reference to a [`GraphDefinition`](graphdefinition.html) that it controls what resources are to be added to the bundle when building the document. The `GraphDefinition` can also specify profiles that apply to the various resources","type":"uri"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Identifies the composition to use. This can either be a simple id, which identifies a composition,"]
        #[doc = "or it can be a full URL, which identifies a composition on another server."]
        #[doc = ""]
        #[doc = "Notes:"]
        #[doc = ""]
        #[doc = "* `GET [base]/Composition/[id]/$document` is identical in meaning to `GET"]
        #[doc = "[base]/Composition/$document?id=[id]`"]
        #[doc = "* the id parameter SHALL NOT be used if the operation is requested on a particular composition (e.g."]
        #[doc = "`GET [base]/Composition/[id]/$document?id=[id]` is not allowed)"]
        #[doc = "* Servers are not required to support generating documents on Compositions located on another server"]
        pub id: Option<FHIRUri>,
        #[doc = "Whether to store the document at the bundle end-point (/Bundle) or not once it is generated. Value ="]
        #[doc = "true or false (default is for the server to decide). If the document is stored, it's location can be"]
        #[doc = "inferred from the `Bundle.id`, but it SHOULD be provided explicitly in the HTTP Location header in"]
        #[doc = "the response"]
        pub persist: Option<FHIRBoolean>,
        #[doc = "Canonical reference to a `GraphDefinition`. If a URL is provided, it is the canonical reference to a"]
        #[doc = "[`GraphDefinition`](graphdefinition.html) that it controls what resources are to be added to the"]
        #[doc = "bundle when building the document. The `GraphDefinition` can also specify profiles that apply to the"]
        #[doc = "various resources"]
        pub graph: Option<FHIRUri>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {}
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation provides support for ongoing maintenance of a client-side [transitive closure"]
#[doc = "table](https://en.wikipedia.org/wiki/Transitive_closure#In_graph_theory) based on server-side"]
#[doc = "terminological logic. For details of how this is used, see [`Maintaining a Closure"]
#[doc = "Table`](terminology-service.html#closure)"]
pub mod ConceptMapClosure {
    use haste_fhir_model::r4::generated::resources::{
        ConceptMap, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{Coding, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "closure";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ConceptMap-closure","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Closure Table Maintenance</h2><p>OPERATION: Closure Table Maintenance</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ConceptMap-closure</pre><div><p>This operation provides support for ongoing maintenance of a client-side <a href=\"https://en.wikipedia.org/wiki/Transitive_closure#In_graph_theory\">transitive closure table</a> based on server-side terminological logic. For details of how this is used, see <a href=\"terminology-service.html#closure\">Maintaining a Closure Table</a></p>\n</div><p>URL: [base]/$closure</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>name</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The name that defines the particular context for the subsumption based closure table</p>\n</div></td></tr><tr><td>IN</td><td>concept</td><td>0..*</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>Concepts to add to the closure table</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A request to resynchronise - request to send all new entries since the nominated version was sent by the server</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"conceptmap.html\">ConceptMap</a></td><td/><td><div><p>A list of new entries (code / system --&gt; code/system) that the client should add to its closure table. The only kind of entry mapping equivalences that can be returned are equal, specializes, subsumes and unmatched</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/ConceptMap-closure","version":"4.0.1","name":"Closure Table Maintenance","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation provides support for ongoing maintenance of a client-side [transitive closure table](https://en.wikipedia.org/wiki/Transitive_closure#In_graph_theory) based on server-side terminological logic. For details of how this is used, see [Maintaining a Closure Table](terminology-service.html#closure)","code":"closure","resource":["ConceptMap"],"system":true,"type":false,"instance":false,"parameter":[{"name":"name","use":"in","min":1,"max":"1","documentation":"The name that defines the particular context for the subsumption based closure table","type":"string"},{"name":"concept","use":"in","min":0,"max":"*","documentation":"Concepts to add to the closure table","type":"Coding"},{"name":"version","use":"in","min":0,"max":"1","documentation":"A request to resynchronise - request to send all new entries since the nominated version was sent by the server","type":"string"},{"name":"return","use":"out","min":1,"max":"1","documentation":"A list of new entries (code / system --> code/system) that the client should add to its closure table. The only kind of entry mapping equivalences that can be returned are equal, specializes, subsumes and unmatched","type":"ConceptMap"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The name that defines the particular context for the subsumption based closure table"]
        pub name: FHIRString,
        #[doc = "Concepts to add to the closure table"]
        pub concept: Option<Vec<Coding>>,
        #[doc = "A request to resynchronise - request to send all new entries since the nominated version was sent by"]
        #[doc = "the server"]
        pub version: Option<FHIRString>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "A list of new entries (code / system --> code/system) that the client should add to its closure"]
        #[doc = "table. The only kind of entry mapping equivalences that can be returned are equal, specializes,"]
        #[doc = "subsumes and unmatched"]
        #[parameter_rename = "return"]
        pub return_: ConceptMap,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::ConceptMap(value.return_)
        }
    }
}
#[doc = "Translate a code from one value set to another, based on the existing value set and concept maps"]
#[doc = "resources, and/or other additional knowledge available to the server."]
#[doc = ""]
#[doc = "One (and only one) of the in parameters (code, coding, codeableConcept) must be provided, to"]
#[doc = "identify the code that is to be translated."]
#[doc = ""]
#[doc = "The operation returns a set of parameters including a `result` for whether there is an acceptable"]
#[doc = "match, and a list of possible matches. Note that the list of matches may include notes of codes for"]
#[doc = "which mapping is specifically excluded, so implementers have to check the match.equivalence for each"]
#[doc = "match"]
pub mod ConceptMapTranslate {
    use haste_fhir_model::r4::generated::resources::{
        ConceptMap, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        CodeableConcept, Coding, FHIRBoolean, FHIRCode, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "translate";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ConceptMap-translate","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Concept Translation</h2><p>OPERATION: Concept Translation</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ConceptMap-translate</pre><div><p>Translate a code from one value set to another, based on the existing value set and concept maps resources, and/or other additional knowledge available to the server.</p>\n<p>One (and only one) of the in parameters (code, coding, codeableConcept) must be provided, to identify the code that is to be translated.</p>\n<p>The operation returns a set of parameters including a 'result' for whether there is an acceptable match, and a list of possible matches. Note that the list of matches may include notes of codes for which mapping is specifically excluded, so implementers have to check the match.equivalence for each match</p>\n</div><p>URL: [base]/ConceptMap/$translate</p><p>URL: [base]/ConceptMap/[id]/$translate</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>A canonical URL for a concept map. The server must know the concept map (e.g. it is defined explicitly in the server's concept maps, or it is defined implicitly by some code system known to the server.</p>\n</div></td></tr><tr><td>IN</td><td>conceptMap</td><td>0..1</td><td><a href=\"conceptmap.html\">ConceptMap</a></td><td/><td><div><p>The concept map is provided directly as part of the request. Servers may choose not to accept concept maps in this fashion.</p>\n</div></td></tr><tr><td>IN</td><td>conceptMapVersion</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The identifier that is used to identify a specific version of the concept map to be used for the translation. This is an arbitrary value managed by the concept map author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.</p>\n</div></td></tr><tr><td>IN</td><td>code</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The code that is to be translated. If a code is provided, a system must be provided</p>\n</div></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The system for the code that is to be translated</p>\n</div></td></tr><tr><td>IN</td><td>version</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the system, if one was provided in the source data</p>\n</div></td></tr><tr><td>IN</td><td>source</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Identifies the value set used when the concept (system/code pair) was chosen. May be a logical id, or an absolute or relative location. The source value set is an optional parameter because in some cases, the client cannot know what the source value set is. However, without a source value set, the server may be unable to safely identify an applicable concept map, and would return an error. For this reason, a source value set SHOULD always be provided. Note that servers may be able to identify an appropriate concept map without a source value set if there is a full mapping for the entire code system in the concept map, or by manual intervention</p>\n</div></td></tr><tr><td>IN</td><td>coding</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A coding to translate</p>\n</div></td></tr><tr><td>IN</td><td>codeableConcept</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses</p>\n</div></td></tr><tr><td>IN</td><td>target</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Identifies the value set in which a translation is sought. May be a logical id, or an absolute or relative location. If there's no target specified, the server should return all known translations, along with their source</p>\n</div></td></tr><tr><td>IN</td><td>targetsystem</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>identifies a target code system in which a mapping is sought. This parameter is an alternative to the target parameter - only one is required. Searching for any translation to a target code system irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the discretion of the server to decide when to support this operation</p>\n</div></td></tr><tr><td>IN</td><td>dependency</td><td>0..*</td><td></td><td/><td><div><p>Another element that may help produce the correct mapping</p>\n</div></td></tr><tr><td>IN</td><td>dependency.element</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The element for this dependency</p>\n</div></td></tr><tr><td>IN</td><td>dependency.concept</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The value for this dependency</p>\n</div></td></tr><tr><td>IN</td><td>reverse</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>if this is true, then the operation should return all the codes that might be mapped to this code. This parameter reverses the meaning of the source and target parameters</p>\n</div></td></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>True if the concept could be translated successfully. The value can only be true if at least one returned match has an equivalence which is not  unmatched or disjoint</p>\n</div></td></tr><tr><td>OUT</td><td>message</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Error details, for display to a human. If this is provided when result = true, the message carries hints and warnings (e.g. a note that the matches could be improved by providing additional detail)</p>\n</div></td></tr><tr><td>OUT</td><td>match</td><td>0..*</td><td></td><td/><td><div><p>A concept in the target value set with an equivalence. Note that there may be multiple matches of equal or differing equivalence, and the matches may include equivalence values that mean that there is no match</p>\n</div></td></tr><tr><td>OUT</td><td>match.equivalence</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>A code indicating the equivalence of the translation, using values from <a href=\"valueset-concept-map-equivalence.html\">ConceptMapEquivalence</a></p>\n</div></td></tr><tr><td>OUT</td><td>match.concept</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>The translation outcome. Note that this would never have userSelected = true, since the process of translations implies that the user is not selecting the code (and only the client could know differently)</p>\n</div></td></tr><tr><td>OUT</td><td>match.product</td><td>0..*</td><td></td><td/><td><div><p>Another element that is the product of this mapping</p>\n</div></td></tr><tr><td>OUT</td><td>match.product.element</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The element for this product</p>\n</div></td></tr><tr><td>OUT</td><td>match.product.concept</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>The value for this product</p>\n</div></td></tr><tr><td>OUT</td><td>match.source</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The canonical reference to the concept map from which this mapping comes from</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/ConceptMap-translate","version":"4.0.1","name":"Concept Translation","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Translate a code from one value set to another, based on the existing value set and concept maps resources, and/or other additional knowledge available to the server. \r\n\r\n One (and only one) of the in parameters (code, coding, codeableConcept) must be provided, to identify the code that is to be translated.  \r\n\r\n The operation returns a set of parameters including a 'result' for whether there is an acceptable match, and a list of possible matches. Note that the list of matches may include notes of codes for which mapping is specifically excluded, so implementers have to check the match.equivalence for each match","code":"translate","resource":["ConceptMap"],"system":false,"type":true,"instance":true,"parameter":[{"name":"url","use":"in","min":0,"max":"1","documentation":"A canonical URL for a concept map. The server must know the concept map (e.g. it is defined explicitly in the server's concept maps, or it is defined implicitly by some code system known to the server.","type":"uri"},{"name":"conceptMap","use":"in","min":0,"max":"1","documentation":"The concept map is provided directly as part of the request. Servers may choose not to accept concept maps in this fashion.","type":"ConceptMap"},{"name":"conceptMapVersion","use":"in","min":0,"max":"1","documentation":"The identifier that is used to identify a specific version of the concept map to be used for the translation. This is an arbitrary value managed by the concept map author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.","type":"string"},{"name":"code","use":"in","min":0,"max":"1","documentation":"The code that is to be translated. If a code is provided, a system must be provided","type":"code"},{"name":"system","use":"in","min":0,"max":"1","documentation":"The system for the code that is to be translated","type":"uri"},{"name":"version","use":"in","min":0,"max":"1","documentation":"The version of the system, if one was provided in the source data","type":"string"},{"name":"source","use":"in","min":0,"max":"1","documentation":"Identifies the value set used when the concept (system/code pair) was chosen. May be a logical id, or an absolute or relative location. The source value set is an optional parameter because in some cases, the client cannot know what the source value set is. However, without a source value set, the server may be unable to safely identify an applicable concept map, and would return an error. For this reason, a source value set SHOULD always be provided. Note that servers may be able to identify an appropriate concept map without a source value set if there is a full mapping for the entire code system in the concept map, or by manual intervention","type":"uri"},{"name":"coding","use":"in","min":0,"max":"1","documentation":"A coding to translate","type":"Coding"},{"name":"codeableConcept","use":"in","min":0,"max":"1","documentation":"A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses","type":"CodeableConcept"},{"name":"target","use":"in","min":0,"max":"1","documentation":"Identifies the value set in which a translation is sought. May be a logical id, or an absolute or relative location. If there's no target specified, the server should return all known translations, along with their source","type":"uri"},{"name":"targetsystem","use":"in","min":0,"max":"1","documentation":"identifies a target code system in which a mapping is sought. This parameter is an alternative to the target parameter - only one is required. Searching for any translation to a target code system irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the discretion of the server to decide when to support this operation","type":"uri"},{"name":"dependency","use":"in","min":0,"max":"*","documentation":"Another element that may help produce the correct mapping","part":[{"name":"element","use":"in","min":0,"max":"1","documentation":"The element for this dependency","type":"uri"},{"name":"concept","use":"in","min":0,"max":"1","documentation":"The value for this dependency","type":"CodeableConcept"}]},{"name":"reverse","use":"in","min":0,"max":"1","documentation":"if this is true, then the operation should return all the codes that might be mapped to this code. This parameter reverses the meaning of the source and target parameters","type":"boolean"},{"name":"result","use":"out","min":1,"max":"1","documentation":"True if the concept could be translated successfully. The value can only be true if at least one returned match has an equivalence which is not  unmatched or disjoint","type":"boolean"},{"name":"message","use":"out","min":0,"max":"1","documentation":"Error details, for display to a human. If this is provided when result = true, the message carries hints and warnings (e.g. a note that the matches could be improved by providing additional detail)","type":"string"},{"name":"match","use":"out","min":0,"max":"*","documentation":"A concept in the target value set with an equivalence. Note that there may be multiple matches of equal or differing equivalence, and the matches may include equivalence values that mean that there is no match","part":[{"name":"equivalence","use":"out","min":0,"max":"1","documentation":"A code indicating the equivalence of the translation, using values from [`ConceptMapEquivalence`](valueset-concept-map-equivalence.html)","type":"code"},{"name":"concept","use":"out","min":0,"max":"1","documentation":"The translation outcome. Note that this would never have userSelected = true, since the process of translations implies that the user is not selecting the code (and only the client could know differently)","type":"Coding"},{"name":"product","use":"out","min":0,"max":"*","documentation":"Another element that is the product of this mapping","part":[{"name":"element","use":"out","min":0,"max":"1","documentation":"The element for this product","type":"uri"},{"name":"concept","use":"out","min":0,"max":"1","documentation":"The value for this product","type":"Coding"}]},{"name":"source","use":"out","min":0,"max":"1","documentation":"The canonical reference to the concept map from which this mapping comes from","type":"uri"}]}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct InputDependency {
        #[doc = "The element for this dependency"]
        pub element: Option<FHIRUri>,
        #[doc = "The value for this dependency"]
        pub concept: Option<CodeableConcept>,
    }
    impl From<InputDependency> for Resource {
        fn from(value: InputDependency) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A canonical URL for a concept map. The server must know the concept map (e.g. it is defined"]
        #[doc = "explicitly in the server's concept maps, or it is defined implicitly by some code system known to"]
        #[doc = "the server."]
        pub url: Option<FHIRUri>,
        #[doc = "The concept map is provided directly as part of the request. Servers may choose not to accept"]
        #[doc = "concept maps in this fashion."]
        pub conceptMap: Option<ConceptMap>,
        #[doc = "The identifier that is used to identify a specific version of the concept map to be used for the"]
        #[doc = "translation. This is an arbitrary value managed by the concept map author and is not expected to be"]
        #[doc = "globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not"]
        #[doc = "available."]
        pub conceptMapVersion: Option<FHIRString>,
        #[doc = "The code that is to be translated. If a code is provided, a system must be provided"]
        pub code: Option<FHIRCode>,
        #[doc = "The system for the code that is to be translated"]
        pub system: Option<FHIRUri>,
        #[doc = "The version of the system, if one was provided in the source data"]
        pub version: Option<FHIRString>,
        #[doc = "Identifies the value set used when the concept (system/code pair) was chosen. May be a logical id,"]
        #[doc = "or an absolute or relative location. The source value set is an optional parameter because in some"]
        #[doc = "cases, the client cannot know what the source value set is. However, without a source value set, the"]
        #[doc = "server may be unable to safely identify an applicable concept map, and would return an error. For"]
        #[doc = "this reason, a source value set SHOULD always be provided. Note that servers may be able to identify"]
        #[doc = "an appropriate concept map without a source value set if there is a full mapping for the entire code"]
        #[doc = "system in the concept map, or by manual intervention"]
        pub source: Option<FHIRUri>,
        #[doc = "A coding to translate"]
        pub coding: Option<Coding>,
        #[doc = "A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing"]
        #[doc = "translations) as it chooses"]
        pub codeableConcept: Option<CodeableConcept>,
        #[doc = "Identifies the value set in which a translation is sought. May be a logical id, or an absolute or"]
        #[doc = "relative location. If there's no target specified, the server should return all known translations,"]
        #[doc = "along with their source"]
        pub target: Option<FHIRUri>,
        #[doc = "identifies a target code system in which a mapping is sought. This parameter is an alternative to"]
        #[doc = "the target parameter - only one is required. Searching for any translation to a target code system"]
        #[doc = "irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the"]
        #[doc = "discretion of the server to decide when to support this operation"]
        pub targetsystem: Option<FHIRUri>,
        #[doc = "Another element that may help produce the correct mapping"]
        #[parameter_nested]
        pub dependency: Option<Vec<InputDependency>>,
        #[doc = "if this is true, then the operation should return all the codes that might be mapped to this code."]
        #[doc = "This parameter reverses the meaning of the source and target parameters"]
        pub reverse: Option<FHIRBoolean>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputMatchProduct {
        #[doc = "The element for this product"]
        pub element: Option<FHIRUri>,
        #[doc = "The value for this product"]
        pub concept: Option<Coding>,
    }
    impl From<OutputMatchProduct> for Resource {
        fn from(value: OutputMatchProduct) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct OutputMatch {
        #[doc = "A code indicating the equivalence of the translation, using values from"]
        #[doc = "[`ConceptMapEquivalence`](valueset-concept-map-equivalence.html)"]
        pub equivalence: Option<FHIRCode>,
        #[doc = "The translation outcome. Note that this would never have userSelected = true, since the process of"]
        #[doc = "translations implies that the user is not selecting the code (and only the client could know"]
        #[doc = "differently)"]
        pub concept: Option<Coding>,
        #[doc = "Another element that is the product of this mapping"]
        #[parameter_nested]
        pub product: Option<Vec<OutputMatchProduct>>,
        #[doc = "The canonical reference to the concept map from which this mapping comes from"]
        pub source: Option<FHIRUri>,
    }
    impl From<OutputMatch> for Resource {
        fn from(value: OutputMatch) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "True if the concept could be translated successfully. The value can only be true if at least one"]
        #[doc = "returned match has an equivalence which is not unmatched or disjoint"]
        pub result: FHIRBoolean,
        #[doc = "Error details, for display to a human. If this is provided when result = true, the message carries"]
        #[doc = "hints and warnings (e.g. a note that the matches could be improved by providing additional detail)"]
        pub message: Option<FHIRString>,
        #[doc = "A concept in the target value set with an equivalence. Note that there may be multiple matches of"]
        #[doc = "equal or differing equivalence, and the matches may include equivalence values that mean that there"]
        #[doc = "is no match"]
        #[parameter_rename = "match"]
        #[parameter_nested]
        pub match_: Option<Vec<OutputMatch>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation is used to submit an `EligibilityRequest` for assessment either as a single"]
#[doc = "`EligibilityRequest` resource instance or as a Bundle containing the `EligibilityRequest` and other"]
#[doc = "referenced resources, or Bundle containing a batch of `EligibilityRequest` resources, either as"]
#[doc = "single `EligibilityRequests` resources or Bundle resources, for processing. The only input parameter"]
#[doc = "is the single `EligibilityRequest` or Bundle resource and the only output is a single"]
#[doc = "`EligibilityResponse`, Bundle of `EligibilityResponses` or an `OperationOutcome` resource."]
pub mod CoverageEligibilityRequestSubmit {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "submit";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"CoverageEligibilityRequest-submit","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Submit an EligibilityRequest resource for assessment</h2><p>OPERATION: Submit an EligibilityRequest resource for assessment</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/CoverageEligibilityRequest-submit</pre><div><p>This operation is used to submit an EligibilityRequest for assessment either as a single EligibilityRequest resource instance or as a Bundle containing the EligibilityRequest and other referenced resources, or Bundle containing a batch of EligibilityRequest resources, either as single EligibilityRequests resources or Bundle resources, for processing. The only input parameter is the single EligibilityRequest or Bundle resource and the only output is a single EligibilityResponse, Bundle of EligibilityResponses or an OperationOutcome resource.</p>\n</div><p>URL: [base]/CoverageEligibilityRequest/$submit</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>resource</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>An EligibilityRequest resource or Bundle of EligibilityRequests, either as individual EligibilityRequest resources or as Bundles each containing a single EligibilityRequest plus referenced resources.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>An EligibilityResponse resource or Bundle of EligibilityResponse responses, either as individual EligibilityResponse resources or as Bundles each containing a single EligibilityResponse plus referenced resources.</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/CoverageEligibilityRequest-submit","version":"4.0.1","name":"Submit an EligibilityRequest resource for assessment","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to submit an `EligibilityRequest` for assessment either as a single `EligibilityRequest` resource instance or as a Bundle containing the `EligibilityRequest` and other referenced resources, or Bundle containing a batch of `EligibilityRequest` resources, either as single `EligibilityRequests` resources or Bundle resources, for processing. The only input parameter is the single `EligibilityRequest` or Bundle resource and the only output is a single `EligibilityResponse`, Bundle of `EligibilityResponses` or an `OperationOutcome` resource.","code":"submit","resource":["CoverageEligibilityRequest"],"system":false,"type":true,"instance":false,"parameter":[{"name":"resource","use":"in","min":1,"max":"1","documentation":"An `EligibilityRequest` resource or Bundle of `EligibilityRequests`, either as individual `EligibilityRequest` resources or as Bundles each containing a single `EligibilityRequest` plus referenced resources.","type":"Resource"},{"name":"return","use":"out","min":1,"max":"1","documentation":"An `EligibilityResponse` resource or Bundle of `EligibilityResponse` responses, either as individual `EligibilityResponse` resources or as Bundles each containing a single `EligibilityResponse` plus referenced resources.","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "An `EligibilityRequest` resource or Bundle of `EligibilityRequests`, either as individual"]
        #[doc = "`EligibilityRequest` resources or as Bundles each containing a single `EligibilityRequest` plus"]
        #[doc = "referenced resources."]
        pub resource: Resource,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "An `EligibilityResponse` resource or Bundle of `EligibilityResponse` responses, either as individual"]
        #[doc = "`EligibilityResponse` resources or as Bundles each containing a single `EligibilityResponse` plus"]
        #[doc = "referenced resources."]
        #[parameter_rename = "return"]
        pub return_: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation is used to return all the information related to an encounter described in the"]
#[doc = "resource on which this operation is invoked. The response is a bundle of type \"searchset\". At a"]
#[doc = "minimum, the encounter resource itself is returned, along with any other resources that the server"]
#[doc = "has available for the given encounter for the user. The server also returns whatever resources are"]
#[doc = "needed to support the records - e.g. linked practitioners, locations, organizations etc. The"]
#[doc = "principle intended use for this operation is to provide a patient with access to their record, or to"]
#[doc = "allow a client to retrieve everything for an encounter for efficient display). The server SHOULD"]
#[doc = "return all resources it has that: * are included in the encounter compartment for the identified"]
#[doc = "encounter (have a reference to the encounter) * are referenced by the standard extenstion for"]
#[doc = "associating an encounter (where no reference element exists)"]
#[doc = "<`http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter>` * the server believes are"]
#[doc = "relevant to the context of the encounter for any other reason (internally defined/decided) * any"]
#[doc = "resource referenced by the above, including binaries and attachments (to make a more complete"]
#[doc = "package) In the US Realm, at a mimimum, the resources returned SHALL include all the data covered by"]
#[doc = "the meaningful use common data elements (see [DAF](http://hl7.org/fhir/us/daf) for further"]
#[doc = "guidance). Other applicable implementation guides may make additional rules about the information"]
#[doc = "that is returned. Note that for many resources, the exact nature of the link to encounter can be"]
#[doc = "ambiguous (e.g. for a `DiagnosticReport`, is it the encounter when it was initiated, or when it was"]
#[doc = "reported?)"]
pub mod EncounterEverything {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRInstant, FHIRInteger};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "everything";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Encounter-everything","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch Encounter Record</h2><p>OPERATION: Fetch Encounter Record</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Encounter-everything</pre><div><p>This operation is used to return all the information related to an encounter described in the resource on which this operation is invoked. The response is a bundle of type &quot;searchset&quot;. At a minimum, the encounter resource itself is returned, along with any other resources that the server has available for the given encounter for the user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, locations, organizations etc. The principle intended use for this operation is to provide a patient with access to their record, or to allow a client to retrieve everything for an encounter for efficient display).</p>\n<p>The server SHOULD return all resources it has that:</p>\n<ul>\n<li>are included in the encounter compartment for the identified encounter (have a reference to the encounter)</li>\n<li>are referenced by the standard extenstion for associating an encounter (where no reference element exists) http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter</li>\n<li>the server believes are relevant to the context of the encounter for any other reason (internally defined/decided)</li>\n<li>any resource referenced by the above, including binaries and attachments (to make a more complete package)</li>\n</ul>\n<p>In the US Realm, at a mimimum, the resources returned SHALL include all the data covered by the meaningful use common data elements (see <a href=\"http://hl7.org/fhir/us/daf\">DAF</a> for further guidance). Other applicable implementation guides may make additional rules about the information that is returned.   Note that for many resources, the exact nature of the link to encounter can be ambiguous (e.g. for a DiagnosticReport, is it the encounter when it was initiated, or when it was reported?)</p>\n</div><p>URL: [base]/Encounter/[id]/$everything</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>_since</td><td>0..1</td><td><a href=\"datatypes.html#instant\">instant</a></td><td/><td><div><p>Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time</p>\n</div></td></tr><tr><td>IN</td><td>_type</td><td>0..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absense of any specified types, the server returns all resource types</p>\n</div></td></tr><tr><td>IN</td><td>_count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>See discussion below on the utility of paging through the results of the $everything operation</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The bundle type is &quot;searchset&quot;</p>\n</div></td></tr></table><div><p>The key differences between this operation and simply searching the encounter compartment are:</p>\n<ul>\n<li>unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)</li>\n<li>the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones)</li>\n</ul>\n<p>This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment.</p>\n<p>It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single encounter, or determine whether the context has the rights to the nominated encounter, if there is one, or can determine an appropriate list of encouners to provide data for from the context of the request.  If there is no nominated encounter (GET /Encounter/$everything) and the context is not associated with a single encounter record, the actual list of encounters is all encounters that the user associated with the request has access to. In such cases, the server may choose to return an error rather than all the records. Specifying the relationship between the context, a user and encounter records is outside the scope of this specification (though see <a href=\"http://hl7.org/fhir/smart-app-launch\">The Smart App Launch Implementation Guide</a>.</p>\n<p>When this operation is used to access multiple encounter records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made <a href=\"async.html\">asynchronously</a>, and associated with <a href=\"formats.html#bulk\">bulk data formats</a>. Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for <a href=\"http.html#paging\">Searching</a>, using the <a href=\"search.html#count\">_count</a> parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment.</p>\n<p>The _since parameter is provided to support periodic queries to get additional information that has changed about the encounter since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Encounter-everything","version":"4.0.1","name":"Fetch Encounter Record","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to return all the information related to an encounter described in the resource on which this operation is invoked. The response is a bundle of type \"searchset\". At a minimum, the encounter resource itself is returned, along with any other resources that the server has available for the given encounter for the user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, locations, organizations etc. The principle intended use for this operation is to provide a patient with access to their record, or to allow a client to retrieve everything for an encounter for efficient display).\r\rThe server SHOULD return all resources it has that:\r\r* are included in the encounter compartment for the identified encounter (have a reference to the encounter)\r* are referenced by the standard extenstion for associating an encounter (where no reference element exists) <http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter>\r* the server believes are relevant to the context of the encounter for any other reason (internally defined/decided)\r* any resource referenced by the above, including binaries and attachments (to make a more complete package)\r\rIn the US Realm, at a mimimum, the resources returned SHALL include all the data covered by the meaningful use common data elements (see [DAF](http://hl7.org/fhir/us/daf) for further guidance). Other applicable implementation guides may make additional rules about the information that is returned.   Note that for many resources, the exact nature of the link to encounter can be ambiguous (e.g. for a `DiagnosticReport`, is it the encounter when it was initiated, or when it was reported?)","code":"everything","comment":"The key differences between this operation and simply searching the encounter compartment are:  \n\n* unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging) \n* the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones)\n\nThis frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment. \n\nIt is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single encounter, or determine whether the context has the rights to the nominated encounter, if there is one, or can determine an appropriate list of encouners to provide data for from the context of the request.  If there is no nominated encounter (GET /Encounter/$everything) and the context is not associated with a single encounter record, the actual list of encounters is all encounters that the user associated with the request has access to. In such cases, the server may choose to return an error rather than all the records. Specifying the relationship between the context, a user and encounter records is outside the scope of this specification (though see [The Smart App Launch Implementation Guide](http://hl7.org/fhir/smart-app-launch).   \n\nWhen this operation is used to access multiple encounter records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made [asynchronously](async.html), and associated with [bulk data formats](formats.html#bulk). Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for [Searching](http.html#paging), using the [_count](search.html#count) parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment.\n\nThe _since parameter is provided to support periodic queries to get additional information that has changed about the encounter since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.","resource":["Encounter"],"system":false,"type":false,"instance":true,"parameter":[{"name":"_since","use":"in","min":0,"max":"1","documentation":"Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time","type":"instant"},{"name":"_type","use":"in","min":0,"max":"*","documentation":"One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absense of any specified types, the server returns all resource types","type":"code"},{"name":"_count","use":"in","min":0,"max":"1","documentation":"See discussion below on the utility of paging through the results of the $everything operation","type":"integer"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The bundle type is \"searchset\"","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Resources updated after this period will be included in the response. The intent of this parameter"]
        #[doc = "is to allow a client to request only records that have changed since the last request, based on"]
        #[doc = "either the return header time, or or (for asynchronous use), the transaction time"]
        #[parameter_rename = "_since"]
        pub since: Option<FHIRInstant>,
        #[doc = "One or more parameters, each containing one or more comma-delimited FHIR resource types to include"]
        #[doc = "in the return resources. In the absense of any specified types, the server returns all resource"]
        #[doc = "types"]
        #[parameter_rename = "_type"]
        pub type_: Option<Vec<FHIRCode>>,
        #[doc = "See discussion below on the utility of paging through the results of the $everything operation"]
        #[parameter_rename = "_count"]
        pub count: Option<FHIRInteger>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The bundle type is \"searchset\""]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "This operation is used to return all the information related to one or more patients that are part"]
#[doc = "of the group on which this operation is invoked. The response is a bundle of type \"searchset\". At a"]
#[doc = "minimum, the patient resource(s) itself is returned, along with any other resources that the server"]
#[doc = "has that are related to the patient(s), and that are available for the given user. The server also"]
#[doc = "returns whatever resources are needed to support the records - e.g. linked practitioners,"]
#[doc = "medications, locations, organizations etc. The intended use for this operation is for a provider or"]
#[doc = "other user to perform a bulk data download. The server SHOULD return at least all resources that it"]
#[doc = "has that are in the patient compartment for the identified patient(s), and any resource referenced"]
#[doc = "from those, including binaries and attachments. In the US Realm, at a mimimum, the resources"]
#[doc = "returned SHALL include all the data covered by the meaningful use common data elements as defined in"]
#[doc = "[US-Core](http://hl7.org/fhir/us/coref). Other applicable implementation guides may make additional"]
#[doc = "rules about how much information that is returned."]
pub mod GroupEverything {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRDate, FHIRInstant, FHIRInteger};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "everything";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Group-everything","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch a group of Patient Records</h2><p>OPERATION: Fetch a group of Patient Records</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Group-everything</pre><div><p>This operation is used to return all the information related to one or more patients that are part of the group on which this operation is invoked. The response is a bundle of type &quot;searchset&quot;. At a minimum, the patient resource(s) itself is returned, along with any other resources that the server has that are related to the patient(s), and that are available for the given user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, medications, locations, organizations etc.   The intended use for this operation is for a provider or other user to perform a bulk data download.  The server SHOULD return at least all resources that it has that are in the patient compartment for the identified patient(s), and any resource referenced from those, including binaries and attachments. In the US Realm, at a mimimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in <a href=\"http://hl7.org/fhir/us/coref\">US-Core</a>. Other applicable implementation guides may make additional rules about how much information that is returned.</p>\n</div><p>URL: [base]/Group/[id]/$everything</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>start</td><td>0..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all records prior to the end date are in scope.</p>\n</div></td></tr><tr><td>IN</td><td>end</td><td>0..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all records subsequent to the start date are in scope.</p>\n</div></td></tr><tr><td>IN</td><td>_since</td><td>0..1</td><td><a href=\"datatypes.html#instant\">instant</a></td><td/><td><div><p>Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time</p>\n</div></td></tr><tr><td>IN</td><td>_type</td><td>0..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absense of any specified types, the server returns all resource types</p>\n</div></td></tr><tr><td>IN</td><td>_count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>See discussion below on the utility of paging through the results of the $everything operation</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The bundle type is &quot;searchset&quot;</p>\n</div></td></tr></table><div><p>The key differences between this operation and simply searching the group's patients compartment are:</p>\n<ul>\n<li>unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)</li>\n<li>the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones).</li>\n</ul>\n<p>This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources.</p>\n<p>It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a particular group, or determine whether the context has the rights to the nominated group, if there is one, or can determine an appropriate list of groups to provide data for from the context of the request.   If there is no nominated group (GET /Group/$everything) and the context is not associated with a single group record, the actual list of groups is all groups that the user associated with the request has access to. In such cases, the server may choose to return an error rather than all the records (and is likely to do so, but not required to).  Specifying the relationship between the context, a user and groups is outside the scope of this specification (though see <a href=\"http://hl7.org/fhir/smart-app-launch\">The Smart App Launch Implementation Guide</a>.</p>\n<p>The return bundle from this operation is usually rather a lot of data; servers typically choose to require that such requests are made <a href=\"async.html\">asynchronously</a>, and associated with <a href=\"formats.html#bulk\">bulk data formats</a>. Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for <a href=\"http.html#paging\">Searching</a>, using the <a href=\"search.html#count\">_count</a> parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.</p>\n<p>The _since parameter is provided to support periodic queries to get additional information that has changed about the group since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Group-everything","version":"4.0.1","name":"Fetch a group of Patient Records","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to return all the information related to one or more patients that are part of the group on which this operation is invoked. The response is a bundle of type \"searchset\". At a minimum, the patient resource(s) itself is returned, along with any other resources that the server has that are related to the patient(s), and that are available for the given user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, medications, locations, organizations etc.   The intended use for this operation is for a provider or other user to perform a bulk data download.  The server SHOULD return at least all resources that it has that are in the patient compartment for the identified patient(s), and any resource referenced from those, including binaries and attachments. In the US Realm, at a mimimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in [US-Core](http://hl7.org/fhir/us/coref). Other applicable implementation guides may make additional rules about how much information that is returned.","code":"everything","comment":"The key differences between this operation and simply searching the group's patients compartment are:    \n\n* unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)  \n* the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones). \n\nThis frees the client from needing to determine what it could or should ask for, particularly with regard to included resources.  \n\nIt is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a particular group, or determine whether the context has the rights to the nominated group, if there is one, or can determine an appropriate list of groups to provide data for from the context of the request.   If there is no nominated group (GET /Group/$everything) and the context is not associated with a single group record, the actual list of groups is all groups that the user associated with the request has access to. In such cases, the server may choose to return an error rather than all the records (and is likely to do so, but not required to).  Specifying the relationship between the context, a user and groups is outside the scope of this specification (though see [The Smart App Launch Implementation Guide](http://hl7.org/fhir/smart-app-launch). \n\nThe return bundle from this operation is usually rather a lot of data; servers typically choose to require that such requests are made [asynchronously](async.html), and associated with [bulk data formats](formats.html#bulk). Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for [Searching](http.html#paging), using the [_count](search.html#count) parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.\n\nThe _since parameter is provided to support periodic queries to get additional information that has changed about the group since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.","resource":["Group"],"system":false,"type":false,"instance":true,"parameter":[{"name":"start","use":"in","min":0,"max":"1","documentation":"The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all records prior to the end date are in scope.","type":"date"},{"name":"end","use":"in","min":0,"max":"1","documentation":"The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all records subsequent to the start date are in scope.","type":"date"},{"name":"_since","use":"in","min":0,"max":"1","documentation":"Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time","type":"instant"},{"name":"_type","use":"in","min":0,"max":"*","documentation":"One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absense of any specified types, the server returns all resource types","type":"code"},{"name":"_count","use":"in","min":0,"max":"1","documentation":"See discussion below on the utility of paging through the results of the $everything operation","type":"integer"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The bundle type is \"searchset\"","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The date range relates to care dates, not record currency dates - e.g. all records relating to care"]
        #[doc = "provided in a certain date range. If no start date is provided, all records prior to the end date"]
        #[doc = "are in scope."]
        pub start: Option<FHIRDate>,
        #[doc = "The date range relates to care dates, not record currency dates - e.g. all records relating to care"]
        #[doc = "provided in a certain date range. If no end date is provided, all records subsequent to the start"]
        #[doc = "date are in scope."]
        pub end: Option<FHIRDate>,
        #[doc = "Resources updated after this period will be included in the response. The intent of this parameter"]
        #[doc = "is to allow a client to request only records that have changed since the last request, based on"]
        #[doc = "either the return header time, or or (for asynchronous use), the transaction time"]
        #[parameter_rename = "_since"]
        pub since: Option<FHIRInstant>,
        #[doc = "One or more parameters, each containing one or more comma-delimited FHIR resource types to include"]
        #[doc = "in the return resources. In the absense of any specified types, the server returns all resource"]
        #[doc = "types"]
        #[parameter_rename = "_type"]
        pub type_: Option<Vec<FHIRCode>>,
        #[doc = "See discussion below on the utility of paging through the results of the $everything operation"]
        #[parameter_rename = "_count"]
        pub count: Option<FHIRInteger>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The bundle type is \"searchset\""]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "The data-requirements operation aggregates and returns the parameters and data requirements for a"]
#[doc = "resource and all its dependencies as a single module definition"]
pub mod LibraryDataRequirements {
    use haste_fhir_model::r4::generated::resources::{
        Library, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "data-requirements";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Library-data-requirements","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Data Requirements</h2><p>OPERATION: Data Requirements</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Library-data-requirements</pre><div><p>The data-requirements operation aggregates and returns the parameters and data requirements for a resource and all its dependencies as a single module definition</p>\n</div><p>URL: [base]/$data-requirements</p><p>URL: [base]/Library/[id]/$data-requirements</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>target</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The target of the data requirements operation</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"library.html\">Library</a></td><td/><td><div><p>The result of the requirements gathering</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for a given target resource. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the target resource and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Library-data-requirements","version":"4.0.1","name":"Data Requirements","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The data-requirements operation aggregates and returns the parameters and data requirements for a resource and all its dependencies as a single module definition","code":"data-requirements","comment":"The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for a given target resource. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the target resource and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)","resource":["Library"],"system":true,"type":false,"instance":true,"parameter":[{"name":"target","use":"in","min":0,"max":"1","documentation":"The target of the data requirements operation","type":"string"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the requirements gathering","type":"Library"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The target of the data requirements operation"]
        pub target: Option<FHIRString>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the requirements gathering"]
        #[parameter_rename = "return"]
        pub return_: Library,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Library(value.return_)
        }
    }
}
#[doc = "This operation allows a client to find an identified list for a particular function by its function."]
#[doc = "The operation takes two parameters, the identity of a patient, and the name of a functional list."]
#[doc = "The list of defined functional lists can be found at [`Current Resource"]
#[doc = "Lists`](lifecycle.html#lists). Applications are not required to support all the lists, and may"]
#[doc = "define additional lists of their own. If the system is able to locate a list that serves the"]
#[doc = "identified purpose, it returns it as the body of the response with a 200 OK status. If the resource"]
#[doc = "cannot be located, the server returns a 404 not found (optionally with an `OperationOutcome`"]
#[doc = "resource)"]
pub mod ListFind {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRId};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "find";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"List-find","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Find a functional list</h2><p>OPERATION: Find a functional list</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/List-find</pre><div><p>This operation allows a client to find an identified list for a particular function by its function. The operation takes two parameters, the identity of a patient, and the name of a functional list.     The list of defined functional lists can be found at <a href=\"lifecycle.html#lists\">Current Resource Lists</a>. Applications are not required to support all the lists, and may define additional lists of their own.   If the system is able to locate a list that serves the identified purpose, it returns it as the body of the response with a 200 OK status. If the resource cannot be located, the server returns a 404 not found (optionally with an OperationOutcome resource)</p>\n</div><p>URL: [base]/List/$find</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>patient</td><td>1..1</td><td><a href=\"datatypes.html#id\">id</a></td><td/><td><div><p>The id of a patient resource located on the server on which this operation is executed</p>\n</div></td></tr><tr><td>IN</td><td>name</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The code for the functional list that is being found</p>\n</div></td></tr></table><div><p>Note that servers may support searching by a functional list, and not support this operation that allows clients to find the list directly</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/List-find","version":"4.0.1","name":"Find a functional list","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation allows a client to find an identified list for a particular function by its function. The operation takes two parameters, the identity of a patient, and the name of a functional list.     The list of defined functional lists can be found at [Current Resource Lists](lifecycle.html#lists). Applications are not required to support all the lists, and may define additional lists of their own.   If the system is able to locate a list that serves the identified purpose, it returns it as the body of the response with a 200 OK status. If the resource cannot be located, the server returns a 404 not found (optionally with an `OperationOutcome` resource)","code":"find","comment":"Note that servers may support searching by a functional list, and not support this operation that allows clients to find the list directly","resource":["List"],"system":false,"type":true,"instance":false,"parameter":[{"name":"patient","use":"in","min":1,"max":"1","documentation":"The id of a patient resource located on the server on which this operation is executed","type":"id"},{"name":"name","use":"in","min":1,"max":"1","documentation":"The code for the functional list that is being found","type":"code"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The id of a patient resource located on the server on which this operation is executed"]
        pub patient: FHIRId,
        #[doc = "The code for the functional list that is being found"]
        pub name: FHIRCode,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {}
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The care-gaps operation is used to determine gaps-in-care based on the results of quality measures"]
pub mod MeasureCareGaps {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRDate, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "care-gaps";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Measure-care-gaps","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Care Gaps</h2><p>OPERATION: Care Gaps</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Measure-care-gaps</pre><div><p>The care-gaps operation is used to determine gaps-in-care based on the results of quality measures</p>\n</div><p>URL: [base]/Measure/$care-gaps</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>periodStart</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period s</p>\n</div></td></tr><tr><td>IN</td><td>periodEnd</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive</p>\n</div></td></tr><tr><td>IN</td><td>topic</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The topic to be used to determine which measures are considered for the care gaps report. Any measure with the given topic will be included in the report</p>\n</div></td></tr><tr><td>IN</td><td>subject</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>Subject for which the care gaps report will be produced</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The result of the care gaps report will be returned as a document bundle with a MeasureReport entry for each included measure</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to calculate a set of measures for a particular topic (e.g. Preventive Care and Screening) and return a document describing the results of each measure for the given subject. Note that it is up to the server to determine whether or not the generated care gaps report is persisted. If the server does not persist the results, the operation does not affect state and can be invoked with a GET</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Measure-care-gaps","version":"4.0.1","name":"Care Gaps","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The care-gaps operation is used to determine gaps-in-care based on the results of quality measures","code":"care-gaps","comment":"The effect of invoking this operation is to calculate a set of measures for a particular topic (e.g. Preventive Care and Screening) and return a document describing the results of each measure for the given subject. Note that it is up to the server to determine whether or not the generated care gaps report is persisted. If the server does not persist the results, the operation does not affect state and can be invoked with a GET","resource":["Measure"],"system":false,"type":true,"instance":false,"parameter":[{"name":"periodStart","use":"in","min":1,"max":"1","documentation":"The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period s","type":"date"},{"name":"periodEnd","use":"in","min":1,"max":"1","documentation":"The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive","type":"date"},{"name":"topic","use":"in","min":1,"max":"1","documentation":"The topic to be used to determine which measures are considered for the care gaps report. Any measure with the given topic will be included in the report","type":"string"},{"name":"subject","use":"in","min":1,"max":"1","documentation":"Subject for which the care gaps report will be produced","type":"string","searchType":"reference"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the care gaps report will be returned as a document bundle with a `MeasureReport` entry for each included measure","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The start of the measurement period. In keeping with the semantics of the date parameter used in the"]
        #[doc = "FHIR search operation, the period will start at the beginning of the period implied by the supplied"]
        #[doc = "timestamp. E.g. a value of 2014 would set the period s"]
        pub periodStart: FHIRDate,
        #[doc = "The end of the measurement period. The period will end at the end of the period implied by the"]
        #[doc = "supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59"]
        #[doc = "inclusive"]
        pub periodEnd: FHIRDate,
        #[doc = "The topic to be used to determine which measures are considered for the care gaps report. Any"]
        #[doc = "measure with the given topic will be included in the report"]
        pub topic: FHIRString,
        #[doc = "Subject for which the care gaps report will be produced"]
        pub subject: FHIRString,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the care gaps report will be returned as a document bundle with a `MeasureReport`"]
        #[doc = "entry for each included measure"]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "The collect-data operation is used to collect the data-of-interest for the given measure."]
pub mod MeasureCollectData {
    use haste_fhir_model::r4::generated::resources::{
        MeasureReport, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRDate, FHIRDateTime, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "collect-data";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Measure-collect-data","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Collect Data</h2><p>OPERATION: Collect Data</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Measure-collect-data</pre><div><p>The collect-data operation is used to collect the data-of-interest for the given measure.</p>\n</div><p>URL: [base]/Measure/$collect-data</p><p>URL: [base]/Measure/[id]/$collect-data</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>periodStart</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period s</p>\n</div></td></tr><tr><td>IN</td><td>periodEnd</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive</p>\n</div></td></tr><tr><td>IN</td><td>measure</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The measure to evaluate. This parameter is only required when the operation is invoked on the resource type, it is not used when invoking the operation on a Measure instance</p>\n</div></td></tr><tr><td>IN</td><td>subject</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>Subject for which the measure will be collected. If not specified, measure data will be collected for all subjects that meet the requirements of the measure. If specified, the measure will only be calculated for the referenced subject(s)</p>\n</div></td></tr><tr><td>IN</td><td>practitioner</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>Practitioner for which the measure will be collected. If specified, measure data will be collected only for subjects that have a primary relationship to the identified practitioner</p>\n</div></td></tr><tr><td>IN</td><td>lastReceivedOn</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date the results of this measure were last received. This parameter used to indicate when the last time data for this measure was collected. This information is used to support incremental data collection scenarios</p>\n</div></td></tr><tr><td>OUT</td><td>measureReport</td><td>1..1</td><td><a href=\"measurereport.html\">MeasureReport</a></td><td/><td><div><p>A MeasureReport of type data-collection detailing the results of the operation</p>\n</div></td></tr><tr><td>OUT</td><td>resource</td><td>0..*</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The result resources that make up the data-of-interest for the measure</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to gather the data required to perform an evaluation of the measure. If the lastReceivedOn parameter is supplied, only data that is new or has been changed since the lastReceivedOn date is included in the response. Note that the resulting MeasureReport is a transient resource</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Measure-collect-data","version":"4.0.1","name":"Collect Data","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The collect-data operation is used to collect the data-of-interest for the given measure.","code":"collect-data","comment":"The effect of invoking this operation is to gather the data required to perform an evaluation of the measure. If the lastReceivedOn parameter is supplied, only data that is new or has been changed since the lastReceivedOn date is included in the response. Note that the resulting MeasureReport is a transient resource","resource":["Measure"],"system":false,"type":true,"instance":true,"parameter":[{"name":"periodStart","use":"in","min":1,"max":"1","documentation":"The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period s","type":"date"},{"name":"periodEnd","use":"in","min":1,"max":"1","documentation":"The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive","type":"date"},{"name":"measure","use":"in","min":0,"max":"1","documentation":"The measure to evaluate. This parameter is only required when the operation is invoked on the resource type, it is not used when invoking the operation on a Measure instance","type":"string","searchType":"reference"},{"name":"subject","use":"in","min":0,"max":"1","documentation":"Subject for which the measure will be collected. If not specified, measure data will be collected for all subjects that meet the requirements of the measure. If specified, the measure will only be calculated for the referenced subject(s)","type":"string","searchType":"reference"},{"name":"practitioner","use":"in","min":0,"max":"1","documentation":"Practitioner for which the measure will be collected. If specified, measure data will be collected only for subjects that have a primary relationship to the identified practitioner","type":"string","searchType":"reference"},{"name":"lastReceivedOn","use":"in","min":0,"max":"1","documentation":"The date the results of this measure were last received. This parameter used to indicate when the last time data for this measure was collected. This information is used to support incremental data collection scenarios","type":"dateTime"},{"name":"measureReport","use":"out","min":1,"max":"1","documentation":"A `MeasureReport` of type data-collection detailing the results of the operation","type":"MeasureReport"},{"name":"resource","use":"out","min":0,"max":"*","documentation":"The result resources that make up the data-of-interest for the measure","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The start of the measurement period. In keeping with the semantics of the date parameter used in the"]
        #[doc = "FHIR search operation, the period will start at the beginning of the period implied by the supplied"]
        #[doc = "timestamp. E.g. a value of 2014 would set the period s"]
        pub periodStart: FHIRDate,
        #[doc = "The end of the measurement period. The period will end at the end of the period implied by the"]
        #[doc = "supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59"]
        #[doc = "inclusive"]
        pub periodEnd: FHIRDate,
        #[doc = "The measure to evaluate. This parameter is only required when the operation is invoked on the"]
        #[doc = "resource type, it is not used when invoking the operation on a Measure instance"]
        pub measure: Option<FHIRString>,
        #[doc = "Subject for which the measure will be collected. If not specified, measure data will be collected"]
        #[doc = "for all subjects that meet the requirements of the measure. If specified, the measure will only be"]
        #[doc = "calculated for the referenced subject(s)"]
        pub subject: Option<FHIRString>,
        #[doc = "Practitioner for which the measure will be collected. If specified, measure data will be collected"]
        #[doc = "only for subjects that have a primary relationship to the identified practitioner"]
        pub practitioner: Option<FHIRString>,
        #[doc = "The date the results of this measure were last received. This parameter used to indicate when the"]
        #[doc = "last time data for this measure was collected. This information is used to support incremental data"]
        #[doc = "collection scenarios"]
        pub lastReceivedOn: Option<FHIRDateTime>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "A `MeasureReport` of type data-collection detailing the results of the operation"]
        pub measureReport: MeasureReport,
        #[doc = "The result resources that make up the data-of-interest for the measure"]
        pub resource: Option<Vec<Resource>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The data-requirements operation aggregates and returns the parameters and data requirements for the"]
#[doc = "measure and all its dependencies as a single module definition"]
pub mod MeasureDataRequirements {
    use haste_fhir_model::r4::generated::resources::{
        Library, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRDate;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "data-requirements";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Measure-data-requirements","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Data Requirements</h2><p>OPERATION: Data Requirements</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Measure-data-requirements</pre><div><p>The data-requirements operation aggregates and returns the parameters and data requirements for the measure and all its dependencies as a single module definition</p>\n</div><p>URL: [base]/Measure/[id]/$data-requirements</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>periodStart</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive</p>\n</div></td></tr><tr><td>IN</td><td>periodEnd</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"library.html\">Library</a></td><td/><td><div><p>The result of the requirements gathering is a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the measure</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the measure. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the libraries referenced by the measures. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements). This operation defines what resources are subsequently referenced in the evaluatedResources element of the MeasureReport when submitting measure data</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Measure-data-requirements","version":"4.0.1","name":"Data Requirements","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The data-requirements operation aggregates and returns the parameters and data requirements for the measure and all its dependencies as a single module definition","code":"data-requirements","comment":"The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the measure. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the libraries referenced by the measures. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements). This operation defines what resources are subsequently referenced in the evaluatedResources element of the MeasureReport when submitting measure data","resource":["Measure"],"system":false,"type":false,"instance":true,"parameter":[{"name":"periodStart","use":"in","min":1,"max":"1","documentation":"The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive","type":"date"},{"name":"periodEnd","use":"in","min":1,"max":"1","documentation":"The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive","type":"date"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the requirements gathering is a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the measure","type":"Library"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The start of the measurement period. In keeping with the semantics of the date parameter used in the"]
        #[doc = "FHIR search operation, the period will start at the beginning of the period implied by the supplied"]
        #[doc = "timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive"]
        pub periodStart: FHIRDate,
        #[doc = "The end of the measurement period. The period will end at the end of the period implied by the"]
        #[doc = "supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59"]
        #[doc = "inclusive"]
        pub periodEnd: FHIRDate,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the requirements gathering is a module-definition Library that describes the aggregate"]
        #[doc = "parameters, data requirements, and dependencies of the measure"]
        #[parameter_rename = "return"]
        pub return_: Library,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Library(value.return_)
        }
    }
}
#[doc = "The evaluate-measure operation is used to calculate an eMeasure and obtain the results"]
pub mod MeasureEvaluateMeasure {
    use haste_fhir_model::r4::generated::resources::{
        MeasureReport, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRDate, FHIRDateTime, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "evaluate-measure";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Measure-evaluate-measure","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Evaluate Measure</h2><p>OPERATION: Evaluate Measure</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Measure-evaluate-measure</pre><div><p>The evaluate-measure operation is used to calculate an eMeasure and obtain the results</p>\n</div><p>URL: [base]/Measure/$evaluate-measure</p><p>URL: [base]/Measure/[id]/$evaluate-measure</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>periodStart</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive</p>\n</div></td></tr><tr><td>IN</td><td>periodEnd</td><td>1..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive</p>\n</div></td></tr><tr><td>IN</td><td>measure</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The measure to evaluate. This parameter is only required when the operation is invoked on the resource type, it is not used when invoking the operation on a Measure instance</p>\n</div></td></tr><tr><td>IN</td><td>reportType</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The type of measure report: subject, subject-list, or population. If not specified, a default value of subject will be used if the subject parameter is supplied, otherwise, population will be used</p>\n</div></td></tr><tr><td>IN</td><td>subject</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>Subject for which the measure will be calculated. If not specified, the measure will be calculated for all subjects that meet the requirements of the measure. If specified, the measure will only be calculated for the referenced subject(s)</p>\n</div></td></tr><tr><td>IN</td><td>practitioner</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>Practitioner for which the measure will be calculated. If specified, the measure will be calculated only for subjects that have a primary relationship to the identified practitioner</p>\n</div></td></tr><tr><td>IN</td><td>lastReceivedOn</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date the results of this measure were last received. This parameter is only valid for patient-level reports and is used to indicate when the last time a result for this patient was received. This information can be used to limit the set of resources returned for a patient-level report</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"measurereport.html\">MeasureReport</a></td><td/><td><div><p>The results of the measure calculation. See the MeasureReport resource for a complete description of the output of this operation. Note that implementations may choose to return a MeasureReport with a status of pending to indicate that the report is still being generated. In this case, the client can use a polling method to continually request the MeasureReport until the status is updated to complete</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to calculate the measure for the given subject, or all subjects if no subject is supplied, and return the results as a MeasureReport resource of the appropriate type. Note that whether or not this operation affects the state of the server depends on whether the server persists the generated MeasureReport. If the MeasureReport is not persisted, this operation can be invoked with GET</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Measure-evaluate-measure","version":"4.0.1","name":"Evaluate Measure","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The evaluate-measure operation is used to calculate an eMeasure and obtain the results","code":"evaluate-measure","comment":"The effect of invoking this operation is to calculate the measure for the given subject, or all subjects if no subject is supplied, and return the results as a MeasureReport resource of the appropriate type. Note that whether or not this operation affects the state of the server depends on whether the server persists the generated MeasureReport. If the MeasureReport is not persisted, this operation can be invoked with GET","resource":["Measure"],"system":false,"type":true,"instance":true,"parameter":[{"name":"periodStart","use":"in","min":1,"max":"1","documentation":"The start of the measurement period. In keeping with the semantics of the date parameter used in the FHIR search operation, the period will start at the beginning of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive","type":"date"},{"name":"periodEnd","use":"in","min":1,"max":"1","documentation":"The end of the measurement period. The period will end at the end of the period implied by the supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59 inclusive","type":"date"},{"name":"measure","use":"in","min":0,"max":"1","documentation":"The measure to evaluate. This parameter is only required when the operation is invoked on the resource type, it is not used when invoking the operation on a Measure instance","type":"string","searchType":"reference"},{"name":"reportType","use":"in","min":0,"max":"1","documentation":"The type of measure report: subject, subject-list, or population. If not specified, a default value of subject will be used if the subject parameter is supplied, otherwise, population will be used","type":"code"},{"name":"subject","use":"in","min":0,"max":"1","documentation":"Subject for which the measure will be calculated. If not specified, the measure will be calculated for all subjects that meet the requirements of the measure. If specified, the measure will only be calculated for the referenced subject(s)","type":"string","searchType":"reference"},{"name":"practitioner","use":"in","min":0,"max":"1","documentation":"Practitioner for which the measure will be calculated. If specified, the measure will be calculated only for subjects that have a primary relationship to the identified practitioner","type":"string","searchType":"reference"},{"name":"lastReceivedOn","use":"in","min":0,"max":"1","documentation":"The date the results of this measure were last received. This parameter is only valid for patient-level reports and is used to indicate when the last time a result for this patient was received. This information can be used to limit the set of resources returned for a patient-level report","type":"dateTime"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The results of the measure calculation. See the `MeasureReport` resource for a complete description of the output of this operation. Note that implementations may choose to return a `MeasureReport` with a status of pending to indicate that the report is still being generated. In this case, the client can use a polling method to continually request the `MeasureReport` until the status is updated to complete","type":"MeasureReport"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The start of the measurement period. In keeping with the semantics of the date parameter used in the"]
        #[doc = "FHIR search operation, the period will start at the beginning of the period implied by the supplied"]
        #[doc = "timestamp. E.g. a value of 2014 would set the period start to be 2014-01-01T00:00:00 inclusive"]
        pub periodStart: FHIRDate,
        #[doc = "The end of the measurement period. The period will end at the end of the period implied by the"]
        #[doc = "supplied timestamp. E.g. a value of 2014 would set the period end to be 2014-12-31T23:59:59"]
        #[doc = "inclusive"]
        pub periodEnd: FHIRDate,
        #[doc = "The measure to evaluate. This parameter is only required when the operation is invoked on the"]
        #[doc = "resource type, it is not used when invoking the operation on a Measure instance"]
        pub measure: Option<FHIRString>,
        #[doc = "The type of measure report: subject, subject-list, or population. If not specified, a default value"]
        #[doc = "of subject will be used if the subject parameter is supplied, otherwise, population will be used"]
        pub reportType: Option<FHIRCode>,
        #[doc = "Subject for which the measure will be calculated. If not specified, the measure will be calculated"]
        #[doc = "for all subjects that meet the requirements of the measure. If specified, the measure will only be"]
        #[doc = "calculated for the referenced subject(s)"]
        pub subject: Option<FHIRString>,
        #[doc = "Practitioner for which the measure will be calculated. If specified, the measure will be calculated"]
        #[doc = "only for subjects that have a primary relationship to the identified practitioner"]
        pub practitioner: Option<FHIRString>,
        #[doc = "The date the results of this measure were last received. This parameter is only valid for"]
        #[doc = "patient-level reports and is used to indicate when the last time a result for this patient was"]
        #[doc = "received. This information can be used to limit the set of resources returned for a patient-level"]
        #[doc = "report"]
        pub lastReceivedOn: Option<FHIRDateTime>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The results of the measure calculation. See the `MeasureReport` resource for a complete description"]
        #[doc = "of the output of this operation. Note that implementations may choose to return a `MeasureReport`"]
        #[doc = "with a status of pending to indicate that the report is still being generated. In this case, the"]
        #[doc = "client can use a polling method to continually request the `MeasureReport` until the status is"]
        #[doc = "updated to complete"]
        #[parameter_rename = "return"]
        pub return_: MeasureReport,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::MeasureReport(value.return_)
        }
    }
}
#[doc = "The submit-data operation is used to submit data-of-interest for a measure. There is no expectation"]
#[doc = "that the submitted data represents all the data-of-interest, only that all the data submitted is"]
#[doc = "relevant to the calculation of the measure for a particular subject or population"]
pub mod MeasureSubmitData {
    use haste_fhir_model::r4::generated::resources::{
        MeasureReport, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "submit-data";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Measure-submit-data","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Submit Data</h2><p>OPERATION: Submit Data</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Measure-submit-data</pre><div><p>The submit-data operation is used to submit data-of-interest for a measure. There is no expectation that the submitted data represents all the data-of-interest, only that all the data submitted is relevant to the calculation of the measure for a particular subject or population</p>\n</div><p>URL: [base]/Measure/$submit-data</p><p>URL: [base]/Measure/[id]/$submit-data</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>measureReport</td><td>1..1</td><td><a href=\"measurereport.html\">MeasureReport</a></td><td/><td><div><p>The measure report being submitted</p>\n</div></td></tr><tr><td>IN</td><td>resource</td><td>0..*</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The individual resources that make up the data-of-interest being submitted</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is that the submitted data is posted to the receiving system and can be used for subsequent calculation of the relevant quality measure. The data-of-interest for a measure can be determined by examining the measure definition, or by invoking the $data-requirements operation</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Measure-submit-data","version":"4.0.1","name":"Submit Data","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The submit-data operation is used to submit data-of-interest for a measure. There is no expectation that the submitted data represents all the data-of-interest, only that all the data submitted is relevant to the calculation of the measure for a particular subject or population","code":"submit-data","comment":"The effect of invoking this operation is that the submitted data is posted to the receiving system and can be used for subsequent calculation of the relevant quality measure. The data-of-interest for a measure can be determined by examining the measure definition, or by invoking the $data-requirements operation","resource":["Measure"],"system":false,"type":true,"instance":true,"parameter":[{"name":"measureReport","use":"in","min":1,"max":"1","documentation":"The measure report being submitted","type":"MeasureReport"},{"name":"resource","use":"in","min":0,"max":"*","documentation":"The individual resources that make up the data-of-interest being submitted","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The measure report being submitted"]
        pub measureReport: MeasureReport,
        #[doc = "The individual resources that make up the data-of-interest being submitted"]
        pub resource: Option<Vec<Resource>>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {}
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation is used to return all the information related to one or more products described in"]
#[doc = "the resource or context on which this operation is invoked. The response is a bundle of type"]
#[doc = "\"searchset\". At a minimum, the product resource(s) itself is returned, along with any other"]
#[doc = "resources that the server has that are related to the products(s), and that are available for the"]
#[doc = "given user. This is typically the marketing authorisations, ingredients, packages, therapeutic"]
#[doc = "indications and so on. The server also returns whatever resources are needed to support the records"]
#[doc = "- e.g. linked organizations, document references etc."]
pub mod MedicinalProductEverything {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRInstant, FHIRInteger};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "everything";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"MedicinalProduct-everything","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch Product Record</h2><p>OPERATION: Fetch Product Record</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/MedicinalProduct-everything</pre><div><p>This operation is used to return all the information related to one or more products described in the resource or context on which this operation is invoked. The response is a bundle of type &quot;searchset&quot;. At a minimum, the product resource(s) itself is returned, along with any other resources that the server has that are related to the products(s), and that are available for the given user. This is typically the marketing authorisations, ingredients, packages, therapeutic indications and so on. The server also returns whatever resources are needed to support the records - e.g. linked organizations, document references etc.</p>\n</div><p>URL: [base]/MedicinalProduct/$everything</p><p>URL: [base]/MedicinalProduct/[id]/$everything</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>_since</td><td>0..1</td><td><a href=\"datatypes.html#instant\">instant</a></td><td/><td><div><p>Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time</p>\n</div></td></tr><tr><td>IN</td><td>_count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>See discussion below on the utility of paging through the results of the $everything operation</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The bundle type is &quot;searchset&quot;</p>\n</div></td></tr></table><div><p>The key differences between this operation and simply performing a search and using _include and _revinclude are:</p>\n<ul>\n<li>unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)</li>\n<li>the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones).</li>\n</ul>\n<p>This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. It also makes for a much shorter and easier to construct query string. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the product data.</p>\n<p>When this operation is used to access multiple product records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made <a href=\"async.html\">asynchronously</a>, and associated with <a href=\"formats.html#bulk\">bulk data formats</a>. Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for <a href=\"http.html#paging\">Searching</a>, using the <a href=\"search.html#count\">_count</a> parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.</p>\n<p>The _since parameter is provided to support periodic queries to get additional information that has changed about the product since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":0},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/MedicinalProduct-everything","version":"4.0.1","name":"Fetch Product Record","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to return all the information related to one or more products described in the resource or context on which this operation is invoked. The response is a bundle of type \"searchset\". At a minimum, the product resource(s) itself is returned, along with any other resources that the server has that are related to the products(s), and that are available for the given user. This is typically the marketing authorisations, ingredients, packages, therapeutic indications and so on. The server also returns whatever resources are needed to support the records - e.g. linked organizations, document references etc.","code":"everything","comment":"The key differences between this operation and simply performing a search and using _include and _revinclude are:    \n\n* unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)  \n* the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones). \n\nThis frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. It also makes for a much shorter and easier to construct query string. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the product data. \n\nWhen this operation is used to access multiple product records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made [asynchronously](async.html), and associated with [bulk data formats](formats.html#bulk). Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for [Searching](http.html#paging), using the [_count](search.html#count) parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.\n\nThe _since parameter is provided to support periodic queries to get additional information that has changed about the product since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.","resource":["MedicinalProduct"],"system":false,"type":true,"instance":true,"parameter":[{"name":"_since","use":"in","min":0,"max":"1","documentation":"Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time","type":"instant"},{"name":"_count","use":"in","min":0,"max":"1","documentation":"See discussion below on the utility of paging through the results of the $everything operation","type":"integer"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The bundle type is \"searchset\"","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Resources updated after this period will be included in the response. The intent of this parameter"]
        #[doc = "is to allow a client to request only records that have changed since the last request, based on"]
        #[doc = "either the return header time, or or (for asynchronous use), the transaction time"]
        #[parameter_rename = "_since"]
        pub since: Option<FHIRInstant>,
        #[doc = "See discussion below on the utility of paging through the results of the $everything operation"]
        #[parameter_rename = "_count"]
        pub count: Option<FHIRInteger>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The bundle type is \"searchset\""]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "This operation accepts a message, processes it according to the definition of the event in the"]
#[doc = "message header, and returns one or more response messages."]
#[doc = ""]
#[doc = "In addition to processing the message event, a server may choose to retain all or some the resources"]
#[doc = "and make them available on a `RESTful` interface, but is not required to do so."]
pub mod MessageHeaderProcessMessage {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRBoolean, FHIRUrl};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "process-message";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"MessageHeader-process-message","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Process Message</h2><p>OPERATION: Process Message</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message</pre><div><p>This operation accepts a message, processes it according to the definition of the event in the message header, and returns one or more response messages.</p>\n<p>In addition to processing the message event, a server may choose to retain all or some the resources and make them available on a RESTful interface, but is not required to do so.</p>\n</div><p>URL: [base]/$process-message</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>content</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The message to process (or, if using asynchronous messaging, it may be a response message to accept)</p>\n</div></td></tr><tr><td>IN</td><td>async</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>If 'true' the message is processed using the asynchronous messaging pattern</p>\n</div></td></tr><tr><td>IN</td><td>response-url</td><td>0..1</td><td><a href=\"datatypes.html#url\">url</a></td><td/><td><div><p>A URL to submit response messages to, if asynchronous messaging is being used, and if the MessageHeader.source.endpoint is not the appropriate place to submit responses</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>0..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value</p>\n</div></td></tr></table><div><p>This operation does not use the parameters resource; the parameters &quot;async&quot; and &quot;response-url&quot; always go in the URL, if they are used, and the &quot;content&quot; parameter is always the body of the HTTP message.</p>\n<p>When processing messages, a server may return one of several status codes:</p>\n<ul>\n<li><strong>200 OK</strong>: Indicates that the message has been fully processed.  If an application-level response is expected for the submitted message, that response SHALL be returned as the body of the 200 response.</li>\n<li><strong>202 Accepted</strong>: Indicates that the receiving system has accepted custody of the message</li>\n<li><strong>204 No Content</strong>: Indicates that the message has been fully processed and would normally have had an application-level response, but because of instructions from the sender (e.g. the <a href=\"extension-messageheader-response-request.html\">messageheader-response-request</a> extension), no response is being provided</li>\n<li><strong>300+</strong>: Indicates that the message was not successfully processed.  The server MAY return an <a href=\"operationoutcome.html\">OperationOutcome</a> with additional information, and SHOULD do so if the response code is 400 or greater.&lt;br/&gt;\nThe client SHALL interpret a 4xx response to indicate that there is no point resubmitting the unaltered message, and a 5xx response to indicate an unexpected error occurred on the part of the server, with the implication that it may be appropriate to resubmit the original message. Doing so SHOULD NOT result in a duplicate message response. Repeated failures indicate either a fatal problem with the submission or a problem with the receiving application.</li>\n</ul>\n<p>The following rules apply when using $process-message:</p>\n<ul>\n<li>The operation only accepts POST transactions - any other HTTP method will result in an HTTP error</li>\n<li>The request content type submitted is always <a href=\"bundle.html\">Bundle</a> with type &quot;message&quot; containing a <a href=\"messageheader.html\">Message Header</a> resource as the first resource</li>\n<li>The response content type returned is always <a href=\"bundle.html\">Bundle</a> with type &quot;message&quot; containing a <a href=\"messageheader.html\">Message Header</a> resource as the first resource, or an HTTP error</li>\n<li>If the response is an error, the body SHOULD be an <a href=\"operationoutcome.html\">Errors &amp;mp; Warning</a> resource with full details</li>\n<li>The mailbox may be authenticated using standard HTTP authentication methods, including OAuth</li>\n</ul>\n<p>The $process-message operation can be used by any HTTP end-point that accepts FHIR messages, not just FHIR RESTful servers.</p>\n<p>In order to ensure consistency of processing, the <a href=\"messaging.html#reliable\">logical rules regarding processing of Bundle.id and message id</a> SHALL be followed when messages are processed using this operation.</p>\n<p>The $process-message operation may be used synchronously, or asynchronously.</p>\n<p>The following rules apply when using the $process-message operation synchronously:</p>\n<ul>\n<li>The URL (http://server/base/$process-message) has no parameters</li>\n<li>It is an error if the sender POSTs a message that requires multiple response messages</li>\n<li>Servers SHALL accept multiple concurrent message submissions and process them correctly (they are allowed to process them sequentially internally, but multiple concurrent submissions is not an error in its own right)</li>\n</ul>\n<p>The following rules apply when using the $process-message operation asynchronously:</p>\n<ul>\n<li>The URL has at least one parameter: http://server/base/$process-message?async=true</li>\n<li>The server acknowledges the message with a 200 OK with no body, or returns an HTTP error if the message cannot be processed</li>\n<li>Accepting the message means that the server has understood the message enough to know where to respond</li>\n<li>An <a href=\"operationoutcome.html\">OperationOutcome</a> SHOULD be returned in either case</li>\n<li>By default, the server responds by invoking the $process-message using the sender's stated end-point in the message: POST [MessageHeader.source.endpoint]/$process-messages]</li>\n<li>Since the source end-point may be manipulated by message transfer engines, an alternative response address may be specified using the parameter &quot;response-url&quot;: http://server/base/$process-message?async=true&amp;amp;response-url=http://server2.com/base/anything.  The endpoint at the specified URL SHALL implement the signature of the $process-message operation (parameter async=true, accept a Bundle, return a 200 OK or an error)</li>\n<li>The server submits response messages to the appropriate end-point with the parameter async=true. There is no response message for the response messages</li>\n</ul>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":4},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message","version":"4.0.1","name":"Process Message","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation accepts a message, processes it according to the definition of the event in the message header, and returns one or more response messages.  \n\nIn addition to processing the message event, a server may choose to retain all or some the resources and make them available on a `RESTful` interface, but is not required to do so.","code":"process-message","comment":"This operation does not use the parameters resource; the parameters \"async\" and \"response-url\" always go in the URL, if they are used, and the \"content\" parameter is always the body of the HTTP message.\n\nWhen processing messages, a server may return one of several status codes:\n* **200 OK**: Indicates that the message has been fully processed.  If an application-level response is expected for the submitted message, that response SHALL be returned as the body of the 200 response.\n* **202 Accepted**: Indicates that the receiving system has accepted custody of the message\n* **204 No Content**: Indicates that the message has been fully processed and would normally have had an application-level response, but because of instructions from the sender (e.g. the [messageheader-response-request](extension-messageheader-response-request.html) extension), no response is being provided\n* **300+**: Indicates that the message was not successfully processed.  The server MAY return an [OperationOutcome](operationoutcome.html) with additional information, and SHOULD do so if the response code is 400 or greater.<br/>\n    The client SHALL interpret a 4xx response to indicate that there is no point resubmitting the unaltered message, and a 5xx response to indicate an unexpected error occurred on the part of the server, with the implication that it may be appropriate to resubmit the original message. Doing so SHOULD NOT result in a duplicate message response. Repeated failures indicate either a fatal problem with the submission or a problem with the receiving application.\n\nThe following rules apply when using $process-message:\n\n* The operation only accepts POST transactions - any other HTTP method will result in an HTTP error\n* The request content type submitted is always [Bundle](bundle.html) with type \"message\" containing a [Message Header](messageheader.html) resource as the first resource\n* The response content type returned is always [Bundle](bundle.html) with type \"message\" containing a [Message Header](messageheader.html) resource as the first resource, or an HTTP error\n* If the response is an error, the body SHOULD be an [Errors &mp; Warning](operationoutcome.html) resource with full details\n* The mailbox may be authenticated using standard HTTP authentication methods, including OAuth\n\nThe $process-message operation can be used by any HTTP end-point that accepts FHIR messages, not just FHIR RESTful servers.\n\nIn order to ensure consistency of processing, the [logical rules regarding processing of Bundle.id and message id](messaging.html#reliable) SHALL be followed when messages are processed using this operation.\n\nThe $process-message operation may be used synchronously, or asynchronously.\n\nThe following rules apply when using the $process-message operation synchronously:\n\n* The URL (http://server/base/$process-message) has no parameters\n* It is an error if the sender POSTs a message that requires multiple response messages\n* Servers SHALL accept multiple concurrent message submissions and process them correctly (they are allowed to process them sequentially internally, but multiple concurrent submissions is not an error in its own right)\n\nThe following rules apply when using the $process-message operation asynchronously:\n\n* The URL has at least one parameter: http://server/base/$process-message?async=true\n* The server acknowledges the message with a 200 OK with no body, or returns an HTTP error if the message cannot be processed\n* Accepting the message means that the server has understood the message enough to know where to respond\n* An [OperationOutcome](operationoutcome.html) SHOULD be returned in either case\n* By default, the server responds by invoking the $process-message using the sender's stated end-point in the message: POST [MessageHeader.source.endpoint]/$process-messages]\n* Since the source end-point may be manipulated by message transfer engines, an alternative response address may be specified using the parameter \"response-url\": http://server/base/$process-message?async=true&amp;response-url=http://server2.com/base/anything.  The endpoint at the specified URL SHALL implement the signature of the $process-message operation (parameter async=true, accept a Bundle, return a 200 OK or an error)\n* The server submits response messages to the appropriate end-point with the parameter async=true. There is no response message for the response messages","resource":["MessageHeader"],"system":true,"type":false,"instance":false,"parameter":[{"name":"content","use":"in","min":1,"max":"1","documentation":"The message to process (or, if using asynchronous messaging, it may be a response message to accept)","type":"Bundle"},{"name":"async","use":"in","min":0,"max":"1","documentation":"If 'true' the message is processed using the asynchronous messaging pattern","type":"boolean"},{"name":"response-url","use":"in","min":0,"max":"1","documentation":"A URL to submit response messages to, if asynchronous messaging is being used, and if the MessageHeader.source.endpoint is not the appropriate place to submit responses","type":"url"},{"name":"return","use":"out","min":0,"max":"1","documentation":"A response message, if synchronous messaging is being used (mandatory in this case). For asynchronous messaging, there is no return value","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The message to process (or, if using asynchronous messaging, it may be a response message to accept)"]
        pub content: Bundle,
        #[doc = "If `true` the message is processed using the asynchronous messaging pattern"]
        #[parameter_rename = "async"]
        pub async_: Option<FHIRBoolean>,
        #[doc = "A URL to submit response messages to, if asynchronous messaging is being used, and if the"]
        #[doc = "`MessageHeader.source.endpoint` is not the appropriate place to submit responses"]
        #[parameter_rename = "response-url"]
        pub response_url: Option<FHIRUrl>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "A response message, if synchronous messaging is being used (mandatory in this case). For"]
        #[doc = "asynchronous messaging, there is no return value"]
        #[parameter_rename = "return"]
        pub return_: Option<Bundle>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_.unwrap_or_default())
        }
    }
}
#[doc = "This operation returns the preferred identifiers for identifiers, and terminologies. The operation"]
#[doc = "takes 2 parameters:"]
#[doc = ""]
#[doc = "* a system identifier - either a URI, an OID, or a v2 table 0396 (other) code"]
#[doc = "* a code for what kind of identifier is desired (URI, OID, v2 table 0396 identifier)"]
#[doc = ""]
#[doc = "and returns either the requested identifier, or an HTTP errors response with an `OperationOutcome`"]
#[doc = "because either the provided identifier was not recognized, or the requested identiifer type is not"]
#[doc = "known."]
#[doc = ""]
#[doc = "The principle use of this operation is when converting between v2, CDA and FHIR `Identifier/CX/II`"]
#[doc = "and `CodeableConcepts/C`(N/W)E/CD but the operation may also find use when converting metadata such"]
#[doc = "as profiles."]
pub mod NamingSystemPreferredId {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "preferred-id";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"NamingSystem-preferred-id","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch Preferred it</h2><p>OPERATION: Fetch Preferred it</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/NamingSystem-preferred-id</pre><div><p>This operation returns the preferred identifiers for identifiers, and terminologies. The operation takes 2 parameters:</p>\n<ul>\n<li>a system identifier - either a URI, an OID, or a v2 table 0396 (other) code</li>\n<li>a code for what kind of identifier is desired (URI, OID, v2 table 0396 identifier)</li>\n</ul>\n<p>and returns either the requested identifier, or an HTTP errors response with an OperationOutcome because either the provided identifier was not recognized, or the requested identiifer type is not known.</p>\n<p>The principle use of this operation is when converting between v2, CDA and FHIR Identifier/CX/II and CodeableConcepts/C(N/W)E/CD but the operation may also find use when converting metadata such as profiles.</p>\n</div><p>URL: [base]/NamingSystem/$preferred-id</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>id</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The server parses the provided id to see what type it is (mary a URI, an OID as a URI, a plain OID, or a v2 table 0396 code). If the server can't tell what type of identifier it is, it can try it as multiple types. It is an error if more than one system matches the provided identifier</p>\n</div></td></tr><tr><td>IN</td><td>type</td><td>1..1</td><td><a href=\"datatypes.html#code\">code</a></td><td><a href=\"valueset-namingsystem-identifier-type.html\">http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.0.1</a> (Required)</td><td/></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>OIDs are return as plain OIDs (not the URI form).</p>\n</div></td></tr></table><div><p>Servers handle this request by finding the provided identifier in their known naming systems, and returning the requested identifier type (<a href=\"namingsystem-definitions.html#NamingSystem.uniqueId.type\">NamingSystem.uniqueId.type</a>). If there are multiple possible identifiers of the specified type (e.g. multiple OIDs) the server returns an error.</p>\n<p>If the server wishes, it can also look through all code systems and value sets it knows about when attempting to find the requested identifier</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/NamingSystem-preferred-id","version":"4.0.1","name":"Fetch Preferred it","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation returns the preferred identifiers for identifiers, and terminologies. The operation takes 2 parameters:     \n\n* a system identifier - either a URI, an OID, or a v2 table 0396 (other) code  \n* a code for what kind of identifier is desired (URI, OID, v2 table 0396 identifier)    \n\nand returns either the requested identifier, or an HTTP errors response with an `OperationOutcome` because either the provided identifier was not recognized, or the requested identiifer type is not known.    \n\nThe principle use of this operation is when converting between v2, CDA and FHIR Identifier/CX/II and CodeableConcepts/C(N/W)E/CD but the operation may also find use when converting metadata such as profiles.","code":"preferred-id","comment":"Servers handle this request by finding the provided identifier in their known naming systems, and returning the requested identifier type ([NamingSystem.uniqueId.type](namingsystem-definitions.html#NamingSystem.uniqueId.type)). If there are multiple possible identifiers of the specified type (e.g. multiple OIDs) the server returns an error.    \n\nIf the server wishes, it can also look through all code systems and value sets it knows about when attempting to find the requested identifier","resource":["NamingSystem"],"system":false,"type":true,"instance":false,"parameter":[{"name":"id","use":"in","min":1,"max":"1","documentation":"The server parses the provided id to see what type it is (mary a URI, an OID as a URI, a plain OID, or a v2 table 0396 code). If the server can't tell what type of identifier it is, it can try it as multiple types. It is an error if more than one system matches the provided identifier","type":"string"},{"name":"type","use":"in","min":1,"max":"1","type":"code","binding":{"strength":"required","valueSet":"http://hl7.org/fhir/ValueSet/namingsystem-identifier-type|4.0.1"}},{"name":"result","use":"out","min":1,"max":"1","documentation":"OIDs are return as plain OIDs (not the URI form).","type":"string"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The server parses the provided id to see what type it is (mary a URI, an OID as a URI, a plain OID,"]
        #[doc = "or a v2 table 0396 code). If the server can't tell what type of identifier it is, it can try it as"]
        #[doc = "multiple types. It is an error if more than one system matches the provided identifier"]
        pub id: FHIRString,
        #[doc = "type_"]
        #[parameter_rename = "type"]
        pub type_: FHIRCode,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "`OIDs` are return as plain `OIDs` (not the URI form)."]
        pub result: FHIRString,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The *lastn query* meets the common need for searching for the most recent or last n=number of"]
#[doc = "observations for a subject. For example, retrieving the last 5 temperatures for a patient to view"]
#[doc = "trends or fetching the most recent laboratory results or vitals signs. To ask a server to return the"]
#[doc = "last n=number of observations, the *lastn* query uses the [`normal search"]
#[doc = "parameters`](observation.html#search) defined for the Observation resource. However, rather than"]
#[doc = "their normal use, they are interpreted as inputs - i.e.. instead of requiring that the resources"]
#[doc = "literally contain the search parameters, they are passed to a server algorithm of some kind that"]
#[doc = "uses them to determine the most appropriate matches."]
#[doc = ""]
#[doc = "The request for a lastn query SHALL include:"]
#[doc = ""]
#[doc = "* A `$lastn` operation parameter"]
#[doc = "* A subject using either the `patient` or `subject` search parameter"]
#[doc = "* A `category` parameter and/or a search parameter that contains a code element in its `FHIRpath`"]
#[doc = "expression. ( e.g., `code` or `code-value-concept`)"]
#[doc = ""]
#[doc = "The request for a lastn query MAY include:"]
#[doc = ""]
#[doc = "* Other Observation search parameters and modifiers"]
#[doc = ""]
#[doc = "The response from a lastn query is a set of observations:"]
#[doc = ""]
#[doc = "* Filtered by additional parameters"]
#[doc = "* If not explicitly filtered by status then will include statuses of `entered-in-error`"]
#[doc = "* 'GROUP BY' `Observation.code`"]
#[doc = "* Codes SHALL be considered equivalent if the `coding.value` *and* `coding.system` are the same."]
#[doc = "* Text only codes SHALL be treated and grouped based on the text."]
#[doc = "* For codes with translations (multiple codings), the code translations are assumed to be equal and"]
#[doc = "the grouping by code SHALL follow the transitive property of equality."]
#[doc = ""]
#[doc = "for example:"]
#[doc = ""]
#[doc = "|`Observation.code for observation a`|`Observation.code for observation b`|`Observation.code for observation c`|`number of groups [codes/text in each group]`|"]
#[doc = "|---|---|---|---|"]
#[doc = "|`a`|`b`|`c`|`3 [a],[b],[c]`|"]
#[doc = "|`a`|`b`|`a,c`|`2 [a.c],[b]`|"]
#[doc = "|`a`|`b`|`a,b`|`1 [a,b]`|"]
#[doc = "|`textM`|`Text`|`t e x t`|`3 [text],[Text],[t e x t]`|"]
#[doc = ""]
#[doc = "* Sorted from most recent to the oldest"]
#[doc = "* Limited to the number of requested responses per group specified by the optional *max* query"]
#[doc = "parameter"]
#[doc = "* In case of a tie - when the effective times for >1 Observations are equal - both will be returned."]
#[doc = "Therefore, more Observations may be returned than is specified in *max*. For example, 4 Observations"]
#[doc = "instead of 3 if the 3rd and 4th most recent observation had the same effective time."]
#[doc = "* If no maximum number is given then only the most recent Observation in each group is returned."]
#[doc = ""]
#[doc = "The set of returned observations should represent distinct real world observations and not the same"]
#[doc = "observation with changes in status or versions. If there are no matches, the *lastn* query SHALL"]
#[doc = "return an empty search set with no error, but may include an operation outcome with further advice."]
pub mod ObservationLastn {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRPositiveInt;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "lastn";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Observation-lastn","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Last N Observations Query</h2><p>OPERATION: Last N Observations Query</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Observation-lastn</pre><div><p>The <em>lastn query</em> meets the common need for searching for the most recent or last n=number of observations for a subject. For example, retrieving the last 5 temperatures for a patient to view trends or fetching the most recent laboratory results or vitals signs. To ask a server to return the last n=number of observations, the <em>lastn</em> query uses the <a href=\"observation.html#search\">normal search parameters</a> defined for the Observation resource.  However, rather than their normal use, they are interpreted as inputs - i.e.. instead of requiring that the resources literally contain the search parameters, they are passed to a server algorithm of some kind that uses them to determine the most appropriate matches.</p>\n<p>The request for a lastn query SHALL include:</p>\n<ul>\n<li>A <code>$lastn</code> operation parameter</li>\n<li>A subject using either the <code>patient</code> or <code>subject</code>  search parameter</li>\n<li>A <code>category</code> parameter and/or a search parameter that contains a code element in its FHIRpath expression.  ( e.g., <code>code</code> or <code>code-value-concept</code>)</li>\n</ul>\n<p>The request for a lastn query MAY include:</p>\n<ul>\n<li>Other Observation search parameters and modifiers</li>\n</ul>\n<p>The response from a lastn query is a set of observations:</p>\n<ul>\n<li>Filtered by additional parameters\n<ul>\n<li>If not explicitly filtered by status then will include statuses of 'entered-in-error'</li>\n</ul>\n</li>\n<li>'GROUP BY' <code>Observation.code</code>\n<ul>\n<li>Codes SHALL be considered equivalent if the <code>coding.value</code> <em>and</em> <code>coding.system</code> are the same.</li>\n<li>Text only codes SHALL be treated and grouped based on the text.</li>\n<li>For codes with translations (multiple codings), the code translations are assumed to be equal and the grouping by code SHALL follow the transitive property of equality.</li>\n</ul>\n</li>\n</ul>\n<p>for example:</p>\n<table class=\"grid\">\n<thead>\n<tr><th>Observation.code for observation a</th><th>Observation.code for observation b</th><th>Observation.code for observation c</th><th>number of groups [codes/text in each group]</th></tr>\n</thead>\n<tbody>\n<tr><td>a</td><td>b</td><td>c</td><td>3 [a],[b],[c]</td></tr>\n<tr><td>a</td><td>b</td><td>a,c</td><td>2 [a.c],[b]</td></tr>\n<tr><td>a</td><td>b</td><td>a,b</td><td>1 [a,b]</td></tr>\n<tr><td>'textM'</td><td>'Text'</td><td>'t e x t'</td><td>3 ['text'],['Text'],['t e x t']</td></tr>\n</tbody>\n</table>\n<ul>\n<li>Sorted from most recent to the oldest</li>\n<li>Limited to the number of requested responses per group specified by the optional <em>max</em> query parameter\n<ul>\n<li>In case of a tie - when the effective times for &gt;1 Observations are equal - both will be returned.  Therefore, more Observations may be returned than is specified in <em>max</em>.  For example, 4 Observations instead of 3 if the 3rd and 4th most recent observation had the same effective time.</li>\n</ul>\n</li>\n<li>If no maximum number is given then only the most recent Observation in each group is returned.</li>\n</ul>\n<p>The set of returned observations should represent distinct real world observations and not the same observation with changes in status or versions. If there are no matches, the <em>lastn</em> query SHALL return an empty search set with no error, but may include an operation outcome with further advice.</p>\n</div><p>URL: [base]/Observation/$lastn</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>max</td><td>0..1</td><td><a href=\"datatypes.html#positiveInt\">positiveInt</a></td><td/><td><div><p><code>max</code> is  an optional input parameter to the <em>lastn</em> query operation.  It is used to specify the maximum number of Observations to return from each group. For example for the query &quot;Fetch the last 3 results for all vitals for a patient&quot; <code>max</code> = 3.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The set of most recent N Observations that match the <em>lastn</em> query search criteria.</p>\n</div></td></tr></table><div><p>The key differences between this query operation and simply searching Observation using the combination of <code>_count</code> and <code>_sort</code> parameters are:</p>\n<ul>\n<li>The <em>lastn</em> query returns <strong>only</strong> the last N resource grouped by code.  Using the _count query method doesn't restrict the total matches so you may need to page through several &quot;A&quot; Observations  before getting to Observation &quot;B&quot;.</li>\n<li>The server is responsible for grouping the observations by codes.  This frees the client from needing to determine which codes she should ask for.</li>\n</ul>\n<p>This operation cannot be performed on observations that the user is not authorized to see.  It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one. If there is no nominated patient (e.g. the operation is invoked at the system level) and the context is not associated with a single patient record, then the server should return an error. Specifying the relationship between the context, a user and patient records is outside the scope of this specification.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Observation-lastn","version":"4.0.1","name":"Last N Observations Query","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The *lastn query* meets the common need for searching for the most recent or last n=number of observations for a subject. For example, retrieving the last 5 temperatures for a patient to view trends or fetching the most recent laboratory results or vitals signs. To ask a server to return the last n=number of observations, the *lastn* query uses the [normal search parameters](observation.html#search) defined for the Observation resource.  However, rather than their normal use, they are interpreted as inputs - i.e.. instead of requiring that the resources literally contain the search parameters, they are passed to a server algorithm of some kind that uses them to determine the most appropriate matches.\n\nThe request for a lastn query SHALL include:\n\n* A `$lastn` operation parameter\n*  A subject using either the `patient` or `subject`  search parameter\n*  A `category` parameter and/or a search parameter that contains a code element in its `FHIRpath` expression.  ( e.g., `code` or `code-value-concept`)\n\nThe request for a lastn query MAY include:\n\n* Other Observation search parameters and modifiers\n\nThe response from a lastn query is a set of observations:\n\n*  Filtered by additional parameters\n   * If not explicitly filtered by status then will include statuses of 'entered-in-error'\n* 'GROUP BY' `Observation.code`\n   * Codes SHALL be considered equivalent if the `coding.value` *and* `coding.system` are the same.\n   * Text only codes SHALL be treated and grouped based on the text.\n   * For codes with translations (multiple codings), the code translations are assumed to be equal and the grouping by code SHALL follow the transitive property of equality.\n\nfor example:\n\n|Observation.code for observation a|Observation.code for observation b|Observation.code for observation c|number of groups [codes/text in each group]|    \n|---|---|---|---|     \n|a|b|c | 3 [a],[b],[c]|    \n|a|b|a,c | 2 [a.c],[b]|     \n|a|b|a,b | 1 [a,b]|    \n|'textM'|'Text'|'t e x t'|3 ['text'],['Text'],['t e x t']|\n\n* Sorted from most recent to the oldest\n* Limited to the number of requested responses per group specified by the optional *max* query parameter\n  * In case of a tie - when the effective times for >1 Observations are equal - both will be returned.  Therefore, more Observations may be returned than is specified in *max*.  For example, 4 Observations instead of 3 if the 3rd and 4th most recent observation had the same effective time.\n* If no maximum number is given then only the most recent Observation in each group is returned.\n\nThe set of returned observations should represent distinct real world observations and not the same observation with changes in status or versions. If there are no matches, the *lastn* query SHALL return an empty search set with no error, but may include an operation outcome with further advice.","code":"lastn","comment":"The key differences between this query operation and simply searching Observation using the combination of `_count` and `_sort` parameters are:\r\r* The *lastn* query returns **only** the last N resource grouped by code.  Using the _count query method doesn't restrict the total matches so you may need to page through several \"A\" Observations  before getting to Observation \"B\".\r* The server is responsible for grouping the observations by codes.  This frees the client from needing to determine which codes she should ask for.\r\rThis operation cannot be performed on observations that the user is not authorized to see.  It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one. If there is no nominated patient (e.g. the operation is invoked at the system level) and the context is not associated with a single patient record, then the server should return an error. Specifying the relationship between the context, a user and patient records is outside the scope of this specification.","resource":["Observation"],"system":false,"type":true,"instance":false,"parameter":[{"name":"max","use":"in","min":0,"max":"1","documentation":"`max` is  an optional input parameter to the *lastn* query operation.  It is used to specify the maximum number of Observations to return from each group. For example for the query \"Fetch the last 3 results for all vitals for a patient\" `max` = 3.","type":"positiveInt"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The set of most recent N Observations that match the *lastn* query search criteria.","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "`max` is an optional input parameter to the *lastn* query operation. It is used to specify the"]
        #[doc = "maximum number of Observations to return from each group. For example for the query \"Fetch the last"]
        #[doc = "3 results for all vitals for a patient\" `max` = 3."]
        pub max: Option<FHIRPositiveInt>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The set of most recent N Observations that match the *lastn* query search criteria."]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "The Statistics operation performs a set of statistical calculations on a set of clinical"]
#[doc = "measurements such as a blood pressure as stored on the server. This operation evaluates"]
#[doc = "[`Observation`](observation.html) resources having valueQuantity elements that have UCUM unit codes."]
#[doc = "Observations with a status of `entered-in-error` will be excluded from the calculations. The set of"]
#[doc = "Observations is defined by 4 parameters: * the subject of the observations for which the statistics"]
#[doc = "are being generated (`subject`) * which observations to generate statistics for (`code` and"]
#[doc = "`system`, or `coding`) * the time period over which to generate statistics 'duration` or `period`) *"]
#[doc = "the set of statistical analyses to return (`statistic`) Possible statistical analyses (see"]
#[doc = "[``StatisticsCode``](valueset-observation-statistics.html)): - **average** (\"Average\"): The"]
#[doc = "[mean](https://en.wikipedia.org/wiki/Arithmetic_mean) of N measurements over the stated period."]
#[doc = "- **maximum** (\"Maximum\"): The [maximum](https://en.wikipedia.org/wiki/Maximal_element) value of N"]
#[doc = "measurements over the stated period."]
#[doc = "- **minimum** (\"Minimum\"): The [minimum](https://en.wikipedia.org/wiki/Minimal_element) value of N"]
#[doc = "measurements over the stated period."]
#[doc = "- **count** (\"Count\"): The [number] of valid measurements over the stated period that contributed to"]
#[doc = "the other statistical outputs."]
#[doc = "- **total-count** (\"Total Count\"): The total [number] of valid measurements over the stated period,"]
#[doc = "including observations that were ignored because they did not contain valid result values."]
#[doc = "- **median** (\"Median\"): The [median](https://en.wikipedia.org/wiki/Median) of N measurements over"]
#[doc = "the stated period."]
#[doc = "- **std-dev** (\"Standard Deviation\"): The [standard"]
#[doc = "deviation](https://en.wikipedia.org/wiki/Standard_deviation) of N measurements over the stated"]
#[doc = "period."]
#[doc = "- **sum** (\"Sum\"): The [sum](https://en.wikipedia.org/wiki/Summation) of N measurements over the"]
#[doc = "stated period."]
#[doc = "- **variance** (\"Variance\"): The [variance](https://en.wikipedia.org/wiki/Variance) of N"]
#[doc = "measurements over the stated period."]
#[doc = "- **20-percent** (\"20th Percentile\"): The 20th"]
#[doc = "[Percentile](https://en.wikipedia.org/wiki/Percentile) of N measurements over the stated period."]
#[doc = "- **80-percent** (\"80th Percentile\"): The 80th"]
#[doc = "[Percentile](https://en.wikipedia.org/wiki/Percentile) of N measurements over the stated period."]
#[doc = "- **4-lower** (\"Lower Quartile\"): The lower [Quartile](https://en.wikipedia.org/wiki/Quartile)"]
#[doc = "Boundary of N measurements over the stated period."]
#[doc = "- **4-upper** (\"Upper Quartile\"): The upper [Quartile](https://en.wikipedia.org/wiki/Quartile)"]
#[doc = "Boundary of N measurements over the stated period."]
#[doc = "- **4-dev** (\"Quartile Deviation\"): The difference between the upper and lower"]
#[doc = "[Quartiles](https://en.wikipedia.org/wiki/Quartile) is called the Interquartile range. (IQR = Q3-Q1)"]
#[doc = "Quartile deviation or Semi-interquartile range is one-half the difference between the first and the"]
#[doc = "third quartiles."]
#[doc = "- **5-1** (\"1st Quintile\"): The lowest of four values that divide the N measurements into a"]
#[doc = "frequency distribution of five classes with each containing one fifth of the total population."]
#[doc = "- **5-2** (\"2nd Quintile\"): The second of four values that divide the N measurements into a"]
#[doc = "frequency distribution of five classes with each containing one fifth of the total population."]
#[doc = "- **5-3** (\"3rd Quintile\"): The third of four values that divide the N measurements into a frequency"]
#[doc = "distribution of five classes with each containing one fifth of the total population."]
#[doc = "- **5-4** (\"4th Quintile\"): The fourth of four values that divide the N measurements into a"]
#[doc = "frequency distribution of five classes with each containing one fifth of the total population."]
#[doc = "- **skew** (\"Skew\"): Skewness is a measure of the asymmetry of the probability distribution of a"]
#[doc = "real-valued random variable about its mean. The skewness value can be positive or negative, or even"]
#[doc = "undefined. Source: [Wikipedia](https://en.wikipedia.org/wiki/Skewness)."]
#[doc = "- **kurtosis** (\"Kurtosis\"): Kurtosis is a measure of the \"tailedness\" of the probability"]
#[doc = "distribution of a real-valued random variable. Source:"]
#[doc = "[Wikipedia](https://en.wikipedia.org/wiki/Kurtosis)."]
#[doc = "- **regression** (\"Regression\"): Linear regression is an approach for modeling two-dimensional"]
#[doc = "sample points with one independent variable and one dependent variable (conventionally, the x and y"]
#[doc = "coordinates in a Cartesian coordinate system) and finds a linear function (a non-vertical straight"]
#[doc = "line) that, as accurately as possible, predicts the dependent variable values as a function of the"]
#[doc = "independent variables. Source: [Wikipedia](https://en.wikipedia.org/wiki/Simple_linear_regression)"]
#[doc = "This Statistic code will return both a gradient and an intercept value."]
#[doc = "If successful, the operation returns an Observation resource for each code with the results of the"]
#[doc = "statistical calculations as component value pairs where the component code = the statistical code."]
#[doc = "The Observation also contains the input parameters `patient`,`code` and `duration` parameters. If"]
#[doc = "unsuccessful, an [``OperationOutcome``](operationoutcome.html) with an error message will be"]
#[doc = "returned. The client can request that all the observations on which the statistics are based be"]
#[doc = "returned as well, using the include parameter. If an include parameter is specified, a limit may"]
#[doc = "also be specified; the sources observations are subsetted at the server's discretion if count >"]
#[doc = "limit. This functionality is included with the intent of supporting graphical presentation"]
pub mod ObservationStats {
    use haste_fhir_model::r4::generated::resources::{
        Observation, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{
        Coding, FHIRBoolean, FHIRCode, FHIRDecimal, FHIRPositiveInt, FHIRString, FHIRUri, Period,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "stats";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Observation-stats","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Observation Statistics</h2><p>OPERATION: Observation Statistics</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Observation-stats</pre><div><p>The Statistics operation performs a set of statistical calculations on a set of clinical measurements such as a blood pressure as stored on the server.  This operation evaluates <a href=\"observation.html\">Observation</a> resources having valueQuantity elements that have UCUM unit codes. Observations with a status of 'entered-in-error' will be excluded from the calculations.</p>\n<p>The set of Observations is defined by 4 parameters:</p>\n<ul>\n<li>the subject of the observations for which the statistics are being generated (<code>subject</code>)</li>\n<li>which observations to generate statistics for (<code>code</code> and <code>system</code>, or <code>coding</code>)</li>\n<li>the time period over which to generate statistics 'duration<code>or</code>period`)</li>\n<li>the set of statistical analyses to return (<code>statistic</code>)</li>\n</ul>\n<p>Possible statistical analyses (see <a href=\"valueset-observation-statistics.html\">StatisticsCode</a>):</p>\n<ul>\n<li><strong>average</strong> (&quot;Average&quot;): The <a href=\"https://en.wikipedia.org/wiki/Arithmetic_mean\">mean</a> of N measurements over the stated period.</li>\n<li><strong>maximum</strong> (&quot;Maximum&quot;): The <a href=\"https://en.wikipedia.org/wiki/Maximal_element\">maximum</a> value of N measurements over the stated period.</li>\n<li><strong>minimum</strong> (&quot;Minimum&quot;): The <a href=\"https://en.wikipedia.org/wiki/Minimal_element\">minimum</a> value of N measurements over the stated period.</li>\n<li><strong>count</strong> (&quot;Count&quot;): The [number] of valid measurements over the stated period that contributed to the other statistical outputs.</li>\n<li><strong>total-count</strong> (&quot;Total Count&quot;): The total [number] of valid measurements over the stated period, including observations that were ignored because they did not contain valid result values.</li>\n<li><strong>median</strong> (&quot;Median&quot;): The <a href=\"https://en.wikipedia.org/wiki/Median\">median</a> of N measurements over the stated period.</li>\n<li><strong>std-dev</strong> (&quot;Standard Deviation&quot;): The <a href=\"https://en.wikipedia.org/wiki/Standard_deviation\">standard deviation</a> of N measurements over the stated period.</li>\n<li><strong>sum</strong> (&quot;Sum&quot;): The <a href=\"https://en.wikipedia.org/wiki/Summation\">sum</a> of N measurements over the stated period.</li>\n<li><strong>variance</strong> (&quot;Variance&quot;): The <a href=\"https://en.wikipedia.org/wiki/Variance\">variance</a> of N measurements over the stated period.</li>\n<li><strong>20-percent</strong> (&quot;20th Percentile&quot;): The 20th <a href=\"https://en.wikipedia.org/wiki/Percentile\">Percentile</a> of N measurements over the stated period.</li>\n<li><strong>80-percent</strong> (&quot;80th Percentile&quot;): The 80th <a href=\"https://en.wikipedia.org/wiki/Percentile\">Percentile</a> of N measurements over the stated period.</li>\n<li><strong>4-lower</strong> (&quot;Lower Quartile&quot;): The lower <a href=\"https://en.wikipedia.org/wiki/Quartile\">Quartile</a> Boundary of N measurements over the stated period.</li>\n<li><strong>4-upper</strong> (&quot;Upper Quartile&quot;): The upper <a href=\"https://en.wikipedia.org/wiki/Quartile\">Quartile</a> Boundary of N measurements over the stated period.</li>\n<li><strong>4-dev</strong> (&quot;Quartile Deviation&quot;): The difference between the upper and lower <a href=\"https://en.wikipedia.org/wiki/Quartile\">Quartiles</a> is called the Interquartile range. (IQR = Q3-Q1) Quartile deviation or Semi-interquartile range is one-half the difference between the first and the third quartiles.</li>\n<li><strong>5-1</strong> (&quot;1st Quintile&quot;): The lowest of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.</li>\n<li><strong>5-2</strong> (&quot;2nd Quintile&quot;): The second of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.</li>\n<li><strong>5-3</strong> (&quot;3rd Quintile&quot;): The third of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.</li>\n<li><strong>5-4</strong> (&quot;4th Quintile&quot;): The fourth of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.</li>\n<li><strong>skew</strong> (&quot;Skew&quot;): Skewness is a measure of the asymmetry of the probability distribution of a real-valued random variable about its mean. The skewness value can be positive or negative, or even undefined.  Source: <a href=\"https://en.wikipedia.org/wiki/Skewness\">Wikipedia</a>.</li>\n<li><strong>kurtosis</strong> (&quot;Kurtosis&quot;): Kurtosis  is a measure of the &quot;tailedness&quot; of the probability distribution of a real-valued random variable.   Source: <a href=\"https://en.wikipedia.org/wiki/Kurtosis\">Wikipedia</a>.</li>\n<li><strong>regression</strong> (&quot;Regression&quot;): Linear regression is an approach for modeling two-dimensional sample points with one independent variable and one dependent variable (conventionally, the x and y coordinates in a Cartesian coordinate system) and finds a linear function (a non-vertical straight line) that, as accurately as possible, predicts the dependent variable values as a function of the independent variables. Source: <a href=\"https://en.wikipedia.org/wiki/Simple_linear_regression\">Wikipedia</a>  This Statistic code will return both a gradient and an intercept value.</li>\n</ul>\n<p>If successful, the operation returns an Observation resource for each code with the results of the statistical calculations as component value pairs where the component code = the statistical code. The Observation also contains the input parameters <code>patient</code>,<code>code</code> and <code>duration</code> parameters. If unsuccessful, an <a href=\"operationoutcome.html\">OperationOutcome</a> with an error message will be returned.</p>\n<p>The client can request that all the observations on which the statistics are based be returned as well, using the include parameter. If an include parameter is specified, a limit may also be specified; the sources observations are subsetted at the server's discretion if count &gt; limit. This functionality is included with the intent of supporting graphical presentation</p>\n</div><p>URL: [base]/Observation/$stats</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>subject</td><td>1..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The subject of the relevant Observations, which has the value of the Observation.subject.reference. E.g. 'Patient/123'. Reference can be to an absolute URL, but servers only perform stats on their own observations</p>\n</div></td></tr><tr><td>IN</td><td>code</td><td>0..*</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The test code(s) upon which the statistics are being performed. Provide along with a system, or as a coding. For example, the LOINC code  =\n2339-0 (Glucose [Mass/\u200bvolume] in Blood) will evaluate all relevant Observations with this code in <code>Observation.code</code> and <code>Observation.component.code</code>. For LOINC codes that are panels, e.g., 85354-9(Blood pressure panel with all children optional), the stats operation returns statistics for each of the individual panel measurements.  That means it will include and evaluate all values grouped by code for all the individual observations that are: 1) referenced in   <code>.related</code> for <code>.related.type</code> = 'has-member'  and 2) component observations in <code>Observation.component</code>.</p>\n</div></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The system for the code(s). Or provide a coding instead</p>\n</div></td></tr><tr><td>IN</td><td>coding</td><td>0..*</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>The test code upon which the statistics are being performed, as a Coding</p>\n</div></td></tr><tr><td>IN</td><td>duration</td><td>0..1</td><td><a href=\"datatypes.html#decimal\">decimal</a></td><td/><td><div><p>The time period of interest given as hours.  For example, the duration = &quot;1&quot; represents the last hour - the time period from on hour ago to now</p>\n</div></td></tr><tr><td>IN</td><td>period</td><td>0..1</td><td><a href=\"datatypes.html#Period\">Period</a></td><td/><td><div><p>The time period over which the calculations to be performed, if a duration is not provided</p>\n</div></td></tr><tr><td>IN</td><td>statistic</td><td>1..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>average|max|min|count  The statistical operations to be performed on the relevant operations. Multiple statistics operations can be specified. These codes are defined <a href=\"valueset-observation-statistics.html\">here</a></p>\n</div></td></tr><tr><td>IN</td><td>include</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Whether to return the observations on which the statistics are based</p>\n</div></td></tr><tr><td>IN</td><td>limit</td><td>0..1</td><td><a href=\"datatypes.html#positiveInt\">positiveInt</a></td><td/><td><div><p>If an include parameter is specified, a limit may also be specified to limit the number of source Observations returned.  If the include paramter is absent or equal to &quot;false&quot; the limit parameter SHALL be ignored by the server</p>\n</div></td></tr><tr><td>OUT</td><td>statistics</td><td>1..*</td><td><a href=\"observation.html\">Observation</a></td><td/><td><div><p>A set of observations, one observation for each code, each containing one component for each statistic. The Observation.component.code contains the statistic, and is relative to the Observation.code and cannot be interpreted independently.  The Observation will also contain a subject, effectivePeriod, and code reflecting the input parameters.  The status is fixed to <code>final</code>.</p>\n</div></td></tr><tr><td>OUT</td><td>source</td><td>0..*</td><td><a href=\"observation.html\">Observation</a></td><td/><td><div><p>Source observations on which the statistics are based</p>\n</div></td></tr></table><div><p>If <a href=\"extensibility.html#modifierExtension\">modifier extensions</a> are present in the Observation, they must be accounted for by implementers.  A modifier extension may affect the observation.value in a way that it should be excluded from the from the calculations.</p>\n<p>This operation cannot be performed on observations that the user is not authorized to see.  It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one. If there is no nominated patient (e.g. the operation is invoked at the system level) and the context is not associated with a single patient record, then the server should return an error. Specifying the relationship between the context, a user and patient records is outside the scope of this specification.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Observation-stats","version":"4.0.1","name":"Observation Statistics","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The Statistics operation performs a set of statistical calculations on a set of clinical measurements such as a blood pressure as stored on the server.  This operation evaluates [Observation](observation.html) resources having valueQuantity elements that have UCUM unit codes. Observations with a status of 'entered-in-error' will be excluded from the calculations.  \r\rThe set of Observations is defined by 4 parameters:\r\r*  the subject of the observations for which the statistics are being generated (`subject`)\r* which observations to generate statistics for (`code` and `system`, or `coding`)\r* the time period over which to generate statistics 'duration` or `period`)\r* the set of statistical analyses to return (`statistic`)\r\rPossible statistical analyses (see [`StatisticsCode`](valueset-observation-statistics.html)):\r\r - **average** (\"Average\"): The [mean](https://en.wikipedia.org/wiki/Arithmetic_mean) of N measurements over the stated period.\r\n - **maximum** (\"Maximum\"): The [maximum](https://en.wikipedia.org/wiki/Maximal_element) value of N measurements over the stated period.\r\n - **minimum** (\"Minimum\"): The [minimum](https://en.wikipedia.org/wiki/Minimal_element) value of N measurements over the stated period.\r\n - **count** (\"Count\"): The [number] of valid measurements over the stated period that contributed to the other statistical outputs.\r\n - **total-count** (\"Total Count\"): The total [number] of valid measurements over the stated period, including observations that were ignored because they did not contain valid result values.\r\n - **median** (\"Median\"): The [median](https://en.wikipedia.org/wiki/Median) of N measurements over the stated period.\r\n - **std-dev** (\"Standard Deviation\"): The [standard deviation](https://en.wikipedia.org/wiki/Standard_deviation) of N measurements over the stated period.\r\n - **sum** (\"Sum\"): The [sum](https://en.wikipedia.org/wiki/Summation) of N measurements over the stated period.\r\n - **variance** (\"Variance\"): The [variance](https://en.wikipedia.org/wiki/Variance) of N measurements over the stated period.\r\n - **20-percent** (\"20th Percentile\"): The 20th [Percentile](https://en.wikipedia.org/wiki/Percentile) of N measurements over the stated period.\r\n - **80-percent** (\"80th Percentile\"): The 80th [Percentile](https://en.wikipedia.org/wiki/Percentile) of N measurements over the stated period.\r\n - **4-lower** (\"Lower Quartile\"): The lower [Quartile](https://en.wikipedia.org/wiki/Quartile) Boundary of N measurements over the stated period.\r\n - **4-upper** (\"Upper Quartile\"): The upper [Quartile](https://en.wikipedia.org/wiki/Quartile) Boundary of N measurements over the stated period.\r\n - **4-dev** (\"Quartile Deviation\"): The difference between the upper and lower [Quartiles](https://en.wikipedia.org/wiki/Quartile) is called the Interquartile range. (IQR = Q3-Q1) Quartile deviation or Semi-interquartile range is one-half the difference between the first and the third quartiles.\r\n - **5-1** (\"1st Quintile\"): The lowest of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.\r\n - **5-2** (\"2nd Quintile\"): The second of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.\r\n - **5-3** (\"3rd Quintile\"): The third of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.\r\n - **5-4** (\"4th Quintile\"): The fourth of four values that divide the N measurements into a frequency distribution of five classes with each containing one fifth of the total population.\r\n - **skew** (\"Skew\"): Skewness is a measure of the asymmetry of the probability distribution of a real-valued random variable about its mean. The skewness value can be positive or negative, or even undefined.  Source: [Wikipedia](https://en.wikipedia.org/wiki/Skewness).\r\n - **kurtosis** (\"Kurtosis\"): Kurtosis  is a measure of the \"tailedness\" of the probability distribution of a real-valued random variable.   Source: [Wikipedia](https://en.wikipedia.org/wiki/Kurtosis).\r\n - **regression** (\"Regression\"): Linear regression is an approach for modeling two-dimensional sample points with one independent variable and one dependent variable (conventionally, the x and y coordinates in a Cartesian coordinate system) and finds a linear function (a non-vertical straight line) that, as accurately as possible, predicts the dependent variable values as a function of the independent variables. Source: [Wikipedia](https://en.wikipedia.org/wiki/Simple_linear_regression)  This Statistic code will return both a gradient and an intercept value.\r\n\r\rIf successful, the operation returns an Observation resource for each code with the results of the statistical calculations as component value pairs where the component code = the statistical code. The Observation also contains the input parameters `patient`,`code` and `duration` parameters. If unsuccessful, an [`OperationOutcome`](operationoutcome.html) with an error message will be returned.\r\rThe client can request that all the observations on which the statistics are based be returned as well, using the include parameter. If an include parameter is specified, a limit may also be specified; the sources observations are subsetted at the server's discretion if count > limit. This functionality is included with the intent of supporting graphical presentation","code":"stats","comment":"If [modifier extensions](extensibility.html#modifierExtension) are present in the Observation, they must be accounted for by implementers.  A modifier extension may affect the observation.value in a way that it should be excluded from the from the calculations.\r\rThis operation cannot be performed on observations that the user is not authorized to see.  It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one. If there is no nominated patient (e.g. the operation is invoked at the system level) and the context is not associated with a single patient record, then the server should return an error. Specifying the relationship between the context, a user and patient records is outside the scope of this specification.","resource":["Observation"],"system":false,"type":true,"instance":false,"parameter":[{"name":"subject","use":"in","min":1,"max":"1","documentation":"The subject of the relevant Observations, which has the value of the Observation.subject.reference. E.g. 'Patient/123'. Reference can be to an absolute URL, but servers only perform stats on their own observations","type":"uri"},{"name":"code","use":"in","min":0,"max":"*","documentation":"The test code(s) upon which the statistics are being performed. Provide along with a system, or as a coding. For example, the LOINC code  = \r2339-0 (Glucose [Mass/\u200bvolume] in Blood) will evaluate all relevant Observations with this code in `Observation.code` and `Observation.component.code`. For LOINC codes that are panels, e.g., 85354-9(Blood pressure panel with all children optional), the stats operation returns statistics for each of the individual panel measurements.  That means it will include and evaluate all values grouped by code for all the individual observations that are: 1) referenced in   `.related` for `.related.type` = 'has-member'  and 2) component observations in `Observation.component`.","type":"string"},{"name":"system","use":"in","min":0,"max":"1","documentation":"The system for the code(s). Or provide a coding instead","type":"uri"},{"name":"coding","use":"in","min":0,"max":"*","documentation":"The test code upon which the statistics are being performed, as a Coding","type":"Coding"},{"name":"duration","use":"in","min":0,"max":"1","documentation":"The time period of interest given as hours.  For example, the duration = \"1\" represents the last hour - the time period from on hour ago to now","type":"decimal"},{"name":"period","use":"in","min":0,"max":"1","documentation":"The time period over which the calculations to be performed, if a duration is not provided","type":"Period"},{"name":"statistic","use":"in","min":1,"max":"*","documentation":"average|max|min|count  The statistical operations to be performed on the relevant operations. Multiple statistics operations can be specified. These codes are defined [here](valueset-observation-statistics.html)","type":"code"},{"name":"include","use":"in","min":0,"max":"1","documentation":"Whether to return the observations on which the statistics are based","type":"boolean"},{"name":"limit","use":"in","min":0,"max":"1","documentation":"If an include parameter is specified, a limit may also be specified to limit the number of source Observations returned.  If the include paramter is absent or equal to \"false\" the limit parameter SHALL be ignored by the server","type":"positiveInt"},{"name":"statistics","use":"out","min":1,"max":"*","documentation":"A set of observations, one observation for each code, each containing one component for each statistic. The Observation.component.code contains the statistic, and is relative to the Observation.code and cannot be interpreted independently.  The Observation will also contain a subject, effectivePeriod, and code reflecting the input parameters.  The status is fixed to `final`.","type":"Observation"},{"name":"source","use":"out","min":0,"max":"*","documentation":"Source observations on which the statistics are based","type":"Observation"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The subject of the relevant Observations, which has the value of the"]
        #[doc = "`Observation.subject.reference.` E.g. 'Patient/123'. Reference can be to an absolute URL, but"]
        #[doc = "servers only perform stats on their own observations"]
        pub subject: FHIRUri,
        #[doc = "The test code(s) upon which the statistics are being performed. Provide along with a system, or as a"]
        #[doc = "coding. For example, the LOINC code = 2339-0 (Glucose [Mass/\u{200b}volume] in Blood) will evaluate all"]
        #[doc = "relevant Observations with this code in `Observation.code` and `Observation.component.code`. For"]
        #[doc = "LOINC codes that are panels, e.g., 85354-9(Blood pressure panel with all children optional), the"]
        #[doc = "stats operation returns statistics for each of the individual panel measurements. That means it will"]
        #[doc = "include and evaluate all values grouped by code for all the individual observations that are: 1)"]
        #[doc = "referenced in `.related` for `.related.type` = `has-member` and 2) component observations in"]
        #[doc = "`Observation.component`."]
        pub code: Option<Vec<FHIRString>>,
        #[doc = "The system for the code(s). Or provide a coding instead"]
        pub system: Option<FHIRUri>,
        #[doc = "The test code upon which the statistics are being performed, as a Coding"]
        pub coding: Option<Vec<Coding>>,
        #[doc = "The time period of interest given as hours. For example, the duration = \"1\" represents the last hour"]
        #[doc = "- the time period from on hour ago to now"]
        pub duration: Option<FHIRDecimal>,
        #[doc = "The time period over which the calculations to be performed, if a duration is not provided"]
        pub period: Option<Period>,
        #[doc = "average|max|min|count The statistical operations to be performed on the relevant operations."]
        #[doc = "Multiple statistics operations can be specified. These codes are defined"]
        #[doc = "[`here`](valueset-observation-statistics.html)"]
        pub statistic: Vec<FHIRCode>,
        #[doc = "Whether to return the observations on which the statistics are based"]
        pub include: Option<FHIRBoolean>,
        #[doc = "If an include parameter is specified, a limit may also be specified to limit the number of source"]
        #[doc = "Observations returned. If the include paramter is absent or equal to \"false\" the limit parameter"]
        #[doc = "SHALL be ignored by the server"]
        pub limit: Option<FHIRPositiveInt>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "A set of observations, one observation for each code, each containing one component for each"]
        #[doc = "statistic. The `Observation.component.code` contains the statistic, and is relative to the"]
        #[doc = "`Observation.code` and cannot be interpreted independently. The Observation will also contain a"]
        #[doc = "subject, effectivePeriod, and code reflecting the input parameters. The status is fixed to `final`."]
        pub statistics: Vec<Observation>,
        #[doc = "Source observations on which the statistics are based"]
        pub source: Option<Vec<Observation>>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation is used to return all the information related to one or more patients described in"]
#[doc = "the resource or context on which this operation is invoked. The response is a bundle of type"]
#[doc = "\"searchset\". At a minimum, the patient resource(s) itself is returned, along with any other"]
#[doc = "resources that the server has that are related to the patient(s), and that are available for the"]
#[doc = "given user. The server also returns whatever resources are needed to support the records - e.g."]
#[doc = "linked practitioners, medications, locations, organizations etc."]
#[doc = ""]
#[doc = "The intended use for this operation is to provide a patient with access to their entire record (e.g."]
#[doc = "\"Blue Button\"), or for provider or other user to perform a bulk data download. The server SHOULD"]
#[doc = "return at least all resources that it has that are in the patient compartment for the identified"]
#[doc = "patient(s), and any resource referenced from those, including binaries and attachments. In the US"]
#[doc = "Realm, at a minimum, the resources returned SHALL include all the data covered by the meaningful use"]
#[doc = "common data elements as defined in the US Core Implementation Guide. Other applicable implementation"]
#[doc = "guides may make additional rules about how much information that is returned."]
pub mod PatientEverything {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRDate, FHIRInstant, FHIRInteger};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "everything";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Patient-everything","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Fetch Patient Record</h2><p>OPERATION: Fetch Patient Record</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Patient-everything</pre><div><p>This operation is used to return all the information related to one or more patients described in the resource or context on which this operation is invoked. The response is a bundle of type &quot;searchset&quot;. At a minimum, the patient resource(s) itself is returned, along with any other resources that the server has that are related to the patient(s), and that are available for the given user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, medications, locations, organizations etc.</p>\n<p>The intended use for this operation is to provide a patient with access to their entire record (e.g. &quot;Blue Button&quot;), or for provider or other user to perform a bulk data download.  The server SHOULD return at least all resources that it has that are in the patient compartment for the identified patient(s), and any resource referenced from those, including binaries and attachments. In the US Realm, at a minimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in the US Core Implementation Guide. Other applicable implementation guides may make additional rules about how much information that is returned.</p>\n</div><p>URL: [base]/Patient/$everything</p><p>URL: [base]/Patient/[id]/$everything</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>start</td><td>0..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all records prior to the end date are in scope.</p>\n</div></td></tr><tr><td>IN</td><td>end</td><td>0..1</td><td><a href=\"datatypes.html#date\">date</a></td><td/><td><div><p>The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all records subsequent to the start date are in scope.</p>\n</div></td></tr><tr><td>IN</td><td>_since</td><td>0..1</td><td><a href=\"datatypes.html#instant\">instant</a></td><td/><td><div><p>Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time</p>\n</div></td></tr><tr><td>IN</td><td>_type</td><td>0..*</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absence of any specified types, the server returns all resource types</p>\n</div></td></tr><tr><td>IN</td><td>_count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>See discussion below on the utility of paging through the results of the $everything operation</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The bundle type is &quot;searchset&quot;</p>\n</div></td></tr></table><div><p>The key differences between this operation and simply searching the patient compartment are:</p>\n<ul>\n<li>unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)</li>\n<li>the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones).</li>\n</ul>\n<p>This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment.</p>\n<p>It is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one, or can determine an appropriate list of patients to provide data for from the context of the request.   If there is no nominated patient (GET /Patient/$everything) and the context is not associated with a single patient record, the actual list of patients is all patients that the user associated with the request has access to. This may be all patients in the family that the patient has access to, or it may be all patients that a care provider has access to, or all patients on the entire record system. In such cases, the server may choose to return an error rather than all the records.  Specifying the relationship between the context, a user and patient records is outside the scope of this specification (though see <a href=\"http://hl7.org/fhir/smart-app-launch\">The Smart App Launch Implementation Guide</a>.</p>\n<p>When this operation is used to access multiple patient records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made <a href=\"async.html\">asynchronously</a>, and associated with <a href=\"formats.html#bulk\">bulk data formats</a>. Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for <a href=\"http.html#paging\">Searching</a>, using the <a href=\"search.html#count\">_count</a> parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.</p>\n<p>The _since parameter is provided to support periodic queries to get additional information that has changed about the patient since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Patient-everything","version":"4.0.1","name":"Fetch Patient Record","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation is used to return all the information related to one or more patients described in the resource or context on which this operation is invoked. The response is a bundle of type \"searchset\". At a minimum, the patient resource(s) itself is returned, along with any other resources that the server has that are related to the patient(s), and that are available for the given user. The server also returns whatever resources are needed to support the records - e.g. linked practitioners, medications, locations, organizations etc.   \n\nThe intended use for this operation is to provide a patient with access to their entire record (e.g. \"Blue Button\"), or for provider or other user to perform a bulk data download.  The server SHOULD return at least all resources that it has that are in the patient compartment for the identified patient(s), and any resource referenced from those, including binaries and attachments. In the US Realm, at a minimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in the US Core Implementation Guide. Other applicable implementation guides may make additional rules about how much information that is returned.","code":"everything","comment":"The key differences between this operation and simply searching the patient compartment are:    \n\n* unless the client requests otherwise, the server returns the entire result set in a single bundle (rather than using paging)  \n* the server is responsible for determining what resources to return as included resources (rather than the client specifying which ones). \n\nThis frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment. \n\nIt is assumed that the server has identified and secured the context appropriately, and can either associate the authorization context with a single patient, or determine whether the context has the rights to the nominated patient, if there is one, or can determine an appropriate list of patients to provide data for from the context of the request.   If there is no nominated patient (GET /Patient/$everything) and the context is not associated with a single patient record, the actual list of patients is all patients that the user associated with the request has access to. This may be all patients in the family that the patient has access to, or it may be all patients that a care provider has access to, or all patients on the entire record system. In such cases, the server may choose to return an error rather than all the records.  Specifying the relationship between the context, a user and patient records is outside the scope of this specification (though see [The Smart App Launch Implementation Guide](http://hl7.org/fhir/smart-app-launch). \n\nWhen this operation is used to access multiple patient records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made [asynchronously](async.html), and associated with [bulk data formats](formats.html#bulk). Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for [Searching](http.html#paging), using the [_count](search.html#count) parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so.\n\nThe _since parameter is provided to support periodic queries to get additional information that has changed about the patient since the last query. This means that the _since parameter is based on record time. The value of the _since parameter should be set to the time from the server. If using direct response, this is the timestamp in the response header. If using the async interface, this is the transaction timestamp in the json response. Servers should ensure that the timestamps a managed such that the client does not miss any changes. Clients should be able to handle getting the same response more than once in the case that the transaction falls on a time boundary. Clients should ensure that the other query parameters are constant to ensure a coherent set of records when doing periodic queries.","resource":["Patient"],"system":false,"type":true,"instance":true,"parameter":[{"name":"start","use":"in","min":0,"max":"1","documentation":"The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all records prior to the end date are in scope.","type":"date"},{"name":"end","use":"in","min":0,"max":"1","documentation":"The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all records subsequent to the start date are in scope.","type":"date"},{"name":"_since","use":"in","min":0,"max":"1","documentation":"Resources updated after this period will be included in the response. The intent of this parameter is to allow a client to request only records that have changed since the last request, based on either the return header time, or or (for asynchronous use), the transaction time","type":"instant"},{"name":"_type","use":"in","min":0,"max":"*","documentation":"One or more parameters, each containing one or more comma-delimited FHIR resource types to include in the return resources. In the absence of any specified types, the server returns all resource types","type":"code"},{"name":"_count","use":"in","min":0,"max":"1","documentation":"See discussion below on the utility of paging through the results of the $everything operation","type":"integer"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The bundle type is \"searchset\"","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The date range relates to care dates, not record currency dates - e.g. all records relating to care"]
        #[doc = "provided in a certain date range. If no start date is provided, all records prior to the end date"]
        #[doc = "are in scope."]
        pub start: Option<FHIRDate>,
        #[doc = "The date range relates to care dates, not record currency dates - e.g. all records relating to care"]
        #[doc = "provided in a certain date range. If no end date is provided, all records subsequent to the start"]
        #[doc = "date are in scope."]
        pub end: Option<FHIRDate>,
        #[doc = "Resources updated after this period will be included in the response. The intent of this parameter"]
        #[doc = "is to allow a client to request only records that have changed since the last request, based on"]
        #[doc = "either the return header time, or or (for asynchronous use), the transaction time"]
        #[parameter_rename = "_since"]
        pub since: Option<FHIRInstant>,
        #[doc = "One or more parameters, each containing one or more comma-delimited FHIR resource types to include"]
        #[doc = "in the return resources. In the absence of any specified types, the server returns all resource"]
        #[doc = "types"]
        #[parameter_rename = "_type"]
        pub type_: Option<Vec<FHIRCode>>,
        #[doc = "See discussion below on the utility of paging through the results of the $everything operation"]
        #[parameter_rename = "_count"]
        pub count: Option<FHIRInteger>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The bundle type is \"searchset\""]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "A Master Patient Index ([MPI](http://en.wikipedia.org/wiki/Enterprise_master_patient_index) ) is a"]
#[doc = "service used to manage patient identification in a context where multiple patient databases exist."]
#[doc = "Healthcare applications and middleware use the MPI to match patients between the databases, and to"]
#[doc = "store new patient details as they are encountered. `MPIs` are highly specialized applications, often"]
#[doc = "tailored extensively to the institution's particular mix of patients. `MPIs` can also be run on a"]
#[doc = "regional and national basis."]
#[doc = ""]
#[doc = "To ask an MPI to match a patient, clients use the \"$match\" operation, which accepts a patient"]
#[doc = "resource which may be only partially complete. The data provided is interpreted as an MPI input and"]
#[doc = "processed by an algorithm of some kind that uses the data to determine the most appropriate matches"]
#[doc = "in the patient set. Note that different MPI matching algorithms have different required inputs. The"]
#[doc = "generic $match operation does not specify any particular algorithm, nor a minimum set of information"]
#[doc = "that must be provided when asking for an MPI match operation to be performed, but many"]
#[doc = "implementations will have a set of minimum information, which may be declared in their definition of"]
#[doc = "the $match operation by specifying a profile on the resource parameter, indicating which properties"]
#[doc = "are required in the search. The patient resource submitted to the operation does not have to be"]
#[doc = "complete, nor does it need to pass validation (i.e. mandatory fields don't need to be populated),"]
#[doc = "but it does have to be a valid instance, as it is used as the reference data to match against."]
pub mod PatientMatch {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRBoolean, FHIRInteger};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "match";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Patient-match","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Find patient matches using MPI based logic</h2><p>OPERATION: Find patient matches using MPI based logic</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Patient-match</pre><div><p>A Master Patient Index (<a href=\"http://en.wikipedia.org/wiki/Enterprise_master_patient_index\">MPI</a> ) is a service used to manage patient identification in a context where multiple patient databases exist. Healthcare applications and middleware use the MPI to match patients between the databases, and to store new patient details as they are encountered. MPIs are highly specialized applications, often tailored extensively to the institution's particular mix of patients. MPIs can also be run on a regional and national basis.</p>\n<p>To ask an MPI to match a patient, clients use the &quot;$match&quot; operation, which accepts a patient resource which may be only partially complete. The data provided is interpreted as an MPI input and processed by an algorithm of some kind that uses the data to determine the most appropriate matches in the patient set.  Note that different MPI matching algorithms have different required inputs. The generic $match operation does not specify any particular algorithm, nor a minimum set of information that must be provided when asking for an MPI match operation to be performed, but many implementations will have a set of minimum information, which may be declared in their definition of the $match operation by specifying a profile on the resource parameter, indicating which properties are required in the search.  The patient resource submitted to the operation does not have to be complete, nor does it need to pass validation (i.e. mandatory fields don't need to be populated), but it does have to be a valid instance, as it is used as the reference data to match against.</p>\n</div><p>URL: [base]/Patient/$match</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>resource</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>Use this to provide an entire set of patient details for the MPI to match against (e.g. POST a patient record to Patient/$match).</p>\n</div></td></tr><tr><td>IN</td><td>onlyCertainMatches</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>If there are multiple potential matches, then the match should not return the results with this flag set to true.  When false, the server may return multiple results with each result graded accordingly.</p>\n</div></td></tr><tr><td>IN</td><td>count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>The maximum number of records to return. If no value is provided, the server decides how many matches to return. Note that clients should be careful when using this, as it may prevent probable - and valid - matches from being returned</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>A bundle contain a set of Patient records that represent possible matches, optionally it may also contain an OperationOutcome with further information about the search results (such as warnings or information messages, such as a count of records that were close but eliminated)  If the operation was unsuccessful, then an OperationOutcome may be returned along with a BadRequest status Code (e.g. security issue, or insufficient properties in patient fragment - check against profile)</p>\n</div></td></tr></table><div><p>The response from an &quot;mpi&quot; query is a bundle containing patient records, ordered from most likely to least likely. If there are no patient matches, the MPI SHALL return an empty search set with no error, but may include an operation outcome with further advice regarding patient selection. All patient records SHALL have a search score from 0 to 1, where 1 is the most certain match, along with an extension &quot;<a href=\"extension-match-grade.html\">match-grade</a>&quot; that indicates the MPI's position on the match quality.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Patient-match","version":"4.0.1","name":"Find patient matches using MPI based logic","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"A Master Patient Index ([MPI](http://en.wikipedia.org/wiki/Enterprise_master_patient_index) ) is a service used to manage patient identification in a context where multiple patient databases exist. Healthcare applications and middleware use the MPI to match patients between the databases, and to store new patient details as they are encountered. MPIs are highly specialized applications, often tailored extensively to the institution's particular mix of patients. MPIs can also be run on a regional and national basis.  \n\nTo ask an MPI to match a patient, clients use the \"$match\" operation, which accepts a patient resource which may be only partially complete. The data provided is interpreted as an MPI input and processed by an algorithm of some kind that uses the data to determine the most appropriate matches in the patient set.  Note that different MPI matching algorithms have different required inputs. The generic $match operation does not specify any particular algorithm, nor a minimum set of information that must be provided when asking for an MPI match operation to be performed, but many implementations will have a set of minimum information, which may be declared in their definition of the $match operation by specifying a profile on the resource parameter, indicating which properties are required in the search.  The patient resource submitted to the operation does not have to be complete, nor does it need to pass validation (i.e. mandatory fields don't need to be populated), but it does have to be a valid instance, as it is used as the reference data to match against.","code":"match","comment":"The response from an \"mpi\" query is a bundle containing patient records, ordered from most likely to least likely. If there are no patient matches, the MPI SHALL return an empty search set with no error, but may include an operation outcome with further advice regarding patient selection. All patient records SHALL have a search score from 0 to 1, where 1 is the most certain match, along with an extension \"[match-grade](extension-match-grade.html)\" that indicates the MPI's position on the match quality.","resource":["Patient"],"system":false,"type":true,"instance":false,"parameter":[{"name":"resource","use":"in","min":1,"max":"1","documentation":"Use this to provide an entire set of patient details for the MPI to match against (e.g. POST a patient record to Patient/$match).","type":"Resource"},{"name":"onlyCertainMatches","use":"in","min":0,"max":"1","documentation":"If there are multiple potential matches, then the match should not return the results with this flag set to true.  When false, the server may return multiple results with each result graded accordingly.","type":"boolean"},{"name":"count","use":"in","min":0,"max":"1","documentation":"The maximum number of records to return. If no value is provided, the server decides how many matches to return. Note that clients should be careful when using this, as it may prevent probable - and valid - matches from being returned","type":"integer"},{"name":"return","use":"out","min":1,"max":"1","documentation":"A bundle contain a set of Patient records that represent possible matches, optionally it may also contain an `OperationOutcome` with further information about the search results (such as warnings or information messages, such as a count of records that were close but eliminated)  If the operation was unsuccessful, then an `OperationOutcome` may be returned along with a `BadRequest` status Code (e.g. security issue, or insufficient properties in patient fragment - check against profile)","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Use this to provide an entire set of patient details for the MPI to match against (e.g. POST a"]
        #[doc = "patient record to Patient/$match)."]
        pub resource: Resource,
        #[doc = "If there are multiple potential matches, then the match should not return the results with this flag"]
        #[doc = "set to true. When false, the server may return multiple results with each result graded accordingly."]
        pub onlyCertainMatches: Option<FHIRBoolean>,
        #[doc = "The maximum number of records to return. If no value is provided, the server decides how many"]
        #[doc = "matches to return. Note that clients should be careful when using this, as it may prevent probable -"]
        #[doc = "and valid - matches from being returned"]
        pub count: Option<FHIRInteger>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "A bundle contain a set of Patient records that represent possible matches, optionally it may also"]
        #[doc = "contain an `OperationOutcome` with further information about the search results (such as warnings or"]
        #[doc = "information messages, such as a count of records that were close but eliminated) If the operation"]
        #[doc = "was unsuccessful, then an `OperationOutcome` may be returned along with a `BadRequest` status Code"]
        #[doc = "(e.g. security issue, or insufficient properties in patient fragment - check against profile)"]
        #[parameter_rename = "return"]
        pub return_: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Bundle(value.return_)
        }
    }
}
#[doc = "The apply operation applies a `PlanDefinition` to a given context"]
pub mod PlanDefinitionApply {
    use haste_fhir_model::r4::generated::resources::{
        CarePlan, OperationDefinition, Parameters, ParametersParameter, PlanDefinition, Resource,
    };
    use haste_fhir_model::r4::generated::types::{CodeableConcept, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "apply";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"PlanDefinition-apply","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Apply</h2><p>OPERATION: Apply</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/PlanDefinition-apply</pre><div><p>The apply operation applies a PlanDefinition to a given context</p>\n</div><p>URL: [base]/PlanDefinition/$apply</p><p>URL: [base]/PlanDefinition/[id]/$apply</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>planDefinition</td><td>0..1</td><td><a href=\"plandefinition.html\">PlanDefinition</a></td><td/><td><div><p>The plan definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter is required</p>\n</div></td></tr><tr><td>IN</td><td>subject</td><td>1..*</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The subject(s) that is/are the target of the plan to be applied. The subject may be a Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be resolved as the subject of the PlanDefinition based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined</p>\n</div></td></tr><tr><td>IN</td><td>encounter</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The encounter in context, if any</p>\n</div></td></tr><tr><td>IN</td><td>practitioner</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The practitioner applying the plan definition</p>\n</div></td></tr><tr><td>IN</td><td>organization</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#reference\">reference</a>)</td><td/><td><div><p>The organization applying the plan definition</p>\n</div></td></tr><tr><td>IN</td><td>userType</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)</p>\n</div></td></tr><tr><td>IN</td><td>userLanguage</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>Preferred language of the person using the system</p>\n</div></td></tr><tr><td>IN</td><td>userTaskContext</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources</p>\n</div></td></tr><tr><td>IN</td><td>setting</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>The current setting of the request (inpatient, outpatient, etc.)</p>\n</div></td></tr><tr><td>IN</td><td>settingContext</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>Additional detail about the setting of the request, if any</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"careplan.html\">CarePlan</a></td><td/><td><div><p>The CarePlan that is the result of applying the plan definition</p>\n</div></td></tr></table><div><p>The result of this operation is a CarePlan resource with a single activity represented by a RequestGroup. The RequestGroup will have actions for each of the applicable actions in the plan based on evaluating the applicability condition in context. For each applicable action, the definition is applied as described in the $apply operation of the ActivityDefinition resource, and the resulting resource is added as an activity to the CarePlan. If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. In addition, parameters to the $apply operation are available within dynamicValue expressions as context variables, accessible by the name of the parameter, prefixed with a percent (%) symbol. For a more detailed description, refer to the PlanDefinition and ActivityDefinition resource documentation</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/PlanDefinition-apply","version":"4.0.1","name":"Apply","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The apply operation applies a `PlanDefinition` to a given context","code":"apply","comment":"The result of this operation is a CarePlan resource with a single activity represented by a RequestGroup. The RequestGroup will have actions for each of the applicable actions in the plan based on evaluating the applicability condition in context. For each applicable action, the definition is applied as described in the $apply operation of the ActivityDefinition resource, and the resulting resource is added as an activity to the CarePlan. If the ActivityDefinition includes library references, those libraries will be available to the evaluated expressions. If those libraries have parameters, those parameters will be bound by name to the parameters given to the operation. In addition, parameters to the $apply operation are available within dynamicValue expressions as context variables, accessible by the name of the parameter, prefixed with a percent (%) symbol. For a more detailed description, refer to the PlanDefinition and ActivityDefinition resource documentation","resource":["PlanDefinition"],"system":false,"type":true,"instance":true,"parameter":[{"name":"planDefinition","use":"in","min":0,"max":"1","documentation":"The plan definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter is required","type":"PlanDefinition"},{"name":"subject","use":"in","min":1,"max":"*","documentation":"The subject(s) that is/are the target of the plan to be applied. The subject may be a Patient, Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be resolved as the subject of the `PlanDefinition` based on the type of the subject. If multiple subjects of the same type are provided, the behavior is implementation-defined","type":"string","searchType":"reference"},{"name":"encounter","use":"in","min":0,"max":"1","documentation":"The encounter in context, if any","type":"string","searchType":"reference"},{"name":"practitioner","use":"in","min":0,"max":"1","documentation":"The practitioner applying the plan definition","type":"string","searchType":"reference"},{"name":"organization","use":"in","min":0,"max":"1","documentation":"The organization applying the plan definition","type":"string","searchType":"reference"},{"name":"userType","use":"in","min":0,"max":"1","documentation":"The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.)","type":"CodeableConcept"},{"name":"userLanguage","use":"in","min":0,"max":"1","documentation":"Preferred language of the person using the system","type":"CodeableConcept"},{"name":"userTaskContext","use":"in","min":0,"max":"1","documentation":"The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources","type":"CodeableConcept"},{"name":"setting","use":"in","min":0,"max":"1","documentation":"The current setting of the request (inpatient, outpatient, etc.)","type":"CodeableConcept"},{"name":"settingContext","use":"in","min":0,"max":"1","documentation":"Additional detail about the setting of the request, if any","type":"CodeableConcept"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The `CarePlan` that is the result of applying the plan definition","type":"CarePlan"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The plan definition to be applied. If the operation is invoked at the instance level, this parameter"]
        #[doc = "is not allowed; if the operation is invoked at the type level, this parameter is required"]
        pub planDefinition: Option<PlanDefinition>,
        #[doc = "The subject(s) that is/are the target of the plan to be applied. The subject may be a Patient,"]
        #[doc = "Practitioner, Organization, Location, Device, or Group. Subjects provided in this parameter will be"]
        #[doc = "resolved as the subject of the `PlanDefinition` based on the type of the subject. If multiple"]
        #[doc = "subjects of the same type are provided, the behavior is implementation-defined"]
        pub subject: Vec<FHIRString>,
        #[doc = "The encounter in context, if any"]
        pub encounter: Option<FHIRString>,
        #[doc = "The practitioner applying the plan definition"]
        pub practitioner: Option<FHIRString>,
        #[doc = "The organization applying the plan definition"]
        pub organization: Option<FHIRString>,
        #[doc = "The type of user initiating the request, e.g. patient, healthcare provider, or specific type of"]
        #[doc = "healthcare provider (physician, nurse, etc.)"]
        pub userType: Option<CodeableConcept>,
        #[doc = "Preferred language of the person using the system"]
        pub userLanguage: Option<CodeableConcept>,
        #[doc = "The task the system user is performing, e.g. laboratory results review, medication list review, etc."]
        #[doc = "This information can be used to tailor decision support outputs, such as recommended information"]
        #[doc = "resources"]
        pub userTaskContext: Option<CodeableConcept>,
        #[doc = "The current setting of the request (inpatient, outpatient, etc.)"]
        pub setting: Option<CodeableConcept>,
        #[doc = "Additional detail about the setting of the request, if any"]
        pub settingContext: Option<CodeableConcept>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The `CarePlan` that is the result of applying the plan definition"]
        #[parameter_rename = "return"]
        pub return_: CarePlan,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::CarePlan(value.return_)
        }
    }
}
#[doc = "The data-requirements operation aggregates and returns the parameters and data requirements for the"]
#[doc = "plan definition and all its dependencies as a single module definition library"]
pub mod PlanDefinitionDataRequirements {
    use haste_fhir_model::r4::generated::resources::{
        Library, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "data-requirements";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"PlanDefinition-data-requirements","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Data Requirements</h2><p>OPERATION: Data Requirements</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/PlanDefinition-data-requirements</pre><div><p>The data-requirements operation aggregates and returns the parameters and data requirements for the plan definition and all its dependencies as a single module definition library</p>\n</div><p>URL: [base]/PlanDefinition/[id]/$data-requirements</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"library.html\">Library</a></td><td/><td><div><p>The result of the requirements gathering is a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the plan definition</p>\n</div></td></tr></table><div><p>The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the plan definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the plan definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/PlanDefinition-data-requirements","version":"4.0.1","name":"Data Requirements","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The data-requirements operation aggregates and returns the parameters and data requirements for the plan definition and all its dependencies as a single module definition library","code":"data-requirements","comment":"The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the plan definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the plan definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)","resource":["PlanDefinition"],"system":false,"type":false,"instance":true,"parameter":[{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the requirements gathering is a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the plan definition","type":"Library"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the requirements gathering is a module-definition Library that describes the aggregate"]
        #[doc = "parameters, data requirements, and dependencies of the plan definition"]
        #[parameter_rename = "return"]
        pub return_: Library,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Library(value.return_)
        }
    }
}
#[doc = "This operation takes a resource in one form, and returns to in another form. Both input and output"]
#[doc = "are a single resource. The primary use of this operation is to convert between formats (e.g. (XML ->"]
#[doc = "JSON or vice versa)"]
pub mod ResourceConvert {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "convert";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-convert","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Convert from one form to another</h2><p>OPERATION: Convert from one form to another</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-convert</pre><div><p>This operation takes a resource in one form, and returns to in another form. Both input and output are a single resource. The primary use of this operation is to convert between formats (e.g. (XML -&gt; JSON or vice versa)</p>\n</div><p>URL: [base]/$convert</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>input</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The resource that is to be converted</p>\n</div></td></tr><tr><td>OUT</td><td>output</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The resource after conversion</p>\n</div></td></tr></table><div><p>While the primary use of this operation is simple - converting a resource from one format to another, there are many potential uses including:</p>\n<ul>\n<li>converting resources from one version to another</li>\n<li>restructuring information in a resource (e.g. moving method into/out of Observation.code)</li>\n<li>extracting data from a questionnaire</li>\n<li>converting CDA documents or v2 messages (as a binary resource) to a bundle (or vice versa) (or even openEHR or openMHealth).</li>\n</ul>\n<p>These variants would all be associated with parameters that define and control these kind of conversions, though such parameters are not defined at this time. In the absence of any parameters, simple format conversion is all that will occur.</p>\n<p>For this reason, implementers should be aware that:</p>\n<ul>\n<li>the output resource type may be different from the input resource (particularly, it might be a bundle)</li>\n<li>binary resources may be represented directly using some other content-type (i.e. just post the content directly)</li>\n</ul>\n<p>Implementers are encouraged to provide feedback to HL7 about their use of this operation</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"draft"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-convert","version":"4.0.1","name":"Convert from one form to another","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation takes a resource in one form, and returns to in another form. Both input and output are a single resource. The primary use of this operation is to convert between formats (e.g. (XML -> JSON or vice versa)","code":"convert","comment":"While the primary use of this operation is simple - converting a resource from one format to another, there are many potential uses including:\n\n* converting resources from one version to another\n* restructuring information in a resource (e.g. moving method into/out of Observation.code)\n* extracting data from a questionnaire\n* converting CDA documents or v2 messages (as a binary resource) to a bundle (or vice versa) (or even openEHR or openMHealth). \n\nThese variants would all be associated with parameters that define and control these kind of conversions, though such parameters are not defined at this time. In the absence of any parameters, simple format conversion is all that will occur.\n\nFor this reason, implementers should be aware that:\n\n* the output resource type may be different from the input resource (particularly, it might be a bundle)\n* binary resources may be represented directly using some other content-type (i.e. just post the content directly)\n\nImplementers are encouraged to provide feedback to HL7 about their use of this operation","resource":["Resource"],"system":true,"type":false,"instance":false,"parameter":[{"name":"input","use":"in","min":1,"max":"1","documentation":"The resource that is to be converted","type":"Resource"},{"name":"output","use":"out","min":1,"max":"1","documentation":"The resource after conversion","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The resource that is to be converted"]
        pub input: Resource,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The resource after conversion"]
        pub output: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Return an entire graph of resources based on a [`GraphDefinition`](graphdefinition.html). The"]
#[doc = "operation is invoked on a specific instance of a resource, and the graph definition tells the server"]
#[doc = "what other resources to return in the same packaage"]
pub mod ResourceGraph {
    use haste_fhir_model::r4::generated::resources::{
        Bundle, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRUri;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "graph";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-graph","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Return a graph of resources</h2><p>OPERATION: Return a graph of resources</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-graph</pre><div><p>Return an entire graph of resources based on a <a href=\"graphdefinition.html\">GraphDefinition</a>. The operation is invoked on a specific instance of a resource, and the graph definition tells the server what other resources to return in the same packaage</p>\n</div><p>URL: [base]/Resource/[id]/$graph</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>graph</td><td>1..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Servers MAY choose to allow any graph definition to be specified, but MAY require that the client choose a graph definition from a specific list of known supported definitions. The server is not required to support a formal definition of the graph on the end point</p>\n</div></td></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"bundle.html\">Bundle</a></td><td/><td><div><p>The set of resources that were in the graph based on the provided definition</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-graph","version":"4.0.1","name":"Return a graph of resources","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Return an entire graph of resources based on a [`GraphDefinition`](graphdefinition.html). The operation is invoked on a specific instance of a resource, and the graph definition tells the server what other resources to return in the same packaage","code":"graph","resource":["Resource"],"system":false,"type":false,"instance":true,"parameter":[{"name":"graph","use":"in","min":1,"max":"1","documentation":"Servers MAY choose to allow any graph definition to be specified, but MAY require that the client choose a graph definition from a specific list of known supported definitions. The server is not required to support a formal definition of the graph on the end point","type":"uri"},{"name":"result","use":"out","min":1,"max":"1","documentation":"The set of resources that were in the graph based on the provided definition","type":"Bundle"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Servers MAY choose to allow any graph definition to be specified, but MAY require that the client"]
        #[doc = "choose a graph definition from a specific list of known supported definitions. The server is not"]
        #[doc = "required to support a formal definition of the graph on the end point"]
        pub graph: FHIRUri,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The set of resources that were in the graph based on the provided definition"]
        pub result: Bundle,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Execute a graphql statement on a since resource or against the entire system. See the [`Using"]
#[doc = "GraphQL with FHIR`](graphql.html) page for further details."]
#[doc = ""]
#[doc = "For the purposes of graphQL compatibility, this operation can also be invoked using a POST with the"]
#[doc = "graphQL as the body, or a JSON body (see [graphQL spec](http://graphql.org/) for details)"]
pub mod ResourceGraphql {
    use haste_fhir_model::r4::generated::resources::{
        Binary, OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "graphql";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-graphql","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Execute a graphql statement</h2><p>OPERATION: Execute a graphql statement</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-graphql</pre><div><p>Execute a graphql statement on a since resource or against the entire system. See the <a href=\"graphql.html\">Using GraphQL with FHIR</a> page for further details.</p>\n<p>For the purposes of graphQL compatibility, this operation can also be invoked using a POST with the graphQL as the body, or a JSON body (see <a href=\"http://graphql.org/\">graphQL spec</a> for details)</p>\n</div><p>URL: [base]/$graphql</p><p>URL: [base]/Resource/[id]/$graphql</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>query</td><td>1..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td/></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"binary.html\">Binary</a></td><td/><td><div><p>The content is always returned as application/json; this SHOULD be specified in the Accept header</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":1},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-graphql","version":"4.0.1","name":"Execute a graphql statement","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Execute a graphql statement on a since resource or against the entire system. See the [Using GraphQL with FHIR](graphql.html) page for further details.\n\nFor the purposes of graphQL compatibility, this operation can also be invoked using a POST with the graphQL as the body, or a JSON body (see [graphQL spec](http://graphql.org/) for details)","code":"graphql","resource":["Resource"],"system":true,"type":false,"instance":true,"parameter":[{"name":"query","use":"in","min":1,"max":"1","type":"string"},{"name":"result","use":"out","min":1,"max":"1","documentation":"The content is always returned as application/json; this SHOULD be specified in the Accept header","type":"Binary"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "query"]
        pub query: FHIRString,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The content is always returned as application/json; this SHOULD be specified in the Accept header"]
        pub result: Binary,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation retrieves a summary of the profiles, tags, and security labels for the given scope;"]
#[doc = "e.g. for each scope:"]
#[doc = ""]
#[doc = "* system-wide: a list of all profiles, tags and security labels in use by the system"]
#[doc = "* resource-type level: A list of all profiles, tags, and security labels for the resource type"]
#[doc = "* individual resource level: A list of all profiles, tags, and security labels for the current"]
#[doc = "version of the resource. Also, as a special case, this operation (and other meta operations) can be"]
#[doc = "performed on a historical version of a resource)"]
pub mod ResourceMeta {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::Meta;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "meta";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-meta","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Access a list of profiles, tags, and security labels</h2><p>OPERATION: Access a list of profiles, tags, and security labels</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-meta</pre><div><p>This operation retrieves a summary of the profiles, tags, and security labels for the given scope; e.g. for each scope:</p>\n<ul>\n<li>system-wide: a list of all profiles, tags and security labels in use by the system</li>\n<li>resource-type level: A list of all profiles, tags, and security labels for the resource type</li>\n<li>individual resource level: A list of all profiles, tags, and security labels for the current version of the resource.  Also, as a special case, this operation (and other meta operations) can be performed on a historical version of a resource)</li>\n</ul>\n</div><p>URL: [base]/$meta</p><p>URL: [base]/Resource/$meta</p><p>URL: [base]/Resource/[id]/$meta</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html#Meta\">Meta</a></td><td/><td><div><p>The meta returned by the operation</p>\n</div></td></tr></table><div><p>At the system and type levels, the $meta operation is used to get a summary of all the labels that are in use across the system. The principal use for this operation is to support search e.g. what tags can be searched for. At these levels, the meta will not contain versionId, lastUpdated etc. Systems are not obligated to implement the operation at this level (and should return a 4xx error if they don't). At the resource and historical entry level, the $meta operation returns the same meta as would be returned by accessing the resource directly. This can be used to allow a system to get access to the meta-information for the resource without accessing the resource itself, e.g. for security reasons</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-meta","version":"4.0.1","name":"Access a list of profiles, tags, and security labels","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation retrieves a summary of the profiles, tags, and security labels for the given scope; e.g. for each scope:  \n\n* system-wide: a list of all profiles, tags and security labels in use by the system \n* resource-type level: A list of all profiles, tags, and security labels for the resource type \n* individual resource level: A list of all profiles, tags, and security labels for the current version of the resource.  Also, as a special case, this operation (and other meta operations) can be performed on a historical version of a resource)","code":"meta","comment":"At the system and type levels, the $meta operation is used to get a summary of all the labels that are in use across the system. The principal use for this operation is to support search e.g. what tags can be searched for. At these levels, the meta will not contain versionId, lastUpdated etc. Systems are not obligated to implement the operation at this level (and should return a 4xx error if they don't). At the resource and historical entry level, the $meta operation returns the same meta as would be returned by accessing the resource directly. This can be used to allow a system to get access to the meta-information for the resource without accessing the resource itself, e.g. for security reasons","resource":["Resource"],"system":true,"type":true,"instance":true,"parameter":[{"name":"return","use":"out","min":1,"max":"1","documentation":"The meta returned by the operation","type":"Meta"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {}
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The meta returned by the operation"]
        #[parameter_rename = "return"]
        pub return_: Meta,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation takes a meta, and adds the profiles, tags, and security labels found in it to the"]
#[doc = "nominated resource"]
pub mod ResourceMetaAdd {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::Meta;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "meta-add";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-meta-add","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Add profiles, tags, and security labels to a resource</h2><p>OPERATION: Add profiles, tags, and security labels to a resource</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-meta-add</pre><div><p>This operation takes a meta, and adds the profiles, tags, and security labels found in it to the nominated resource</p>\n</div><p>URL: [base]/Resource/[id]/$meta-add</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>meta</td><td>1..1</td><td><a href=\"resource.html#Meta\">Meta</a></td><td/><td><div><p>Profiles, tags, and security labels to add to the existing resource. Note that profiles, tags, and security labels are sets, and duplicates are not created.  The identity of a tag or security label is the system+code. When matching existing tags during adding, version and display are ignored. For profiles, matching is based on the full URL</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html#Meta\">Meta</a></td><td/><td><div><p>Resulting meta for the resource</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-meta-add","version":"4.0.1","name":"Add profiles, tags, and security labels to a resource","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation takes a meta, and adds the profiles, tags, and security labels found in it to the nominated resource","code":"meta-add","resource":["Resource"],"system":false,"type":false,"instance":true,"parameter":[{"name":"meta","use":"in","min":1,"max":"1","documentation":"Profiles, tags, and security labels to add to the existing resource. Note that profiles, tags, and security labels are sets, and duplicates are not created.  The identity of a tag or security label is the system+code. When matching existing tags during adding, version and display are ignored. For profiles, matching is based on the full URL","type":"Meta"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Resulting meta for the resource","type":"Meta"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Profiles, tags, and security labels to add to the existing resource. Note that profiles, tags, and"]
        #[doc = "security labels are sets, and duplicates are not created. The identity of a tag or security label is"]
        #[doc = "the system+code. When matching existing tags during adding, version and display are ignored. For"]
        #[doc = "profiles, matching is based on the full URL"]
        pub meta: Meta,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Resulting meta for the resource"]
        #[parameter_rename = "return"]
        pub return_: Meta,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "This operation takes a meta, and deletes the profiles, tags, and security labels found in it from"]
#[doc = "the nominated resource"]
pub mod ResourceMetaDelete {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::Meta;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "meta-delete";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-meta-delete","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Delete profiles, tags, and security labels for a resource</h2><p>OPERATION: Delete profiles, tags, and security labels for a resource</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-meta-delete</pre><div><p>This operation takes a meta, and deletes the profiles, tags, and security labels found in it from the nominated resource</p>\n</div><p>URL: [base]/Resource/[id]/$meta-delete</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>meta</td><td>1..1</td><td><a href=\"resource.html#Meta\">Meta</a></td><td/><td><div><p>Profiles, tags, and security labels to delete from the existing resource. It is not an error if these tags, profiles, and labels do not exist.  The identity of a tag or security label is the system+code. When matching existing tags during deletion, version and display are ignored. For profiles, matching is based on the full URL</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html#Meta\">Meta</a></td><td/><td><div><p>Resulting meta for the resource</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":3},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-meta-delete","version":"4.0.1","name":"Delete profiles, tags, and security labels for a resource","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"This operation takes a meta, and deletes the profiles, tags, and security labels found in it from the nominated resource","code":"meta-delete","resource":["Resource"],"system":false,"type":false,"instance":true,"parameter":[{"name":"meta","use":"in","min":1,"max":"1","documentation":"Profiles, tags, and security labels to delete from the existing resource. It is not an error if these tags, profiles, and labels do not exist.  The identity of a tag or security label is the system+code. When matching existing tags during deletion, version and display are ignored. For profiles, matching is based on the full URL","type":"Meta"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Resulting meta for the resource","type":"Meta"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Profiles, tags, and security labels to delete from the existing resource. It is not an error if"]
        #[doc = "these tags, profiles, and labels do not exist. The identity of a tag or security label is the"]
        #[doc = "system+code. When matching existing tags during deletion, version and display are ignored. For"]
        #[doc = "profiles, matching is based on the full URL"]
        pub meta: Meta,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "Resulting meta for the resource"]
        #[parameter_rename = "return"]
        pub return_: Meta,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The validate operation checks whether the attached content would be acceptable either generally, as"]
#[doc = "a create, an update or as a delete to an existing resource. The action the server takes depends on"]
#[doc = "the mode parameter:"]
#[doc = ""]
#[doc = "* [mode not provided]: The server checks the content of the resource against any schema, constraint"]
#[doc = "rules, and other general terminology rules"]
#[doc = "* create: The server checks the content, and then checks that the content would be acceptable as a"]
#[doc = "create (e.g. that the content would not violate any uniqueness constraints)"]
#[doc = "* update: The server checks the content, and then checks that it would accept it as an update"]
#[doc = "against the nominated specific resource (e.g. that there are no changes to immutable fields the"]
#[doc = "server does not allow to change, and checking version integrity if appropriate)"]
#[doc = "* delete: The server ignores the content, and checks that the nominated resource is allowed to be"]
#[doc = "deleted (e.g. checking referential integrity rules)"]
#[doc = ""]
#[doc = "Modes update and delete can only be used when the operation is invoked at the resource instance"]
#[doc = "level. The return from this operation is an [`OperationOutcome`](operationoutcome.html)"]
#[doc = ""]
#[doc = "Note that this operation is not the only way to validate resources - see [`Validating"]
#[doc = "Resources`](validation.html) for further information."]
pub mod ResourceValidate {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, OperationOutcome, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRCode, FHIRUri};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "validate";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"Resource-validate","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Validate a resource</h2><p>OPERATION: Validate a resource</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/Resource-validate</pre><div><p>The validate operation checks whether the attached content would be acceptable either generally, as a create, an update or as a delete to an existing resource.  The action the server takes depends on the mode parameter:</p>\n<ul>\n<li>[mode not provided]: The server checks the content of the resource against any schema, constraint rules, and other general terminology rules</li>\n<li>create: The server checks the content, and then checks that the content would be acceptable as a create (e.g. that the content would not violate any uniqueness constraints)</li>\n<li>update: The server checks the content, and then checks that it would accept it as an update against the nominated specific resource (e.g. that there are no changes to immutable fields the server does not allow to change, and checking version integrity if appropriate)</li>\n<li>delete: The server ignores the content, and checks that the nominated resource is allowed to be deleted (e.g. checking referential integrity rules)</li>\n</ul>\n<p>Modes update and delete can only be used when the operation is invoked at the resource instance level.   The return from this operation is an <a href=\"operationoutcome.html\">OperationOutcome</a></p>\n<p>Note that this operation is not the only way to validate resources - see <a href=\"validation.html\">Validating Resources</a> for further information.</p>\n</div><p>URL: [base]/Resource/$validate</p><p>URL: [base]/Resource/[id]/$validate</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>resource</td><td>0..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>Must be present unless the mode is &quot;delete&quot;</p>\n</div></td></tr><tr><td>IN</td><td>mode</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td><a href=\"valueset-resource-validation-mode.html\">http://hl7.org/fhir/ValueSet/resource-validation-mode|4.0.1</a> (Required)</td><td><div><p>Default is 'no action'; (e.g. general validation)</p>\n</div></td></tr><tr><td>IN</td><td>profile</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>If this is nominated, then the resource is validated against this specific profile. If a profile is nominated, and the server cannot validate against the nominated profile, it SHALL return an error</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"operationoutcome.html\">OperationOutcome</a></td><td/><td><div><p>If the operation outcome does not list any errors, and a mode was specified, then this is an indication that the operation would be expected to succeed (excepting for transactional integrity issues, see below)</p>\n</div></td></tr></table><div><p>This operation may be used during design and development to validate application design. It can also be used at run-time. One possible use might be that a client asks the server whether a proposed update is valid as the user is editing a dialog and displays an updated error to the user. The operation can be used as part of a light-weight two phase commit protocol but there is no expectation that the server will hold the content of the resource after this operation is used, or that the server guarantees to successfully perform an actual create, update or delete after the validation operation completes.</p>\n<p>This operation returns a 200 OK whether or not the resource is valid. A 4xx or 5xx error means that the validation itself could not be performed, and it is unknown whether the resource is valid or not.</p>\n<p>Note: the correct behaviour of validation with regard to language (especially for Coding.display) is currently undefined, and further development and testing may lead to specific requirements or recommendations in subsequent releases</p>\n<p>Future versions of this specifcation may add additional validation parameters. A candidate list is maintained with the <a href=\"https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator\">FHIR Validator Documentation</a></p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/Resource-validate","version":"4.0.1","name":"Validate a resource","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The validate operation checks whether the attached content would be acceptable either generally, as a create, an update or as a delete to an existing resource.  The action the server takes depends on the mode parameter:  \n\n* [mode not provided]: The server checks the content of the resource against any schema, constraint rules, and other general terminology rules \n* create: The server checks the content, and then checks that the content would be acceptable as a create (e.g. that the content would not violate any uniqueness constraints) \n* update: The server checks the content, and then checks that it would accept it as an update against the nominated specific resource (e.g. that there are no changes to immutable fields the server does not allow to change, and checking version integrity if appropriate) \n* delete: The server ignores the content, and checks that the nominated resource is allowed to be deleted (e.g. checking referential integrity rules)  \n\nModes update and delete can only be used when the operation is invoked at the resource instance level.   The return from this operation is an [`OperationOutcome`](operationoutcome.html)\n\nNote that this operation is not the only way to validate resources - see [Validating Resources](validation.html) for further information.","code":"validate","comment":"This operation may be used during design and development to validate application design. It can also be used at run-time. One possible use might be that a client asks the server whether a proposed update is valid as the user is editing a dialog and displays an updated error to the user. The operation can be used as part of a light-weight two phase commit protocol but there is no expectation that the server will hold the content of the resource after this operation is used, or that the server guarantees to successfully perform an actual create, update or delete after the validation operation completes.\n\nThis operation returns a 200 OK whether or not the resource is valid. A 4xx or 5xx error means that the validation itself could not be performed, and it is unknown whether the resource is valid or not.\n\nNote: the correct behaviour of validation with regard to language (especially for Coding.display) is currently undefined, and further development and testing may lead to specific requirements or recommendations in subsequent releases\n\nFuture versions of this specifcation may add additional validation parameters. A candidate list is maintained with the [FHIR Validator Documentation](https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator)","resource":["Resource"],"system":false,"type":true,"instance":true,"parameter":[{"name":"resource","use":"in","min":0,"max":"1","documentation":"Must be present unless the mode is \"delete\"","type":"Resource"},{"name":"mode","use":"in","min":0,"max":"1","documentation":"Default is 'no action'; (e.g. general validation)","type":"code","binding":{"strength":"required","valueSet":"http://hl7.org/fhir/ValueSet/resource-validation-mode|4.0.1"}},{"name":"profile","use":"in","min":0,"max":"1","documentation":"If this is nominated, then the resource is validated against this specific profile. If a profile is nominated, and the server cannot validate against the nominated profile, it SHALL return an error","type":"uri"},{"name":"return","use":"out","min":1,"max":"1","documentation":"If the operation outcome does not list any errors, and a mode was specified, then this is an indication that the operation would be expected to succeed (excepting for transactional integrity issues, see below)","type":"OperationOutcome"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Must be present unless the mode is \"delete\""]
        pub resource: Option<Resource>,
        #[doc = "Default is 'no action'; (e.g. general validation)"]
        pub mode: Option<FHIRCode>,
        #[doc = "If this is nominated, then the resource is validated against this specific profile. If a profile is"]
        #[doc = "nominated, and the server cannot validate against the nominated profile, it SHALL return an error"]
        pub profile: Option<FHIRUri>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "If the operation outcome does not list any errors, and a mode was specified, then this is an"]
        #[doc = "indication that the operation would be expected to succeed (excepting for transactional integrity"]
        #[doc = "issues, see below)"]
        #[parameter_rename = "return"]
        pub return_: OperationOutcome,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::OperationOutcome(value.return_)
        }
    }
}
#[doc = "Generates a [`Questionnaire`](questionnaire.html) instance based on a specified"]
#[doc = "[`StructureDefinition`](structuredefinition.html), creating questions for each core element or"]
#[doc = "extension element found in the [`StructureDefinition`](structuredefinition.html)."]
#[doc = ""]
#[doc = "If the operation is not called at the instance level, one of the *identifier*, *profile* or *url*"]
#[doc = "`in` parameters must be provided. If more than one is specified, servers may raise an error or may"]
#[doc = "resolve with the parameter of their choice. If called at the instance level, these parameters will"]
#[doc = "be ignored. The response will contain a [`Questionnaire`](questionnaire.html) instance based on the"]
#[doc = "specified [`StructureDefinition`](structuredefinition.html) and/or an"]
#[doc = "[`OperationOutcome`](operationoutcome.html) resource with errors or warnings. Nested groups are used"]
#[doc = "to handle complex structures and data types. If the `supportedOnly` parameter is set to true, only"]
#[doc = "those elements marked as \"must support\" will be included."]
#[doc = ""]
#[doc = "This operation is intended to enable auto-generation of simple interfaces for arbitrary profiles."]
#[doc = "The `questionnaire` approach to data entry has limitations that will make it less optimal than"]
#[doc = "custom-defined interfaces. However, this function may be useful for simple applications or for"]
#[doc = "systems that wish to support \"non-core\" resources with minimal development effort."]
pub mod StructureDefinitionQuestionnaire {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Questionnaire, Resource,
    };
    use haste_fhir_model::r4::generated::types::{FHIRBoolean, FHIRCanonical, FHIRString};
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "questionnaire";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"StructureDefinition-questionnaire","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Build Questionnaire</h2><p>OPERATION: Build Questionnaire</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/StructureDefinition-questionnaire</pre><div><p>Generates a <a href=\"questionnaire.html\">Questionnaire</a> instance  based on a specified <a href=\"structuredefinition.html\">StructureDefinition</a>, creating questions for each core element or extension element found in the <a href=\"structuredefinition.html\">StructureDefinition</a>.</p>\n<p>If the operation is not called at the instance level, one of the <em>identifier</em>, <em>profile</em> or <em>url</em> 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored. The response will contain a <a href=\"questionnaire.html\">Questionnaire</a> instance based on the specified <a href=\"structuredefinition.html\">StructureDefinition</a> and/or an <a href=\"operationoutcome.html\">OperationOutcome</a> resource with errors or warnings.  Nested groups are used to handle complex structures and data types.  If the 'supportedOnly' parameter is set to true, only those elements marked as &quot;must support&quot; will be included.</p>\n<p>This operation is intended to enable auto-generation of simple interfaces for arbitrary profiles.  The 'questionnaire' approach to data entry has limitations that will make it less optimal than custom-defined interfaces.  However, this function may be useful for simple applications or for systems that wish to support &quot;non-core&quot; resources with minimal development effort.</p>\n</div><p>URL: [base]/StructureDefinition/$questionnaire</p><p>URL: [base]/StructureDefinition/[id]/$questionnaire</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>identifier</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>A logical identifier (i.e. 'StructureDefinition.identifier''). The server must know the StructureDefinition or be able to retrieve it from other known repositories.</p>\n</div></td></tr><tr><td>IN</td><td>profile</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#token\">token</a>)</td><td/><td><div><p>The <a href=\"structuredefinition.html\">StructureDefinition</a> is provided directly as part of the request. Servers may choose not to accept profiles in this fashion</p>\n</div></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>The StructureDefinition's official URL (i.e. 'StructureDefinition.url'). The server must know the StructureDefinition or be able to retrieve it from other known repositories.</p>\n</div></td></tr><tr><td>IN</td><td>supportedOnly</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>If true, the questionnaire will only include those elements marked as &quot;mustSupport='true'&quot; in the StructureDefinition.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"questionnaire.html\">Questionnaire</a></td><td/><td><div><p>The questionnaire form generated based on the StructureDefinition.</p>\n</div></td></tr></table><div><p><strong>Open Issue</strong>: Ideally, extensions should be populated in the generated <a href=\"questionnaire.html\">Questionnaire</a> that will support taking <a href=\"questionnaireresponse.html\">QuestionnaireResponse</a> resources generated from the Questionnaire and turning them back into the appropriate resources.</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/StructureDefinition-questionnaire","version":"4.0.1","name":"Build Questionnaire","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Generates a [Questionnaire](questionnaire.html) instance  based on a specified [`StructureDefinition`](structuredefinition.html), creating questions for each core element or extension element found in the [`StructureDefinition`](structuredefinition.html).    \n\nIf the operation is not called at the instance level, one of the *identifier*, *profile* or *url* 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored. The response will contain a [Questionnaire](questionnaire.html) instance based on the specified [`StructureDefinition`](structuredefinition.html) and/or an [`OperationOutcome`](operationoutcome.html) resource with errors or warnings.  Nested groups are used to handle complex structures and data types.  If the 'supportedOnly' parameter is set to true, only those elements marked as \"must support\" will be included.  \n\nThis operation is intended to enable auto-generation of simple interfaces for arbitrary profiles.  The 'questionnaire' approach to data entry has limitations that will make it less optimal than custom-defined interfaces.  However, this function may be useful for simple applications or for systems that wish to support \"non-core\" resources with minimal development effort.","code":"questionnaire","comment":"**Open Issue**: Ideally, extensions should be populated in the generated [Questionnaire](questionnaire.html) that will support taking [QuestionnaireResponse](questionnaireresponse.html) resources generated from the Questionnaire and turning them back into the appropriate resources.","resource":["StructureDefinition"],"system":false,"type":true,"instance":true,"parameter":[{"name":"identifier","use":"in","min":0,"max":"1","documentation":"A logical identifier (i.e. 'StructureDefinition.identifier''). The server must know the `StructureDefinition` or be able to retrieve it from other known repositories.","type":"canonical","targetProfile":["http://hl7.org/fhir/StructureDefinition/StructureDefinition"]},{"name":"profile","use":"in","min":0,"max":"1","documentation":"The [`StructureDefinition`](structuredefinition.html) is provided directly as part of the request. Servers may choose not to accept profiles in this fashion","type":"string","searchType":"token"},{"name":"url","use":"in","min":0,"max":"1","documentation":"The `StructureDefinition`'s official URL (i.e. 'StructureDefinition.url'). The server must know the `StructureDefinition` or be able to retrieve it from other known repositories.","type":"canonical","targetProfile":["http://hl7.org/fhir/StructureDefinition/StructureDefinition"]},{"name":"supportedOnly","use":"in","min":0,"max":"1","documentation":"If true, the questionnaire will only include those elements marked as \"mustSupport='true'\" in the `StructureDefinition`.","type":"boolean"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The questionnaire form generated based on the `StructureDefinition`.","type":"Questionnaire"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A logical identifier (i.e. '`StructureDefinition.identifier`''). The server must know the"]
        #[doc = "`StructureDefinition` or be able to retrieve it from other known repositories."]
        #[parameter_rename = "identifier"]
        pub identifier_: Option<FHIRCanonical>,
        #[doc = "The [`StructureDefinition`](structuredefinition.html) is provided directly as part of the request."]
        #[doc = "Servers may choose not to accept profiles in this fashion"]
        pub profile: Option<FHIRString>,
        #[doc = "The `StructureDefinition`'s official URL (i.e. '`StructureDefinition.url`'). The server must know"]
        #[doc = "the `StructureDefinition` or be able to retrieve it from other known repositories."]
        pub url: Option<FHIRCanonical>,
        #[doc = "If true, the questionnaire will only include those elements marked as \"mustSupport=`true`\" in the"]
        #[doc = "`StructureDefinition`."]
        pub supportedOnly: Option<FHIRBoolean>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The questionnaire form generated based on the `StructureDefinition`."]
        #[parameter_rename = "return"]
        pub return_: Questionnaire,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Questionnaire(value.return_)
        }
    }
}
#[doc = "Generates a [`StructureDefinition`](structuredefinition.html) instance with a snapshot, based on a"]
#[doc = "differential in a specified [`StructureDefinition`](structuredefinition.html)."]
#[doc = ""]
#[doc = "If the operation is not called at the instance level, either *definition* or *url* `in` parameters"]
#[doc = "must be provided. If more than one is specified, servers may raise an error or may resolve with the"]
#[doc = "parameter of their choice. If called at the instance level, these parameters will be ignored."]
pub mod StructureDefinitionSnapshot {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource, StructureDefinition,
    };
    use haste_fhir_model::r4::generated::types::FHIRString;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "snapshot";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"StructureDefinition-snapshot","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Generate Snapshot</h2><p>OPERATION: Generate Snapshot</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/StructureDefinition-snapshot</pre><div><p>Generates a <a href=\"structuredefinition.html\">StructureDefinition</a> instance  with  a snapshot, based on a differential in a specified <a href=\"structuredefinition.html\">StructureDefinition</a>.</p>\n<p>If the operation is not called at the instance level, either <em>definition</em> or <em>url</em> 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored.</p>\n</div><p>URL: [base]/StructureDefinition/$snapshot</p><p>URL: [base]/StructureDefinition/[id]/$snapshot</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>definition</td><td>0..1</td><td><a href=\"structuredefinition.html\">StructureDefinition</a></td><td/><td><div><p>The <a href=\"structuredefinition.html\">StructureDefinition</a> is provided directly as part of the request. Servers may choose not to accept profiles in this fashion</p>\n</div></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a><br/>(<a href=\"search.html#token\">token</a>)</td><td/><td><div><p>The StructureDefinition's canonical URL (i.e. 'StructureDefinition.url'). The server must know the structure definition, or be able to retrieve it from other known repositories.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"structuredefinition.html\">StructureDefinition</a></td><td/><td><div><p>The structure definition with a snapshot</p>\n</div></td></tr></table><div/></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/StructureDefinition-snapshot","version":"4.0.1","name":"Generate Snapshot","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Generates a [`StructureDefinition`](structuredefinition.html) instance  with  a snapshot, based on a differential in a specified [`StructureDefinition`](structuredefinition.html).   \n\nIf the operation is not called at the instance level, either *definition* or *url* 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored.","code":"snapshot","resource":["StructureDefinition"],"system":false,"type":true,"instance":true,"parameter":[{"name":"definition","use":"in","min":0,"max":"1","documentation":"The [`StructureDefinition`](structuredefinition.html) is provided directly as part of the request. Servers may choose not to accept profiles in this fashion","type":"StructureDefinition"},{"name":"url","use":"in","min":0,"max":"1","documentation":"The `StructureDefinition`'s canonical URL (i.e. 'StructureDefinition.url'). The server must know the structure definition, or be able to retrieve it from other known repositories.","type":"string","searchType":"token"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The structure definition with a snapshot","type":"StructureDefinition"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The [`StructureDefinition`](structuredefinition.html) is provided directly as part of the request."]
        #[doc = "Servers may choose not to accept profiles in this fashion"]
        pub definition: Option<StructureDefinition>,
        #[doc = "The `StructureDefinition`'s canonical URL (i.e. '`StructureDefinition.url`'). The server must know"]
        #[doc = "the structure definition, or be able to retrieve it from other known repositories."]
        pub url: Option<FHIRString>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The structure definition with a snapshot"]
        #[parameter_rename = "return"]
        pub return_: StructureDefinition,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::StructureDefinition(value.return_)
        }
    }
}
#[doc = "The transform operation takes input content, applies a structure map transform, and then returns the"]
#[doc = "output."]
pub mod StructureMapTransform {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource,
    };
    use haste_fhir_model::r4::generated::types::FHIRUri;
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "transform";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"StructureMap-transform","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Model Instance Transformation</h2><p>OPERATION: Model Instance Transformation</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/StructureMap-transform</pre><div><p>The transform operation takes input content, applies a structure map transform, and then returns the output.</p>\n</div><p>URL: [base]/StructureMap/$transform</p><p>URL: [base]/StructureMap/[id]/$transform</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>source</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The structure map to apply. This is only needed if the operation is invoked at the resource level. If the $transform operation is invoked on a particular structure map, this will be ignored by the server</p>\n</div></td></tr><tr><td>IN</td><td>content</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The logical content to transform</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"resource.html\">Resource</a></td><td/><td><div><p>The result of the transform</p>\n</div></td></tr></table><div><p>The input and return are specified as 'Resources'. In most usage of the $transform operation, either the input or return content is not a valid FHIR resource. In these cases, the return type is actually a <a href=\"binary.html\">Binary</a> resource. For this operation, the Binary resources may be encoded directly, using a mime-type, as shown in the example. Note: this specification does not yet address the means by which the servers may know the correct mime types for the various content involved</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":2},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"url":"http://hl7.org/fhir/OperationDefinition/StructureMap-transform","version":"4.0.1","name":"Model Instance Transformation","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The transform operation takes input content, applies a structure map transform, and then returns the output.","code":"transform","comment":"The input and return are specified as 'Resources'. In most usage of the $transform operation, either the input or return content is not a valid FHIR resource. In these cases, the return type is actually a [Binary](binary.html) resource. For this operation, the Binary resources may be encoded directly, using a mime-type, as shown in the example. Note: this specification does not yet address the means by which the servers may know the correct mime types for the various content involved","resource":["StructureMap"],"system":false,"type":true,"instance":true,"parameter":[{"name":"source","use":"in","min":0,"max":"1","documentation":"The structure map to apply. This is only needed if the operation is invoked at the resource level. If the $transform operation is invoked on a particular structure map, this will be ignored by the server","type":"uri"},{"name":"content","use":"in","min":1,"max":"1","documentation":"The logical content to transform","type":"Resource"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the transform","type":"Resource"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "The structure map to apply. This is only needed if the operation is invoked at the resource level."]
        #[doc = "If the $transform operation is invoked on a particular structure map, this will be ignored by the"]
        #[doc = "server"]
        pub source: Option<FHIRUri>,
        #[doc = "The logical content to transform"]
        pub content: Resource,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "The result of the transform"]
        #[parameter_rename = "return"]
        pub return_: Resource,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "The definition of a value set is used to create a simple collection of codes suitable for use for"]
#[doc = "data entry or validation."]
#[doc = ""]
#[doc = "If the operation is not called at the instance level, one of the in parameters url, context or"]
#[doc = "valueSet must be provided. An expanded value set will be returned, or an `OperationOutcome` with an"]
#[doc = "error message."]
pub mod ValueSetExpand {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource, ValueSet,
    };
    use haste_fhir_model::r4::generated::types::{
        FHIRBoolean, FHIRCanonical, FHIRCode, FHIRDateTime, FHIRInteger, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "expand";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ValueSet-expand","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Value Set Expansion</h2><p>OPERATION: Value Set Expansion</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ValueSet-expand</pre><div><p>The definition of a value set is used to create a simple collection of codes suitable for use for data entry or validation.</p>\n<p>If the operation is not called at the instance level, one of the in parameters url, context or valueSet must be provided.  An expanded value set will be returned, or an OperationOutcome with an error message.</p>\n</div><p>URL: [base]/ValueSet/$expand</p><p>URL: [base]/ValueSet/[id]/$expand</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>A canonical reference to a value set. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server</p>\n</div></td></tr><tr><td>IN</td><td>valueSet</td><td>0..1</td><td><a href=\"valueset.html\">ValueSet</a></td><td/><td><div><p>The value set is provided directly as part of the request. Servers may choose not to accept value sets in this fashion</p>\n</div></td></tr><tr><td>IN</td><td>valueSetVersion</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The identifier that is used to identify a specific version of the value set to be used when generating the expansion. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.</p>\n</div></td></tr><tr><td>IN</td><td>context</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The context of the value set, so that the server can resolve this to a value set to expand. The recommended format for this URI is [Structure Definition URL]#[name or path into structure definition] e.g. http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation. Other forms may be used but are not defined. This form is only usable if the terminology server also has access to the conformance registry that the server is using, but can be used to delegate the mapping from an application context to a binding at run-time</p>\n</div></td></tr><tr><td>IN</td><td>contextDirection</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>If a context is provided, a context direction may also be provided. Valid values are:</p>\n<ul>\n<li>'incoming': the codes a client can use for PUT/POST operations,  and</li>\n<li>'outgoing', the codes a client might receive from the server.</li>\n</ul>\n<p>The purpose is to inform the server whether to use the value set associated with the context for reading or writing purposes (note: for most elements, this is the same value set, but there are a few elements where the reading and writing value sets are different)</p>\n</div></td></tr><tr><td>IN</td><td>filter</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A text filter that is applied to restrict the codes that are returned (this is useful in a UI context). The interpretation of this is delegated to the server in order to allow to determine the most optimal search approach for the context. The server can document the way this parameter works in <a href=\"terminologycapabilities.html\">TerminologyCapabilities</a>..expansion.textFilter. Typical usage of this parameter includes functionality like:</p>\n<ul>\n<li>using left matching e.g. &quot;acut ast&quot;</li>\n<li>allowing for wild cards such as %, &amp;, ?</li>\n<li>searching on definition as well as display(s)</li>\n<li>allowing for search conditions (and / or / exclusions)</li>\n</ul>\n<p>Text Search engines such as Lucene or Solr, long with their considerable functionality, might also be used. The optional text search might also be code system specific, and servers might have different implementations for different code systems</p>\n</div></td></tr><tr><td>IN</td><td>date</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date for which the expansion should be generated.  if a date is provided, it means that the server should use the value set / code system definitions as they were on the given date, or return an error if this is not possible.  Normally, the date is the current conditions (which is the default value) but under some circumstances, systems need to generate an expansion as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.</p>\n</div></td></tr><tr><td>IN</td><td>offset</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)</p>\n</div></td></tr><tr><td>IN</td><td>count</td><td>0..1</td><td><a href=\"datatypes.html#integer\">integer</a></td><td/><td><div><p>Paging support - how many codes should be provided in a partial page view. Paging only applies to flat expansions - servers ignore paging if the expansion is not flat.  If count = 0, the client is asking how large the expansion is. Servers SHOULD honor this request for hierarchical expansions as well, and simply return the overall count</p>\n</div></td></tr><tr><td>IN</td><td>includeDesignations</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether concept designations are to be included or excluded in value set expansions</p>\n</div></td></tr><tr><td>IN</td><td>designation</td><td>0..*</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A <a href=\"search.html#token\">token</a> that specifies a system+code that is either a use or a language. Designations that match by language or use are included in the expansion. If no designation is specified, it is at the server discretion which designations to return</p>\n</div></td></tr><tr><td>IN</td><td>includeDefinition</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether the value set definition is included or excluded in value set expansions</p>\n</div></td></tr><tr><td>IN</td><td>activeOnly</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether inactive concepts are included or excluded in value set expansions. Note that if the value set explicitly specifies that inactive codes are included, this parameter can still remove them from a specific expansion, but this parameter cannot include them if the value set excludes them</p>\n</div></td></tr><tr><td>IN</td><td>excludeNested</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether or not the value set expansion nests codes or not (i.e. ValueSet.expansion.contains.contains)</p>\n</div></td></tr><tr><td>IN</td><td>excludeNotForUI</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether or not the value set expansion is assembled for a user interface use or not. Value sets intended for User Interface might include <a href=\"codesystem.html#status\">'abstract' codes</a> or have nested contains with items with no code or abstract = true, with the sole purpose of helping a user navigate through the list efficiently, where as a value set not generated for UI use might be flat, and only contain the selectable codes in the value set. The exact implications of 'for UI' depend on the code system, and what properties it exposes for a terminology server to use. In the FHIR Specification itself, the value set expansions are generated with excludeNotForUI = false, and the expansions used when generated schema / code etc, or performing validation, are all excludeNotForUI = true.</p>\n</div></td></tr><tr><td>IN</td><td>excludePostCoordinated</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Controls whether or not the value set expansion includes post coordinated codes</p>\n</div></td></tr><tr><td>IN</td><td>displayLanguage</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Specifies the language to be used for description in the expansions i.e. the language to be used for ValueSet.expansion.contains.display</p>\n</div></td></tr><tr><td>IN</td><td>exclude-system</td><td>0..*</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>Code system, or a particular version of a code system to be excluded from the value set expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56</p>\n</div></td></tr><tr><td>IN</td><td>system-version</td><td>0..*</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>Specifies a version to use for a system, if the value set does not specify which one to use. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56</p>\n</div></td></tr><tr><td>IN</td><td>check-system-version</td><td>0..*</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>Edge Case: Specifies a version to use for a system. If a value set specifies a different version, an error is returned instead of the expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56</p>\n</div></td></tr><tr><td>IN</td><td>force-system-version</td><td>0..*</td><td><a href=\"datatypes.html#canonical\">canonical</a></td><td/><td><div><p>Edge Case: Specifies a version to use for a system. This parameter overrides any specified version in the value set (and any it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the value is override, the version used SHALL explicitly be represented in the expansion parameters</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td>1..1</td><td><a href=\"valueset.html\">ValueSet</a></td><td/><td><div><p>The result of the expansion. Servers generating expansions SHOULD ensure that all the parameters that affect the contents of the expansion are recorded in the ValueSet.expansion.parameter list</p>\n</div></td></tr></table><div><p>The value set expansion returned by this query should be treated as a transient result that will change over time (whether it does or not depends on how the value set is specified), so applications should repeat the operation each time the value set is used.</p>\n<p>If the expansion is too large (at the discretion of the server), the server MAY return an error (OperationOutcome with code too-costly). Clients can work through large flat expansions in a set of pages (partial views of the full expansion) instead of just getting the full expansion in a single exchange by using offset and count parameters, or use the count parameter to request a subset of the expansion for limited purposes. Servers are not obliged to support paging, but if they do, SHALL support both the offset and count parameters. Hierarchical expansions are not subject to paging and servers simply return the entire expansion.</p>\n<p>Different servers may return different results from expanding a value set for the following reasons:</p>\n<ul>\n<li>The underlying code systems are different (e.g. different versions, possibly with different defined behavior)</li>\n<li>The server optimizes filter includes differently, such as sorting by code frequency</li>\n<li>Servers introduce arbitrary groups to assist a user to navigate the lists based either on extensions in the definition, or additional knowledge available to the server</li>\n</ul>\n<p>When a server cannot correctly expand a value set because it does not fully understand the code systems (e.g. it has the wrong version, or incomplete definitions) then it SHALL return an error. If the value set itself is unbounded due to the inclusion of post-coordinated value sets (e.g. SNOMED CT, UCUM), then the extension <a href=\"extension-valueset-unclosed.html\">http://hl7.org/fhir/StructureDefinition/valueset-unclosed</a> can be used to indicate that the expansion is incomplete</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/ValueSet-expand","version":"4.0.1","name":"Value Set Expansion","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"The definition of a value set is used to create a simple collection of codes suitable for use for data entry or validation. \n\nIf the operation is not called at the instance level, one of the in parameters url, context or valueSet must be provided.  An expanded value set will be returned, or an `OperationOutcome` with an error message.","code":"expand","comment":"The value set expansion returned by this query should be treated as a transient result that will change over time (whether it does or not depends on how the value set is specified), so applications should repeat the operation each time the value set is used.  \n\nIf the expansion is too large (at the discretion of the server), the server MAY return an error (OperationOutcome with code too-costly). Clients can work through large flat expansions in a set of pages (partial views of the full expansion) instead of just getting the full expansion in a single exchange by using offset and count parameters, or use the count parameter to request a subset of the expansion for limited purposes. Servers are not obliged to support paging, but if they do, SHALL support both the offset and count parameters. Hierarchical expansions are not subject to paging and servers simply return the entire expansion.  \n\nDifferent servers may return different results from expanding a value set for the following reasons:  \n\n* The underlying code systems are different (e.g. different versions, possibly with different defined behavior) \n* The server optimizes filter includes differently, such as sorting by code frequency \n* Servers introduce arbitrary groups to assist a user to navigate the lists based either on extensions in the definition, or additional knowledge available to the server\n\nWhen a server cannot correctly expand a value set because it does not fully understand the code systems (e.g. it has the wrong version, or incomplete definitions) then it SHALL return an error. If the value set itself is unbounded due to the inclusion of post-coordinated value sets (e.g. SNOMED CT, UCUM), then the extension [http://hl7.org/fhir/StructureDefinition/valueset-unclosed](extension-valueset-unclosed.html) can be used to indicate that the expansion is incomplete","resource":["ValueSet"],"system":false,"type":true,"instance":true,"parameter":[{"name":"url","use":"in","min":0,"max":"1","documentation":"A canonical reference to a value set. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server","type":"uri"},{"name":"valueSet","use":"in","min":0,"max":"1","documentation":"The value set is provided directly as part of the request. Servers may choose not to accept value sets in this fashion","type":"ValueSet"},{"name":"valueSetVersion","use":"in","min":0,"max":"1","documentation":"The identifier that is used to identify a specific version of the value set to be used when generating the expansion. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.","type":"string"},{"name":"context","use":"in","min":0,"max":"1","documentation":"The context of the value set, so that the server can resolve this to a value set to expand. The recommended format for this URI is [Structure Definition URL]#[name or path into structure definition] e.g. <http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation>. Other forms may be used but are not defined. This form is only usable if the terminology server also has access to the conformance registry that the server is using, but can be used to delegate the mapping from an application context to a binding at run-time","type":"uri"},{"name":"contextDirection","use":"in","min":0,"max":"1","documentation":"If a context is provided, a context direction may also be provided. Valid values are: \n\n* 'incoming': the codes a client can use for PUT/POST operations,  and \n* 'outgoing', the codes a client might receive from the server.\n\nThe purpose is to inform the server whether to use the value set associated with the context for reading or writing purposes (note: for most elements, this is the same value set, but there are a few elements where the reading and writing value sets are different)","type":"code"},{"name":"filter","use":"in","min":0,"max":"1","documentation":"A text filter that is applied to restrict the codes that are returned (this is useful in a UI context). The interpretation of this is delegated to the server in order to allow to determine the most optimal search approach for the context. The server can document the way this parameter works in [`TerminologyCapabilities`](terminologycapabilities.html)..expansion.textFilter. Typical usage of this parameter includes functionality like:\n\n* using left matching e.g. \"acut ast\"\n* allowing for wild cards such as %, &, ?\n* searching on definition as well as display(s)\n* allowing for search conditions (and / or / exclusions)\n\nText Search engines such as Lucene or Solr, long with their considerable functionality, might also be used. The optional text search might also be code system specific, and servers might have different implementations for different code systems","type":"string"},{"name":"date","use":"in","min":0,"max":"1","documentation":"The date for which the expansion should be generated.  if a date is provided, it means that the server should use the value set / code system definitions as they were on the given date, or return an error if this is not possible.  Normally, the date is the current conditions (which is the default value) but under some circumstances, systems need to generate an expansion as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.","type":"dateTime"},{"name":"offset","use":"in","min":0,"max":"1","documentation":"Paging support - where to start if a subset is desired (default = 0). Offset is number of records (not number of pages)","type":"integer"},{"name":"count","use":"in","min":0,"max":"1","documentation":"Paging support - how many codes should be provided in a partial page view. Paging only applies to flat expansions - servers ignore paging if the expansion is not flat.  If count = 0, the client is asking how large the expansion is. Servers SHOULD honor this request for hierarchical expansions as well, and simply return the overall count","type":"integer"},{"name":"includeDesignations","use":"in","min":0,"max":"1","documentation":"Controls whether concept designations are to be included or excluded in value set expansions","type":"boolean"},{"name":"designation","use":"in","min":0,"max":"*","documentation":"A [token](search.html#token) that specifies a system+code that is either a use or a language. Designations that match by language or use are included in the expansion. If no designation is specified, it is at the server discretion which designations to return","type":"string"},{"name":"includeDefinition","use":"in","min":0,"max":"1","documentation":"Controls whether the value set definition is included or excluded in value set expansions","type":"boolean"},{"name":"activeOnly","use":"in","min":0,"max":"1","documentation":"Controls whether inactive concepts are included or excluded in value set expansions. Note that if the value set explicitly specifies that inactive codes are included, this parameter can still remove them from a specific expansion, but this parameter cannot include them if the value set excludes them","type":"boolean"},{"name":"excludeNested","use":"in","min":0,"max":"1","documentation":"Controls whether or not the value set expansion nests codes or not (i.e. ValueSet.expansion.contains.contains)","type":"boolean"},{"name":"excludeNotForUI","use":"in","min":0,"max":"1","documentation":"Controls whether or not the value set expansion is assembled for a user interface use or not. Value sets intended for User Interface might include ['abstract' codes](codesystem.html#status) or have nested contains with items with no code or abstract = true, with the sole purpose of helping a user navigate through the list efficiently, where as a value set not generated for UI use might be flat, and only contain the selectable codes in the value set. The exact implications of 'for UI' depend on the code system, and what properties it exposes for a terminology server to use. In the FHIR Specification itself, the value set expansions are generated with excludeNotForUI = false, and the expansions used when generated schema / code etc, or performing validation, are all excludeNotForUI = true.","type":"boolean"},{"name":"excludePostCoordinated","use":"in","min":0,"max":"1","documentation":"Controls whether or not the value set expansion includes post coordinated codes","type":"boolean"},{"name":"displayLanguage","use":"in","min":0,"max":"1","documentation":"Specifies the language to be used for description in the expansions i.e. the language to be used for ValueSet.expansion.contains.display","type":"code"},{"name":"exclude-system","use":"in","min":0,"max":"*","documentation":"Code system, or a particular version of a code system to be excluded from the value set expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56","type":"canonical"},{"name":"system-version","use":"in","min":0,"max":"*","documentation":"Specifies a version to use for a system, if the value set does not specify which one to use. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56","type":"canonical"},{"name":"check-system-version","use":"in","min":0,"max":"*","documentation":"Edge Case: Specifies a version to use for a system. If a value set specifies a different version, an error is returned instead of the expansion. The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56","type":"canonical"},{"name":"force-system-version","use":"in","min":0,"max":"*","documentation":"Edge Case: Specifies a version to use for a system. This parameter overrides any specified version in the value set (and any it depends on). The format is the same as a canonical URL: [system]|[version] - e.g. http://loinc.org|2.56. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal with situations where specifications have fallen into decay as time passes. If the value is override, the version used SHALL explicitly be represented in the expansion parameters","type":"canonical"},{"name":"return","use":"out","min":1,"max":"1","documentation":"The result of the expansion. Servers generating expansions SHOULD ensure that all the parameters that affect the contents of the expansion are recorded in the ValueSet.expansion.parameter list","type":"ValueSet"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "A canonical reference to a value set. The server must know the value set (e.g. it is defined"]
        #[doc = "explicitly in the server's value sets, or it is defined implicitly by some code system known to the"]
        #[doc = "server"]
        pub url: Option<FHIRUri>,
        #[doc = "The value set is provided directly as part of the request. Servers may choose not to accept value"]
        #[doc = "sets in this fashion"]
        pub valueSet: Option<ValueSet>,
        #[doc = "The identifier that is used to identify a specific version of the value set to be used when"]
        #[doc = "generating the expansion. This is an arbitrary value managed by the value set author and is not"]
        #[doc = "expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed"]
        #[doc = "version is not available."]
        pub valueSetVersion: Option<FHIRString>,
        #[doc = "The context of the value set, so that the server can resolve this to a value set to expand. The"]
        #[doc = "recommended format for this URI is [Structure Definition URL]#[name or path into structure"]
        #[doc = "definition] e.g."]
        #[doc = "<`http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation>`."]
        #[doc = "Other forms may be used but are not defined. This form is only usable if the terminology server also"]
        #[doc = "has access to the conformance registry that the server is using, but can be used to delegate the"]
        #[doc = "mapping from an application context to a binding at run-time"]
        pub context: Option<FHIRUri>,
        #[doc = "If a context is provided, a context direction may also be provided. Valid values are:"]
        #[doc = ""]
        #[doc = "* `incoming`: the codes a client can use for PUT/POST operations, and"]
        #[doc = "* `outgoing`, the codes a client might receive from the server."]
        #[doc = ""]
        #[doc = "The purpose is to inform the server whether to use the value set associated with the context for"]
        #[doc = "reading or writing purposes (note: for most elements, this is the same value set, but there are a"]
        #[doc = "few elements where the reading and writing value sets are different)"]
        pub contextDirection: Option<FHIRCode>,
        #[doc = "A text filter that is applied to restrict the codes that are returned (this is useful in a UI"]
        #[doc = "context). The interpretation of this is delegated to the server in order to allow to determine the"]
        #[doc = "most optimal search approach for the context. The server can document the way this parameter works"]
        #[doc = "in [`TerminologyCapabilities`](terminologycapabilities.html)..expansion.textFilter. Typical usage of"]
        #[doc = "this parameter includes functionality like:"]
        #[doc = ""]
        #[doc = "* using left matching e.g. \"acut ast\""]
        #[doc = "* allowing for wild cards such as %, &, ?"]
        #[doc = "* searching on definition as well as display(s)"]
        #[doc = "* allowing for search conditions (and / or / exclusions)"]
        #[doc = ""]
        #[doc = "Text Search engines such as Lucene or Solr, long with their considerable functionality, might also"]
        #[doc = "be used. The optional text search might also be code system specific, and servers might have"]
        #[doc = "different implementations for different code systems"]
        pub filter: Option<FHIRString>,
        #[doc = "The date for which the expansion should be generated. if a date is provided, it means that the"]
        #[doc = "server should use the value set / code system definitions as they were on the given date, or return"]
        #[doc = "an error if this is not possible. Normally, the date is the current conditions (which is the default"]
        #[doc = "value) but under some circumstances, systems need to generate an expansion as it would have been in"]
        #[doc = "the past. A typical example of this would be where code selection is constrained to the set of codes"]
        #[doc = "that were available when the patient was treated, not when the record is being edited. Note that"]
        #[doc = "which date is appropriate is a matter for implementation policy."]
        pub date: Option<FHIRDateTime>,
        #[doc = "Paging support - where to start if a subset is desired (default = 0). Offset is number of records"]
        #[doc = "(not number of pages)"]
        pub offset: Option<FHIRInteger>,
        #[doc = "Paging support - how many codes should be provided in a partial page view. Paging only applies to"]
        #[doc = "flat expansions - servers ignore paging if the expansion is not flat. If count = 0, the client is"]
        #[doc = "asking how large the expansion is. Servers SHOULD honor this request for hierarchical expansions as"]
        #[doc = "well, and simply return the overall count"]
        pub count: Option<FHIRInteger>,
        #[doc = "Controls whether concept designations are to be included or excluded in value set expansions"]
        pub includeDesignations: Option<FHIRBoolean>,
        #[doc = "A [`token`](search.html#token) that specifies a system+code that is either a use or a language."]
        #[doc = "Designations that match by language or use are included in the expansion. If no designation is"]
        #[doc = "specified, it is at the server discretion which designations to return"]
        pub designation: Option<Vec<FHIRString>>,
        #[doc = "Controls whether the value set definition is included or excluded in value set expansions"]
        pub includeDefinition: Option<FHIRBoolean>,
        #[doc = "Controls whether inactive concepts are included or excluded in value set expansions. Note that if"]
        #[doc = "the value set explicitly specifies that inactive codes are included, this parameter can still remove"]
        #[doc = "them from a specific expansion, but this parameter cannot include them if the value set excludes"]
        #[doc = "them"]
        pub activeOnly: Option<FHIRBoolean>,
        #[doc = "Controls whether or not the value set expansion nests codes or not (i.e."]
        #[doc = "`ValueSet.expansion.contains.contains`)"]
        pub excludeNested: Option<FHIRBoolean>,
        #[doc = "Controls whether or not the value set expansion is assembled for a user interface use or not. Value"]
        #[doc = "sets intended for User Interface might include [``abstract` codes`](codesystem.html#status) or have"]
        #[doc = "nested contains with items with no code or abstract = true, with the sole purpose of helping a user"]
        #[doc = "navigate through the list efficiently, where as a value set not generated for UI use might be flat,"]
        #[doc = "and only contain the selectable codes in the value set. The exact implications of 'for UI' depend on"]
        #[doc = "the code system, and what properties it exposes for a terminology server to use. In the FHIR"]
        #[doc = "Specification itself, the value set expansions are generated with exclude`NotForUI` = false, and the"]
        #[doc = "expansions used when generated schema / code etc, or performing validation, are all"]
        #[doc = "exclude`NotForUI` = true."]
        pub excludeNotForUI: Option<FHIRBoolean>,
        #[doc = "Controls whether or not the value set expansion includes post coordinated codes"]
        pub excludePostCoordinated: Option<FHIRBoolean>,
        #[doc = "Specifies the language to be used for description in the expansions i.e. the language to be used for"]
        #[doc = "`ValueSet.expansion.contains.display`"]
        pub displayLanguage: Option<FHIRCode>,
        #[doc = "Code system, or a particular version of a code system to be excluded from the value set expansion."]
        #[doc = "The format is the same as a canonical URL: `[system]|[version] - e.g. http://loinc.org|2.56`"]
        #[parameter_rename = "exclude-system"]
        pub exclude_system: Option<Vec<FHIRCanonical>>,
        #[doc = "Specifies a version to use for a system, if the value set does not specify which one to use. The"]
        #[doc = "format is the same as a canonical URL: `[system]|[version] - e.g. http://loinc.org|2.56`"]
        #[parameter_rename = "system-version"]
        pub system_version: Option<Vec<FHIRCanonical>>,
        #[doc = "Edge Case: Specifies a version to use for a system. If a value set specifies a different version, an"]
        #[doc = "error is returned instead of the expansion. The format is the same as a canonical URL:"]
        #[doc = "`[system]|[version] - e.g. http://loinc.org|2.56`"]
        #[parameter_rename = "check-system-version"]
        pub check_system_version: Option<Vec<FHIRCanonical>>,
        #[doc = "Edge Case: Specifies a version to use for a system. This parameter overrides any specified version"]
        #[doc = "in the value set (and any it depends on). The format is the same as a canonical URL:"]
        #[doc = "`[system]|[version] - e.g. http://loinc.org|2.56`. Note that this has obvious safety issues, in that"]
        #[doc = "it may result in a value set expansion giving a different list of codes that is both wrong and"]
        #[doc = "unsafe, and implementers should only use this capability reluctantly. It primarily exists to deal"]
        #[doc = "with situations where specifications have fallen into decay as time passes. If the value is"]
        #[doc = "override, the version used SHALL explicitly be represented in the expansion parameters"]
        #[parameter_rename = "force-system-version"]
        pub force_system_version: Option<Vec<FHIRCanonical>>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "The result of the expansion. Servers generating expansions SHOULD ensure that all the parameters"]
        #[doc = "that affect the contents of the expansion are recorded in the `ValueSet.expansion.parameter` list"]
        #[parameter_rename = "return"]
        pub return_: ValueSet,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::ValueSet(value.return_)
        }
    }
}
#[doc = "Validate that a coded value is in the set of codes allowed by a value set."]
#[doc = ""]
#[doc = "If the operation is not called at the instance level, one of the in parameters url, context or"]
#[doc = "valueSet must be provided. One (and only one) of the in parameters code, coding, or codeableConcept"]
#[doc = "must be provided. The operation returns a result (true / false), an error message, and the"]
#[doc = "recommended display for the code"]
pub mod ValueSetValidateCode {
    use haste_fhir_model::r4::generated::resources::{
        OperationDefinition, Parameters, ParametersParameter, Resource, ValueSet,
    };
    use haste_fhir_model::r4::generated::types::{
        CodeableConcept, Coding, FHIRBoolean, FHIRCode, FHIRDateTime, FHIRString, FHIRUri,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "validate-code";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ValueSet-validate-code","meta":{"lastUpdated":"2019-10-31T22:29:23.356+00:00"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Value Set based Validation</h2><p>OPERATION: Value Set based Validation</p><p>The official URL for this operation definition is: </p><pre>http://hl7.org/fhir/OperationDefinition/ValueSet-validate-code</pre><div><p>Validate that a coded value is in the set of codes allowed by a value set.</p>\n<p>If the operation is not called at the instance level, one of the in parameters url, context or  valueSet must be provided.  One (and only one) of the in parameters code, coding, or codeableConcept must be provided.  The operation returns a result (true / false), an error message, and the recommended display for the code</p>\n</div><p>URL: [base]/ValueSet/$validate-code</p><p>URL: [base]/ValueSet/[id]/$validate-code</p><p>Parameters</p><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>url</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>Value set Canonical URL. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server</p>\n</div></td></tr><tr><td>IN</td><td>context</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The context of the value set, so that the server can resolve this to a value set to validate against. The recommended format for this URI is [Structure Definition URL]#[name or path into structure definition] e.g. http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation. Other forms may be used but are not defined. This form is only usable if the terminology server also has access to the conformance registry that the server is using, but can be used to delegate the mapping from an application context to a binding at run-time</p>\n</div></td></tr><tr><td>IN</td><td>valueSet</td><td>0..1</td><td><a href=\"valueset.html\">ValueSet</a></td><td/><td><div><p>The value set is provided directly as part of the request. Servers may choose not to accept value sets in this fashion. This parameter is used when the client wants the server to expand a value set that is not stored on the server</p>\n</div></td></tr><tr><td>IN</td><td>valueSetVersion</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The identifier that is used to identify a specific version of the value set to be used when validating the code. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.</p>\n</div></td></tr><tr><td>IN</td><td>code</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>The code that is to be validated. If a code is provided, a system or a context must be provided (if a context is provided, then the server SHALL ensure that the code is not ambiguous without a system)</p>\n</div></td></tr><tr><td>IN</td><td>system</td><td>0..1</td><td><a href=\"datatypes.html#uri\">uri</a></td><td/><td><div><p>The system for the code that is to be validated</p>\n</div></td></tr><tr><td>IN</td><td>systemVersion</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The version of the system, if one was provided in the source data</p>\n</div></td></tr><tr><td>IN</td><td>display</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name using the display parameter in the outcome. Whether displays are case sensitive is code system dependent</p>\n</div></td></tr><tr><td>IN</td><td>coding</td><td>0..1</td><td><a href=\"datatypes.html#Coding\">Coding</a></td><td/><td><div><p>A coding to validate</p>\n</div></td></tr><tr><td>IN</td><td>codeableConcept</td><td>0..1</td><td><a href=\"datatypes.html#CodeableConcept\">CodeableConcept</a></td><td/><td><div><p>A full codeableConcept to validate. The server returns true if one of the coding values is in the value set, and may also validate that the codings are not in conflict with each other if more than one is present</p>\n</div></td></tr><tr><td>IN</td><td>date</td><td>0..1</td><td><a href=\"datatypes.html#dateTime\">dateTime</a></td><td/><td><div><p>The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.</p>\n</div></td></tr><tr><td>IN</td><td>abstract</td><td>0..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is false, abstract codes are not considered to be valid.</p>\n<p>Note that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in an actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.</p>\n</div></td></tr><tr><td>IN</td><td>displayLanguage</td><td>0..1</td><td><a href=\"datatypes.html#code\">code</a></td><td/><td><div><p>Specifies the language to be used for description when validating the display property</p>\n</div></td></tr><tr><td>OUT</td><td>result</td><td>1..1</td><td><a href=\"datatypes.html#boolean\">boolean</a></td><td/><td><div><p>True if the concept details supplied are valid</p>\n</div></td></tr><tr><td>OUT</td><td>message</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>Error details, if result = false. If this is provided when result = true, the message carries hints and warnings</p>\n</div></td></tr><tr><td>OUT</td><td>display</td><td>0..1</td><td><a href=\"datatypes.html#string\">string</a></td><td/><td><div><p>A valid display for the concept if the system wishes to display this to a user</p>\n</div></td></tr></table><div><p>Note: the correct behaviour of validation with regard to language for Coding.display items is currently undefined, and further development and testing may lead to specific requirements or recommendations in subsequent releases</p>\n</div></div>"},"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm","valueInteger":5},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"normative"},{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-normative-version","valueCode":"4.0.1"}],"url":"http://hl7.org/fhir/OperationDefinition/ValueSet-validate-code","version":"4.0.1","name":"Value Set based Validation","status":"draft","kind":"operation","date":"2019-10-31T22:29:23+00:00","publisher":"HL7 (FHIR Project)","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"},{"system":"email","value":"fhir@lists.hl7.org"}]}],"description":"Validate that a coded value is in the set of codes allowed by a value set.\n\nIf the operation is not called at the instance level, one of the in parameters url, context or  valueSet must be provided.  One (and only one) of the in parameters code, coding, or codeableConcept must be provided.  The operation returns a result (true / false), an error message, and the recommended display for the code","code":"validate-code","comment":"Note: the correct behaviour of validation with regard to language for Coding.display items is currently undefined, and further development and testing may lead to specific requirements or recommendations in subsequent releases","resource":["ValueSet"],"system":false,"type":true,"instance":true,"parameter":[{"name":"url","use":"in","min":0,"max":"1","documentation":"Value set Canonical URL. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server","type":"uri"},{"name":"context","use":"in","min":0,"max":"1","documentation":"The context of the value set, so that the server can resolve this to a value set to validate against. The recommended format for this URI is [Structure Definition URL]#[name or path into structure definition] e.g. <http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation>. Other forms may be used but are not defined. This form is only usable if the terminology server also has access to the conformance registry that the server is using, but can be used to delegate the mapping from an application context to a binding at run-time","type":"uri"},{"name":"valueSet","use":"in","min":0,"max":"1","documentation":"The value set is provided directly as part of the request. Servers may choose not to accept value sets in this fashion. This parameter is used when the client wants the server to expand a value set that is not stored on the server","type":"ValueSet"},{"name":"valueSetVersion","use":"in","min":0,"max":"1","documentation":"The identifier that is used to identify a specific version of the value set to be used when validating the code. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.","type":"string"},{"name":"code","use":"in","min":0,"max":"1","documentation":"The code that is to be validated. If a code is provided, a system or a context must be provided (if a context is provided, then the server SHALL ensure that the code is not ambiguous without a system)","type":"code"},{"name":"system","use":"in","min":0,"max":"1","documentation":"The system for the code that is to be validated","type":"uri"},{"name":"systemVersion","use":"in","min":0,"max":"1","documentation":"The version of the system, if one was provided in the source data","type":"string"},{"name":"display","use":"in","min":0,"max":"1","documentation":"The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name using the display parameter in the outcome. Whether displays are case sensitive is code system dependent","type":"string"},{"name":"coding","use":"in","min":0,"max":"1","documentation":"A coding to validate","type":"Coding"},{"name":"codeableConcept","use":"in","min":0,"max":"1","documentation":"A full codeableConcept to validate. The server returns true if one of the coding values is in the value set, and may also validate that the codings are not in conflict with each other if more than one is present","type":"CodeableConcept"},{"name":"date","use":"in","min":0,"max":"1","documentation":"The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.","type":"dateTime"},{"name":"abstract","use":"in","min":0,"max":"1","documentation":"If this parameter has a value of true, the client is stating that the validation is being performed in a context where a concept designated as 'abstract' is appropriate/allowed to be used, and the server should regard abstract codes as valid. If this parameter is false, abstract codes are not considered to be valid.\n\nNote that. 'abstract' is a property defined by many HL7 code systems that indicates that the concept is a logical grouping concept that is not intended to be used asa 'concrete' concept to in an actual patient/care/process record. This language is borrowed from Object Orienated theory where 'asbtract' objects are never instantiated. However in the general record and terminology eco-system, there are many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when editing value sets themselves. This parameter allows a client to indicate to the server that it is working in such a context.","type":"boolean"},{"name":"displayLanguage","use":"in","min":0,"max":"1","documentation":"Specifies the language to be used for description when validating the display property","type":"code"},{"name":"result","use":"out","min":1,"max":"1","documentation":"True if the concept details supplied are valid","type":"boolean"},{"name":"message","use":"out","min":0,"max":"1","documentation":"Error details, if result = false. If this is provided when result = true, the message carries hints and warnings","type":"string"},{"name":"display","use":"out","min":0,"max":"1","documentation":"A valid display for the concept if the system wishes to display this to a user","type":"string"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Value set Canonical URL. The server must know the value set (e.g. it is defined explicitly in the"]
        #[doc = "server's value sets, or it is defined implicitly by some code system known to the server"]
        pub url: Option<FHIRUri>,
        #[doc = "The context of the value set, so that the server can resolve this to a value set to validate"]
        #[doc = "against. The recommended format for this URI is [Structure Definition URL]#[name or path into"]
        #[doc = "structure definition] e.g."]
        #[doc = "<`http://hl7.org/fhir/StructureDefinition/observation-hspc-height-hspcheight#Observation.interpretation>`."]
        #[doc = "Other forms may be used but are not defined. This form is only usable if the terminology server also"]
        #[doc = "has access to the conformance registry that the server is using, but can be used to delegate the"]
        #[doc = "mapping from an application context to a binding at run-time"]
        pub context: Option<FHIRUri>,
        #[doc = "The value set is provided directly as part of the request. Servers may choose not to accept value"]
        #[doc = "sets in this fashion. This parameter is used when the client wants the server to expand a value set"]
        #[doc = "that is not stored on the server"]
        pub valueSet: Option<ValueSet>,
        #[doc = "The identifier that is used to identify a specific version of the value set to be used when"]
        #[doc = "validating the code. This is an arbitrary value managed by the value set author and is not expected"]
        #[doc = "to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is"]
        #[doc = "not available."]
        pub valueSetVersion: Option<FHIRString>,
        #[doc = "The code that is to be validated. If a code is provided, a system or a context must be provided (if"]
        #[doc = "a context is provided, then the server SHALL ensure that the code is not ambiguous without a system)"]
        pub code: Option<FHIRCode>,
        #[doc = "The system for the code that is to be validated"]
        pub system: Option<FHIRUri>,
        #[doc = "The version of the system, if one was provided in the source data"]
        pub systemVersion: Option<FHIRString>,
        #[doc = "The display associated with the code, if provided. If a display is provided a code must be provided."]
        #[doc = "If no display is provided, the server cannot validate the display value, but may choose to return a"]
        #[doc = "recommended display name using the display parameter in the outcome. Whether displays are case"]
        #[doc = "sensitive is code system dependent"]
        pub display: Option<FHIRString>,
        #[doc = "A coding to validate"]
        pub coding: Option<Coding>,
        #[doc = "A full codeableConcept to validate. The server returns true if one of the coding values is in the"]
        #[doc = "value set, and may also validate that the codings are not in conflict with each other if more than"]
        #[doc = "one is present"]
        pub codeableConcept: Option<CodeableConcept>,
        #[doc = "The date for which the validation should be checked. Normally, this is the current conditions (which"]
        #[doc = "is the default values) but under some circumstances, systems need to validate that a correct code"]
        #[doc = "was used at some point in the past. A typical example of this would be where code selection is"]
        #[doc = "constrained to the set of codes that were available when the patient was treated, not when the"]
        #[doc = "record is being edited. Note that which date is appropriate is a matter for implementation policy."]
        pub date: Option<FHIRDateTime>,
        #[doc = "If this parameter has a value of true, the client is stating that the validation is being performed"]
        #[doc = "in a context where a concept designated as `abstract` is appropriate/allowed to be used, and the"]
        #[doc = "server should regard abstract codes as valid. If this parameter is false, abstract codes are not"]
        #[doc = "considered to be valid."]
        #[doc = ""]
        #[doc = "Note that. `abstract` is a property defined by many HL7 code systems that indicates that the concept"]
        #[doc = "is a logical grouping concept that is not intended to be used asa `concrete` concept to in an actual"]
        #[doc = "patient/care/process record. This language is borrowed from Object Orienated theory where `asbtract`"]
        #[doc = "objects are never instantiated. However in the general record and terminology eco-system, there are"]
        #[doc = "many contexts where it is appropraite to use these codes e.g. as decision making criterion, or when"]
        #[doc = "editing value sets themselves. This parameter allows a client to indicate to the server that it is"]
        #[doc = "working in such a context."]
        #[parameter_rename = "abstract"]
        pub abstract_: Option<FHIRBoolean>,
        #[doc = "Specifies the language to be used for description when validating the display property"]
        pub displayLanguage: Option<FHIRCode>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Output {
        #[doc = "True if the concept details supplied are valid"]
        pub result: FHIRBoolean,
        #[doc = "Error details, if result = false. If this is provided when result = true, the message carries hints"]
        #[doc = "and warnings"]
        pub message: Option<FHIRString>,
        #[doc = "A valid display for the concept if the system wishes to display this to a user"]
        pub display: Option<FHIRString>,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
}
#[doc = "Execute a view definition against supplied or server data."]
pub mod ViewDefinitionRun {
    use haste_fhir_model::r4::generated::resources::{
        Binary, OperationDefinition, Parameters, ParametersParameter, Resource, ViewDefinition,
    };
    use haste_fhir_model::r4::generated::types::{
        FHIRBoolean, FHIRCode, FHIRInstant, FHIRInteger, FHIRString, Reference,
    };
    use haste_fhir_operation_error::OperationOutcomeError;
    use haste_fhir_ops::derive::{FromParameters, ToParameters};
    use std::sync::LazyLock;
    pub const CODE: &str = "viewdefinition-run";
    const OPERATION_DEFINITION_JSON: &str = r#"{"resourceType":"OperationDefinition","id":"ViewDefinitionRun","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: OperationDefinition ViewDefinitionRun</b></p><a name=\"ViewDefinitionRun\"> </a><a name=\"hcViewDefinitionRun\"> </a><p>URL: [base]/$viewdefinition-run</p><p>URL: [base]/CanonicalResource/$viewdefinition-run</p><p>URL: [base]/CanonicalResource/[id]/$viewdefinition-run</p><h3>Parameters</h3><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>_format</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#code\">code</a></td><td><a href=\"ValueSet-OutputFormatCodes.html\">Output Format Codes</a> (Extensible)</td><td><div><p>Output format for the result (for example json, ndjson, csv, parquet). Optional; if omitted, the server returns ndjson by default.</p>\n</div></td></tr><tr><td>IN</td><td>header</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#boolean\">boolean</a></td><td/><td><div><p>Include CSV headers (default true). Applies only when csv output is requested.</p>\n</div></td></tr><tr><td>IN</td><td>viewReference</td><td>system, type</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/references.html#Reference\">Reference</a></td><td/><td><div><p>Reference to a ViewDefinition stored on the server.</p>\n</div></td></tr><tr><td>IN</td><td>viewResource</td><td>system, type</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/canonicalresource.html\">CanonicalResource</a> (<a href=\"StructureDefinition-ViewDefinition.html\" title=\"https://sql-on-fhir.org/ig/StructureDefinition/ViewDefinition\">View Definition</a>)</td><td/><td><div><p>Inline ViewDefinition resource to execute.</p>\n</div></td></tr><tr><td>IN</td><td>patient</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/references.html#Reference\">Reference</a></td><td/><td><div><p>Restrict execution to the specified patient.</p>\n</div></td></tr><tr><td>IN</td><td>group</td><td>system, type, instance</td><td>0..*</td><td><a href=\"http://hl7.org/fhir/R5/references.html#Reference\">Reference</a></td><td/><td><div><p>Restrict execution to members of the given group(s).</p>\n</div></td></tr><tr><td>IN</td><td>source</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#string\">string</a></td><td/><td><div><p>External data source to use (for example a URI or bucket name).</p>\n</div></td></tr><tr><td>IN</td><td>resource</td><td>system, type, instance</td><td>0..*</td><td><a href=\"http://hl7.org/fhir/R5/resource.html\">Resource</a></td><td/><td><div><p>FHIR resources to transform instead of using server data.</p>\n</div></td></tr><tr><td>IN</td><td>_limit</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#integer\">integer</a></td><td/><td><div><p>Maximum number of rows to return.</p>\n</div></td></tr><tr><td>IN</td><td>_since</td><td>system, type, instance</td><td>0..1</td><td><a href=\"http://hl7.org/fhir/R5/datatypes.html#instant\">instant</a></td><td/><td><div><p>Include only resources modified after this instant.</p>\n</div></td></tr><tr><td>OUT</td><td>return</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R5/binary.html\">Binary</a></td><td/><td><div><p>Transformed data encoded in the requested output format.</p>\n</div></td></tr></table></div>"},"url":"http://sql-on-fhir.org/OperationDefinition/$viewdefinition-run","version":"2.1.0-pre","name":"ViewDefinitionRun","title":"ViewDefinition Run","status":"active","kind":"operation","date":"2026-05-21T08:53:46+00:00","publisher":"SQL on FHIR Working Group","contact":[{"name":"SQL on FHIR Working Group","telecom":[{"system":"url","value":"https://sql-on-fhir.org"}]}],"description":"Execute a view definition against supplied or server data.","jurisdiction":[{"coding":[{"system":"http://unstats.un.org/unsd/methods/m49/m49.htm","code":"001","display":"World"}]}],"code":"viewdefinition-run","resource":["ViewDefinition"],"system":true,"type":true,"instance":true,"parameter":[{"name":"_format","use":"in","min":0,"max":"1","documentation":"Output format for the result (for example json, ndjson, csv, parquet). Optional; if omitted, the server returns ndjson by default.","type":"code","binding":{"strength":"extensible","valueSet":"https://sql-on-fhir.org/ig/ValueSet/OutputFormatCodes"}},{"name":"header","use":"in","min":0,"max":"1","documentation":"Include CSV headers (default true). Applies only when csv output is requested.","type":"boolean"},{"name":"viewReference","use":"in","min":0,"max":"1","documentation":"Reference to a ViewDefinition stored on the server.","type":"Reference"},{"name":"viewResource","use":"in","min":0,"max":"1","documentation":"Inline ViewDefinition resource to execute.","type":"ViewDefinition","targetProfile":["https://sql-on-fhir.org/ig/StructureDefinition/ViewDefinition"]},{"name":"patient","use":"in","min":0,"max":"1","documentation":"Restrict execution to the specified patient.","type":"Reference"},{"name":"group","use":"in","min":0,"max":"*","documentation":"Restrict execution to members of the given group(s).","type":"Reference"},{"name":"source","use":"in","min":0,"max":"1","documentation":"External data source to use (for example a URI or bucket name).","type":"string"},{"name":"resource","use":"in","min":0,"max":"*","documentation":"FHIR resources to transform instead of using server data.","type":"Resource"},{"name":"_limit","use":"in","min":0,"max":"1","documentation":"Maximum number of rows to return.","type":"integer"},{"name":"_since","use":"in","min":0,"max":"1","documentation":"Include only resources modified after this instant.","type":"instant"},{"name":"return","use":"out","min":1,"max":"1","documentation":"Transformed data encoded in the requested output format.","type":"Binary"}]}"#;
    #[doc = "The `OperationDefinition` this module was generated from."]
    pub static OPERATION_DEFINITION: LazyLock<OperationDefinition> = LazyLock::new(|| {
        serde_json::from_str(OPERATION_DEFINITION_JSON)
            .expect("Generated OperationDefinition JSON must deserialize.")
    });
    #[derive(Debug, FromParameters, ToParameters)]
    pub struct Input {
        #[doc = "Output format for the result (for example json, ndjson, csv, parquet). Optional; if omitted, the"]
        #[doc = "server returns ndjson by default."]
        #[parameter_rename = "_format"]
        pub format: Option<FHIRCode>,
        #[doc = "Include CSV headers (default true). Applies only when csv output is requested."]
        pub header: Option<FHIRBoolean>,
        #[doc = "Reference to a `ViewDefinition` stored on the server."]
        pub viewReference: Option<Reference>,
        #[doc = "Inline `ViewDefinition` resource to execute."]
        pub viewResource: Option<ViewDefinition>,
        #[doc = "Restrict execution to the specified patient."]
        pub patient: Option<Reference>,
        #[doc = "Restrict execution to members of the given group(s)."]
        pub group: Option<Vec<Reference>>,
        #[doc = "External data source to use (for example a URI or bucket name)."]
        pub source: Option<FHIRString>,
        #[doc = "FHIR resources to transform instead of using server data."]
        pub resource: Option<Vec<Resource>>,
        #[doc = "Maximum number of rows to return."]
        #[parameter_rename = "_limit"]
        pub limit: Option<FHIRInteger>,
        #[doc = "Include only resources modified after this instant."]
        #[parameter_rename = "_since"]
        pub since: Option<FHIRInstant>,
    }
    impl From<Input> for Resource {
        fn from(value: Input) -> Self {
            let parameters: Vec<ParametersParameter> = value.into();
            Resource::Parameters(Parameters {
                parameter: Some(parameters),
                ..Default::default()
            })
        }
    }
    #[derive(Debug, FromParameters)]
    pub struct Output {
        #[doc = "Transformed data encoded in the requested output format."]
        #[parameter_rename = "return"]
        pub return_: Binary,
    }
    impl From<Output> for Resource {
        fn from(value: Output) -> Self {
            Resource::Binary(value.return_)
        }
    }
}