Prompt for the DiagnoseApp

Please create a React-JS application for the DiagnoseModule. The application  has to offer the following views for the user interface: 
    1. DiagnoseView 
    2. KontaktAnfrageView 
    3. PatientDiagnoseView 
    4. PatientDokumentView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The DiagnoseView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Code   type: STRING 
    - name: Name   type: STRING 
An existing Diagnose entity should be loaded from the relative URL: 
    "/DiagnoseService/diagnose/{id}"   (HTTP-GET) 
If a new Diagnose entity has been created, the new entity should be posted to the relative URL: 
    "/DiagnoseService/diagnose"   (HTTP-POST) 
If an existing Diagnose entity has been updated, the modified entity should be sent to the relative URL: 
    "/DiagnoseService/diagnose/{id}"   (HTTP-PUT) 
If an existing Diagnose entity has to be deleted, the following relative URL should be called: 
    "/DiagnoseService/diagnose/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following PatientDiagnose columns: 
    - column: DiagnosedAm 
    - column: Patient 
    - column: Diagnose 
    - column: IstPrimaer 
    - column: Notizen 
The table should have the title "PatientDiagnoses" und the data must be loaded from the server with the following relative URL: 
    "/DiagnoseService/patientdiagnose/diagnose/{id}" 
Add a HTML table to the view with the following PatientDiagnose columns: 
    - column: DiagnosedAm 
    - column: Patient 
    - column: Diagnose 
    - column: IstPrimaer 
    - column: Notizen 
The table should have the title "PatientDiagnoses" und the data must be loaded from the server with the following relative URL: 
    "/DiagnoseService/patientdiagnose/diagnosedam/{id}" 
Add a HTML table to the view with the following BehandlungsSitzungDiagnose columns: 
    - column: Notizen 
    - column: BehandlungsSitzung 
    - column: Diagnose 
The table should have the title "BehandlungsSitzungDiagnoses" und the data must be loaded from the server with the following relative URL: 
    "/LeistungService/behandlungssitzungdiagnose/diagnose/{id}"

2. The KontaktAnfrageView must contain the following fields: 
    - name: Betreff   type: STRING 
    - name: EMail   type: STRING 
    - name: ErstelltAm   type: DATE 
    - name: IpAdresse   type: STRING 
    - name: Nachricht   type: STRING 
    - name: Name   type: STRING 
    - name: Patient   type: Patient 
    - name: SeitenHerkunft   type: STRING 
    - name: Status   type: STRING 
    - name: Telefonnummer   type: STRING 
The data source for the [Patient] select control should be loaded from the relative URL: 
    "/PatientService/patient"   (HTTP-GET) 
An existing KontaktAnfrage entity should be loaded from the relative URL: 
    "/DiagnoseService/kontaktanfrage/{id}"   (HTTP-GET) 
If a new KontaktAnfrage entity has been created, the new entity should be posted to the relative URL: 
    "/DiagnoseService/kontaktanfrage"   (HTTP-POST) 
If an existing KontaktAnfrage entity has been updated, the modified entity should be sent to the relative URL: 
    "/DiagnoseService/kontaktanfrage/{id}"   (HTTP-PUT) 
If an existing KontaktAnfrage entity has to be deleted, the following relative URL should be called: 
    "/DiagnoseService/kontaktanfrage/{id}"   (HTTP-DELETE)

3. The PatientDiagnoseView must contain the following fields: 
    - name: Diagnose   type: Diagnose 
    - name: DiagnosedAm   type: Diagnose 
    - name: IstPrimaer   type: BOOL 
    - name: Notizen   type: STRING 
    - name: Patient   type: Patient 
The data source for the [DiagnosedAm] select control should be loaded from the relative URL: 
    "/DiagnoseService/diagnose"   (HTTP-GET) 
The data source for the [Patient] select control should be loaded from the relative URL: 
    "/PatientService/patient"   (HTTP-GET) 
The data source for the [Diagnose] select control should be loaded from the relative URL: 
    "/DiagnoseService/diagnose"   (HTTP-GET) 
An existing PatientDiagnose entity should be loaded from the relative URL: 
    "/DiagnoseService/patientdiagnose/{id}"   (HTTP-GET) 
If a new PatientDiagnose entity has been created, the new entity should be posted to the relative URL: 
    "/DiagnoseService/patientdiagnose"   (HTTP-POST) 
If an existing PatientDiagnose entity has been updated, the modified entity should be sent to the relative URL: 
    "/DiagnoseService/patientdiagnose/{id}"   (HTTP-PUT) 
If an existing PatientDiagnose entity has to be deleted, the following relative URL should be called: 
    "/DiagnoseService/patientdiagnose/{id}"   (HTTP-DELETE)

4. The PatientDokumentView must contain the following fields: 
    - name: DateiPfad   type: STRING 
    - name: DokumentTyp   type: STRING 
    - name: HochgeladenAm   type: DATE 
    - name: HochgeladenVonMitarbeiter   type: LONG 
    - name: Notizen   type: STRING 
    - name: Patient   type: Patient 
    - name: Titel   type: STRING 
The data source for the [Patient] select control should be loaded from the relative URL: 
    "/PatientService/patient"   (HTTP-GET) 
An existing PatientDokument entity should be loaded from the relative URL: 
    "/DiagnoseService/patientdokument/{id}"   (HTTP-GET) 
If a new PatientDokument entity has been created, the new entity should be posted to the relative URL: 
    "/DiagnoseService/patientdokument"   (HTTP-POST) 
If an existing PatientDokument entity has been updated, the modified entity should be sent to the relative URL: 
    "/DiagnoseService/patientdokument/{id}"   (HTTP-PUT) 
If an existing PatientDokument entity has to be deleted, the following relative URL should be called: 
    "/DiagnoseService/patientdokument/{id}"   (HTTP-DELETE)