Requirements Federated Learning and mUlti-party computation Techniques for prostatE cancer
0.1.0 - ci-build
Requirements Federated Learning and mUlti-party computation Techniques for prostatE cancer
0.1.0 - ci-build
Requirements Federated Learning and mUlti-party computation Techniques for prostatE cancer, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/flute-requirements/ and changes regularly. See the Directory of published versions
The different requirements defined in this RTF have been identified through workshops with the different stakeholders of the project, led by HL7 Europe.
Table 11: Standards contribution – functional requirements
| ID | Description | Priority | Category |
|---|---|---|---|
| F-STD-1 | The FLUTE project SHOULD use the HL7 FHIR standard whenever possible. | Medium | Standards usage |
| F-STD-2 | The FLUTE project SHOULD use SNOMED CT, LOINC and UCUM terminologies whenever possible | Medium | Standards usage |
| F-STD-3 | The FLUTE project SHOULD use DICOMweb (DICOM) for imaging evidences | Medium | Standards usage |
| F-STD-4 | A conceptual/logical model of the data that has to be exchanged SHALL be specified | High | Data Model |
| F-STD-5 | Privacy Policies SHOULD be modelled and exchanged using the HL7 FHIR standard | Medium | Privacy Policies |
| F-STD-6 | Permission to access healthcare Data SHOULD be modelled and exchanged using the HL7 FHIR Permission resource | Medium | Privacy Policies |
| F-STD-7 | The prediction of whether a biopsy is need SHOULD be modelled and exchanged using the HL7 FHIR standard | Medium | Prediction Result |
| F-STD-8 | The FHIR exchange capabilities of each system SHALL be modelled and exchanged using the HL7 FHIR CapabilityStatement resource | High | FHIR Architecture |
| F-STD-9 | Each Hospital SHALL expose its non-imaging data using the HL7 FHIR standard | High | FHIR Architecture |
| F-STD-10 | The FLUTE project SHOULD explore the possibility to model AI models using the HL7 standards FHIR and/or CQL | Medium | AI Modeling |
Table 12: Standards contribution – non-functional requirements
| ID | Description | Priority | Category |
|---|---|---|---|
| NF-STD-1 | The definition of the different actors of the platform SHOULD be modelled and exchanged using the HL7 FHIR ActorDefinition resource. | Medium | Testing and Specifications |
| NF-STD-2 | The definition of the different requirements of the platform SHOULD be modelled and exchanged using the HL7 FHIR Requirement resource. | Medium | Testing and Specifications |
| NF-STD-3 | The example scenarios of the platform usage SHOULD be modelled and exchanged using the HL7 FHIR ExampleScenario resource. | Medium | Testing and Specifications |
| NF-STD-4 | The testing of the different requirements of the platform SHOULD be modelled and exchanged using the HL7 FHIR TestScript, TestPlan and TestReport resource. | Medium | Testing and Specifications |