Generated Narrative: StructureDefinition Diagnosis Name Flags Card. Type Description & Constraints Diagnosis 0..* Base Diagnosis #xD; identifier 1..* Identifier ID #xD; <a href="StructureDefinition-Diagnosis-definitions.html#Diagnosis.dateOfDiagnosis" title="Official date of diagnosis. Please report the date as documented in the clinical record. Differences across institutions may occur in defining this date (either the date of the final test (laboratory, imaging, surgery or pathology report) based on which therapeutic decision was taken. In other cases the date of the pathology report is used to define the date of diagnosis. The system will send an 'error' message if the date of diagnosis is more recent hat the date of start of treatment. If the date is unkown or partially missed insert the year at the best of your knowledge.">dateOfDiagnosis 0..* BackboneElement Date of diagnosis #xD; centerOfDiagnosis 0..* BackboneElement Center of diagnosis #xD; identifier 0..1 Identifier Center code #xD; name 0..1 string Center name #xD; city 0..1 string Center city #xD; country 1..1 string Center country #xD; primaryTreatmentCenter 0..1 BackboneElement Primary treatment center #xD; name 0..1 string Primary treatment center name #xD; city 0..1 string Primary treatment center city #xD; country 0..1 string Primary treatment center country #xD; dateOfArrivalAtCenter 1..* dateTime Date of arrival to our institution #xD; diagnosticGroup 0..* CodeableConcept Diagnostic Group #xD; <a href="StructureDefinition-Diagnosis-definitions.html#Diagnosis.morphologyCode" title="Report the diagnosis using the ICD-O-3 Morphology coding system (an help tool is built into the system). If also the site of the tumor will be reported (see 'site') using the ICD-O-3 Topography codes, the system will automatically define the tumor according to ICCC-3 classic pediatric classification (see: Cancer category). This field is automatically generated if both ICD-O-3 Morphology and Topography data have been reported">morphologyCode 0..* CodeableConcept Diagnosis #xD; tumorBehaviour 0..* CodeableConcept Tumour behaviour (ICD-O-3 type) #xD; description 0..1 string Diagnosis description #xD; site 0..* BackboneElement Site #xD; code 0..* CodeableConcept Site(ICD-O-3 topography) #xD; description 0..* string Site description #xD; laterality 0..* CodeableConcept Laterality #xD; metastasis 0..* BackboneElement Metastatic #xD; identifier 0..* integer Metastasis id #xD; site 0..* BackboneElement Metastasis site #xD; code 0..* CodeableConcept Metastasis site code #xD; description 0..* string Additional description of sites of metastatis #xD; geneticMarkers 0..1 string Genetic markers(text) #xD; <a href="StructureDefinition-Diagnosis-definitions.html#Diagnosis.stage" title="Stage/Risk. Free trext to specify the stage, if applicable, of the tumor at diagnosis. Staging codes may be different across tumor types and eras of treatment. Please report the one used to define the survivors' tumor at the moment of diagnosis.#xA;In case of leukemia the 'risk' (e.g. high, standard) could be reported. If the stage is unknown, specifie 'NK'">stage 0..1 string Stage/Risk #xD; immunology 0..* CodeableConcept Immunology #xD; <a href="StructureDefinition-Diagnosis-definitions.html#Diagnosis.hereditaryPredisposition" title="Hereditary Cancer Predisposition Syndromeor medical condition cancer associated. Report here if the survivor has some Hereditary Cancer Predisposition Syndrome or a medical conditions, cancer associated. The SurPass system provides a list of the most common Hereditary Cancer Predisposition Syndromes or other medical conditions reported to be cancer associated (an help tool is build into the system: when you start writing the computer proposes the syndromes/conditions with similar spelling). If the syndrome is not listed, please mark other and then 'Specify'">hereditaryPredisposition 0..* CodeableConcept Hereditary Cancer Predisposition #xD; notes 0..* string Notes #xD; Documentation for this format
Diagnosis model to PCSP HL7 FHIR R4 Profiles
Official date of diagnosis. Please report the date as documented in the clinical record. Differences across institutions may occur in defining this date (either the date of the final test (laboratory, imaging, surgery or pathology report) based on which therapeutic decision was taken. In other cases the date of the pathology report is used to define the date of diagnosis. The system will send an 'error' message if the date of diagnosis is more recent hat the date of start of treatment. If the date is unkown or partially missed insert the year at the best of your knowledge.
Institution in which the diagnosis was made.
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")])
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
Code of the institution in which the diagnosis was made. IN AIEOP thus information is retrievable from the Mod.1.01 database
Report here the institution in which most of the treatment was given
Diagnostic Group. ICCC-3 Classification (Main and Extended classification tables)
Report the diagnosis using the ICD-O-3 Morphology coding system (an help tool is built into the system). If also the site of the tumor will be reported (see 'site') using the ICD-O-3 Topography codes, the system will automatically define the tumor according to ICCC-3 classic pediatric classification (see: Cancer category). This field is automatically generated if both ICD-O-3 Morphology and Topography data have been reported
Tumour behaviour. Automatically generated by the system for benign tumors
Site . Report the site of the tumor using the ICD-O-3 Topography (an help tool is built into the system). If also ICD-O-3 Morphology data have been reported, the system will automatically define the tumor also according to ICCC-3 classic pediatric classification (see: Cancer category)
Site description . Free text to report the site of the tumor
Some tumors may be either localized (e.g. stage III neuroblastoma) or metastatic. Please specify.
Please report here the site(s) of metastases detected at diagnosis.
Metastases detected at diagnosis (using ICD-O-3 Topography). If site(s) is unknown, code C80.9
Additional description of sites of metastatis
Please report here any genetic marker: chromosomal alterations (e.g. translocation, deletions, duplications); or other types of genetic alterations (amplification, deletion, mutation)
Condition.evidence.where(code = http://snomed.info/sct#106221001 'Genetic finding')
Stage/Risk. Free trext to specify the stage, if applicable, of the tumor at diagnosis. Staging codes may be different across tumor types and eras of treatment. Please report the one used to define the survivors' tumor at the moment of diagnosis. In case of leukemia the 'risk' (e.g. high, standard) could be reported. If the stage is unknown, specifie 'NK'
Immunology . This is a free text field. Report here, if applicable (e.g. leukemias) the immunophenotype of the disease (sometimes already reported in the ICD-O-3 Morphology coding). If immunology is unknown, specify 'NK'
Condition.evidence.where(code = http://snomed.info/sct#365861007 'Finding of immune status')
Hereditary Cancer Predisposition Syndromeor medical condition cancer associated. Report here if the survivor has some Hereditary Cancer Predisposition Syndrome or a medical conditions, cancer associated. The SurPass system provides a list of the most common Hereditary Cancer Predisposition Syndromes or other medical conditions reported to be cancer associated (an help tool is build into the system: when you start writing the computer proposes the syndromes/conditions with similar spelling). If the syndrome is not listed, please mark other and then 'Specify'
Condition.evidence.where(code = http://snomed.info/sct#32895009 'Hereditary disease')