Generated Narrative: StructureDefinition be-model-eagreement Name Flags Card. Type Description & Constraints be-model-eagreement 0..* Element BeModelEAgreement Elements defined in Ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension #xD; serviceProvider 0..1 Identifier NIHDI number of the service provider making the request #xD; patient 1..1 Identifier Patient identification #xD; eAgreementType 1..1 CodeableConcept Identification of the type of agreement (ex: Fb). A general type "physiotherapist" is applicable for the consultation #xD; decisionId 0..1 Identifier Identifier of the decision communicated by the insurer organization (included in the consultation flow) #xD; desiredStartDate 0..1 dateTime Desired agreement start date, corresponding to the processing start date (dd/mm/yyyy) #xD; pathologyOnsetDate 0..1 dateTime Estimated date of onset of pathology (dd/mm/yyyy) #xD; assessmentCompletionDates 0..5 dateTime Date(s) of completion of the assessment (1 to 5 for an ask and 1 for an extend) to be communicated in case of a treatment request #xD; pathologicalSituation 0..1 CodeableConcept Coding of the pathological situation referring to existing notification/request forms (e.g.: Fb-51) #xD; notes 0..1 Annotation Free text for any additional information #xD; prescription 0..1 BackboneElement Data of the prescription concerned by the request #xD; identification 0..1 Identifier UHMEP identifier of the referral prescription #xD; prescriber 1..1 Identifier NIHDI number of the prescriber #xD; authoredOn 1..1 dateTime Prescription date #xD; quantity 1..1 positiveInt Number of sessions prescribed #xD; scan 0..1 Binary Electronic copy of the prescription #xD; related 0..1 BackboneElement Prescription of a previous pathology #xD; identification 0..1 Identifier UHMEP identifier of the referral prescription #xD; prescriber 1..1 Identifier NIHDI number of the prescriber #xD; authoredOn 1..1 dateTime Prescription date #xD; quantity 1..1 positiveInt Number of sessions prescribed #xD; scan 0..1 Binary Electronic copy of the prescription #xD; attachment 0..* BackboneElement Other possible appendix #xD; kind 1..1 CodeableConcept Type of content (medical report, …) #xD; title 0..1 string Free text allowing a more precise description of the subject of the appendix (recommended) #xD; scan 1..1 Binary Electronic copy #xD; Documentation for this format
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")])
NIHDI number of the service provider making the request
Identification of the type of agreement (ex: Fb). A general type "physiotherapist" is applicable for the consultation
Identifier of the decision communicated by the insurer organization (included in the consultation flow)
Desired agreement start date, corresponding to the processing start date (dd/mm/yyyy)
Estimated date of onset of pathology (dd/mm/yyyy)
Date(s) of completion of the assessment (1 to 5 for an ask and 1 for an extend) to be communicated in case of a treatment request
Coding of the pathological situation referring to existing notification/request forms (e.g.: Fb-51)
Free text for any additional information
Data of the prescription concerned by the request
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
UHMEP identifier of the referral prescription
Free text allowing a more precise description of the subject of the appendix (recommended)