Name Flags Card. Type Description & Constraints <a href="StructureDefinition-BeModelPopulationScreening-definitions.html#BeModelPopulationScreening" title="Logical model for recurrent population based screening. The model represents one iteration of a screening, called episode. A patient can have multiple episodes for a given screening. A screening of a specific type for a given patient can be repeated after a certain period. Each time the screening is repeated results in a new episode.">BeModelPopulationScreening 0..* Element Logical model for population screening event This logical model cannot be the target of a reference patient 1..1 Reference(Patient) The patient for the screening screeningType 1..1 CodeableConcept The related screening <a href="StructureDefinition-BeModelPopulationScreening-definitions.html#BeModelPopulationScreening.screeningYear" title="The year of the screening process/episode for the given screening. If the patient participated, the participation year is taken. If the patient didn't participate, the calendar year of the invitation is taken. If there is no invitation or participation, there will be no episode. For example, if patient is allowed a population based screening every 2 years for a given screening type and the first screening episode invitation took place in 2022, the next episode will be created for the next invitation in 2024. If the patient has a refusal or exclusion registered and does not have a participation/invitation, so the patient does not have any episodes, the calendar year of the registration of the refusal/exclusion is taken.">screeningYear 1..1 string The calendar year of the screening invitation 0..1 BackboneElement The appointment details of the invitation date 1..1 date The date the patient is invited to participate in the population based screening time 0..1 time The time for the screening if there is a proposed appointment. This is the case for breast cancer screening. locationName 0..1 string Human readable name of the location where the patient is invited to participate. locationAddress 0..1 string Human readable address of the invitation location participation 0..1 BackboneElement The participation details date 1..1 date The date the patient participated in the population based screening locationName 0..1 string Human readable name of the location where the patient participated locationAddress 0..1 string Human readable address of the participation location result 0..1 CodeableConcept The result of participation in the population based screening followup 0..1 BackboneElement Details of proposed actions for the patient after the screening concluded. needed 0..1 boolean Indication if the patient should request or take other examinations/steps based on the outcome of the screening. advice 0..1 string Indication what other examinations/steps the patient should take. request 0..1 string The other examinations that the patient should take. <a href="StructureDefinition-BeModelPopulationScreening-definitions.html#BeModelPopulationScreening.nextInvitation" title="This field gives a short human readable indication for the patient if the patient can expect future invitations for the population based screening and an estimation when the next invitation will be created. If the patient will not receive future invitations for the screening, a short explanation will be given.">nextInvitation 1..1 BackboneElement This field gives a short human readable indication for the patient if the patient can expect future invitations for the population based screening and an estimation when the next invitation will be created. If the patient will not receive future invitations for the screening, a short explanation will be given. type 1..1 CodeableConcept Type of the next invitation or lack of next invitation date 0..1 dateTime (Partial) date of next invitation, if applicable Documentation for this format
Logical model for population screening event
Logical model for recurrent population based screening. The model represents one iteration of a screening, called episode. A patient can have multiple episodes for a given screening. A screening of a specific type for a given patient can be repeated after a certain period. Each time the screening is repeated results in a new episode.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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 manageable, 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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The related screening, for example breast cancer, colon cancer or cervicalcancer.
The year of the screening process/episode for the given screening. If the patient participated, the participation year is taken. If the patient didn't participate, the calendar year of the invitation is taken. If there is no invitation or participation, there will be no episode. For example, if patient is allowed a population based screening every 2 years for a given screening type and the first screening episode invitation took place in 2022, the next episode will be created for the next invitation in 2024. If the patient has a refusal or exclusion registered and does not have a participation/invitation, so the patient does not have any episodes, the calendar year of the registration of the refusal/exclusion is taken.
The appointment details of the invitation
An invitation is not mandatory, in some cases a patient can participate for a screening without an invitation.
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 manageable, 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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The date the patient is invited to participate in the population based screening
The time for the screening if there is a proposed appointment. This is the case for breast cancer screening.
Human readable name of the location where the patient is invited to participate.
For some screenings, but not all, a location is provided for the patient.
Human readable address of the invitation location
A participation is not mandatory. A patient can choose not to participate for a screening.
The date the patient participated in the population based screening
Human readable name of the location where the patient participated
Human readable address of the participation location
The result of participation in the population based screening
Notify the patient if the result was abnormal/positive or normal/negative
Details of proposed actions for the patient after the screening concluded.
This data acts purely as info for the patient to inform the patient of proposed actions and should not be followed up by the screening authority.
Indication if the patient should request or take other examinations/steps based on the outcome of the screening.
Indication what other examinations/steps the patient should take.
The other examinations that the patient should take.
This field gives a short human readable indication for the patient if the patient can expect future invitations for the population based screening and an estimation when the next invitation will be created. If the patient will not receive future invitations for the screening, a short explanation will be given.
Type of the next invitation or lack of next invitation
(Partial) date of next invitation, if applicable