docs.healthdata.beICT Information Session 2023.08.11
Dernière mise à jour: 2023-09-07 13:29
INVITATION
Dear Sir/Madam,
I’m sending you this mail to remind you that the ICT Info Session takes place tomorrow at 10.30am CET.
We’ll be tackling the Q&A section as usual, including a case study submitted by one of the participating institutions.
The questions and answers, along with the recording, will be posted on the DOCs page in due course.
Below you will find all the necessary connection details.
| Join from the meeting link |
| https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898 |
Don’t hesitate to reach out to us if you have any questions. We look forward to your presence at our meetings.
Kind Regards,
The healthdata.be team
RESOURCES
Recording of the session
Slide deck of the session
Questions and answers to the session
EAM: Entity Access Management; ACC: Online Acceptance Environment; TECH DOC: Technical Documentation; MISC: Miscellaneous
| # | Question | Answer | Topic |
|---|---|---|---|
| Q01 | Could you tell me what happens when a person with an author group in their name leaves a hospital (departure, retirement, etc.)? Who still has access to all the data encoded or in progress in this group? | We deactivate the user but the author group will still exist. Therefore, the registrations will always be visible to the Leads. The Study Lead will be able to submit unfinished registrations and view previously submitted registrations. | EAM |
| Q02 | For coronary angioplasty qermid, on test environment, I receive a clear answer about incorect fields. When all fields are corrected I receive an answer that doesn’t help me : { "responsesDetails": [ "Une erreur s'est produite lors de l'envoi de la demande." ], "timestamp": "2023-08-03T11:48:07" } Where is the problem ? What do I have to do ? | (to be answered next week) | ACC |
| Q03 | What about {TX_BUSINESS_KEY=40.12.28-141.4015/06/2023}? What about {TX_BUSINESS_KEY=44.05.12-095.1914/07/2023}? -> What does that mean and how do I go forward? | (to be answered next week) | HD4DP |
| Q04 | Could it be possible that the number of incidents is decreasing because we are still waiting for solutions to tickets already registered before entering new ones? | To a certain extent, this is correct. A number of you have been patiently waiting for tickets to be resolved, despite other incidents arising. There are a number of incident tickets created which reference previous incidents as a way of attempting to escalate the issues. This, however, doesn't actually work. Therefore, we urge everyone to send an email to the support mailbox for any escalations. This has a dual purpose: keeps the number of incidents to a manageable amount and alerts us to burning issues. | EAM |
This documentation is being updated regularly. We try to provide as correct, complete and clear as possible information on these pages. Nevertheless, if you see anything in the documentation that is not correct, does not match your experience or requires further clarification, please create a support ticket via our portal (https://healthdatabe.atlassian.net/servicedesk/customer/portals) or send us an e-mail via support.healthdata@sciensano.be to report this documentation issue. Please, do not forget to mention the URL or web address of the page with the documentation issue. We will then adjust the documentation as soon as possible. Thank you!