Struct ResearchSubjectProgress

pub struct ResearchSubjectProgress {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub type: Option<CodeableConcept>,
    pub type_ext: Option<FieldExtension>,
    pub subject_state: Option<CodeableConcept>,
    pub subject_state_ext: Option<FieldExtension>,
    pub milestone: Option<CodeableConcept>,
    pub milestone_ext: Option<FieldExtension>,
    pub reason: Option<CodeableConcept>,
    pub reason_ext: Option<FieldExtension>,
    pub start_date: Option<DateTime>,
    pub start_date_ext: Option<FieldExtension>,
    pub end_date: Option<DateTime>,
    pub end_date_ext: Option<FieldExtension>,
}

Sub-fields of the progress field in ResearchSubject

Fields

id: Option<String>

Unique id for inter-element referencing

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

extension: Vec<Extension>

Additional content defined by implementations

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

modifier_extension: Vec<Extension>

Extensions that cannot be ignored even if unrecognized

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

type: Option<CodeableConcept>

ResearchSubjectStateType; state | milestone

Identifies the aspect of the subject’s journey that the state refers to.

type_ext: Option<FieldExtension>

Extension field.

subject_state: Option<CodeableConcept>

ResearchSubjectProgresss; candidate | eligible | follow-up | ineligible | not-registered | off-study | on-study | on-study-intervention | on-study-observation | pending-on-study | potential-candidate | screening | withdrawn

The current state of the subject.

subject_state_ext: Option<FieldExtension>

Extension field.

milestone: Option<CodeableConcept>

ResearchSubjectMilestone; SignedUp | Screened | Randomized

The milestones the subject has passed through.

There can be multiple entries but it is also valid to just have the most recent. This should npt be rlied upon as the full path the subject has taken.

milestone_ext: Option<FieldExtension>

Extension field.

reason: Option<CodeableConcept>

StateChangeReason; State change reason

The reason for the state change. If coded it should follow the formal subject state model.

reason_ext: Option<FieldExtension>

Extension field.

start_date: Option<DateTime>

State change date

The date when the new status started.

This is NOT the date the change in state was recorded.

start_date_ext: Option<FieldExtension>

Extension field.

end_date: Option<DateTime>

State change date

The date when the state ended.

end_date_ext: Option<FieldExtension>

Extension field.

Implementations

impl ResearchSubjectProgress

pub fn builder() -> ResearchSubjectProgressBuilder

Start building a new instance

Trait Implementations

impl Clone for ResearchSubjectProgress

fn clone(&self) -> ResearchSubjectProgress

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ResearchSubjectProgress

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ResearchSubjectProgress

fn deserialize<__D>( __deserializer: __D, ) -> Result<ResearchSubjectProgress, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ResearchSubjectProgress

fn eq(&self, other: &ResearchSubjectProgress) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ResearchSubjectProgress

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for ResearchSubjectProgress