1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
//! GuidanceResponse
//!
//! URL: http://hl7.org/fhir/StructureDefinition/GuidanceResponse
//!
//! Version: 5.0.0
//!
//! GuidanceResponse Resource: A guidance response is the formal response to a guidance request, including any output parameters returned by the evaluation, as well as the description of any proposed actions to be taken.
//!
//! FHIR: <https://build.fhir.org/>
//!
//! UML: <https://build.fhir.org/uml.html>
// Allow unused crate::r5::types as types;
#![allow(unused_imports)]
use crate::r5::types;
use ::serde::{Deserialize, Serialize};
use fhir_derive_macros::Validate;
/// A guidance response is the formal response to a guidance request,
/// including any output parameters returned by the evaluation, as well as
/// the description of any proposed actions to be taken. It is typically
/// produced by a clinical decision support service after evaluating a
/// knowledge module (such as a rule, ECA rule, or order set) against a
/// patient's data, and may carry proposed actions, data requirements, or
/// evaluation messages.
///
/// Within the FHIR R5 clinical decision support workflow, a
/// `GuidanceResponse` is generated as the result of invoking a CDS Hooks
/// service, a `$evaluate` operation on a `PlanDefinition`, or an equivalent
/// knowledge artifact. It correlates back to the originating request via
/// `request_identifier`, references the subject and encounter the guidance
/// applies to, and reports its processing outcome through `status`
/// (for example `success`, `data-required`, or `failure`). The response may
/// bundle structured output parameters, proposed follow-up actions as
/// `result` references, evaluation `note`s, and any `data_requirement`s the
/// evaluating module still needs in order to complete its assessment.
///
/// # Related resources
///
/// - The `subject` is typically a [`Patient`](crate::r5::resources::patient::Patient).
/// - The guidance module itself may be identified via `module_codeable_concept`
/// using a [`CodeableConcept`](crate::r5::types::CodeableConcept), or by
/// canonical/absolute URI referencing a `PlanDefinition` or `ActivityDefinition`.
/// - `evaluation_message` and `output_parameters` typically reference an
/// `OperationOutcome` and a `Parameters` resource, respectively.
///
/// # Examples
///
/// ```
/// use fhir::r5::resources::guidance_response::GuidanceResponse;
///
/// let value = GuidanceResponse::default();
/// let json = ::serde_json::to_value(&value).unwrap();
/// let back: GuidanceResponse = ::serde_json::from_value(json).unwrap();
/// assert_eq!(value, back);
/// ```
#[serde_with::skip_serializing_none]
#[derive(Debug, Default, Clone, Serialize, Deserialize, PartialEq, Eq, Validate)]
#[serde(rename_all = "camelCase")]
pub struct GuidanceResponse {
/// Logical id of this artifact
pub id: Option<types::String>,
/// Metadata about the resource
pub meta: Option<types::Meta>,
/// A set of rules under which this content was created
pub implicit_rules: Option<types::Uri>,
/// Language of the resource content
pub language: Option<types::Code>,
/// Text summary of the resource, for human interpretation
pub text: Option<types::Narrative>,
/// Contained, inline Resources
pub contained: Option<Vec<::serde_json::Value>>,
/// Additional content defined by implementations
pub extension: Option<Vec<types::Extension>>,
/// Extensions that cannot be ignored
pub modifier_extension: Option<Vec<types::Extension>>,
/// The identifier of the original guidance request that this response correlates to, if any
pub request_identifier: Option<types::Identifier>,
/// Business identifier
pub identifier: Option<Vec<types::Identifier>>,
/// What guidance was requested
pub module_uri: Option<types::Uri>,
/// What guidance was requested
pub module_canonical: Option<types::Canonical>,
/// What guidance was requested
pub module_codeable_concept: Option<types::CodeableConcept>,
/// The processing status of the guidance response: success | data-requested | data-required | in-progress | failure | entered-in-error
pub status: types::Code,
/// The patient (or other subject) the guidance was requested and evaluated for
pub subject: Option<types::Reference>,
/// Encounter during which the response was returned
pub encounter: Option<types::Reference>,
/// When the guidance response was processed
pub occurrence_date_time: Option<types::DateTime>,
/// Device returning the guidance
pub performer: Option<types::Reference>,
/// Why guidance is needed
pub reason: Option<Vec<types::CodeableReference>>,
/// Additional notes about the response
pub note: Option<Vec<types::Annotation>>,
/// Reference to an OperationOutcome containing messages resulting from the evaluation of the artifact or artifacts
pub evaluation_message: Option<types::Reference>,
/// Reference to a Parameters resource containing the output parameters of the evaluation, if any
pub output_parameters: Option<types::Reference>,
/// Proposed actions resulting from the evaluation, such as RequestGroup resources, if any
pub result: Option<Vec<types::Reference>>,
/// Additional data that was requested by the evaluating module but was not supplied with the original request
pub data_requirement: Option<Vec<types::DataRequirement>>,
}
#[cfg(test)]
mod tests {
use super::*;
type T = GuidanceResponse;
#[test]
fn test_default() {
let _ = T::default();
}
#[test]
fn test_serde_round_trip() {
let value = T::default();
let json = ::serde_json::to_value(&value).expect("to_value");
let back: T = ::serde_json::from_value(json).expect("from_value");
assert_eq!(value, back);
}
}