HD ICT Information Sessions

HD ICT Information Sessions johanvanbussel mer 22/02/2023 - 09:27

HD ICT Information Sessions - Overview

HD ICT Information Sessions - Overview Bart.Servaes ven 28/07/2023 - 12:08

ICT Information Session 2023.09.29

INVITATION

Dear colleague,

The healthdata.be team hereby invites you to a new series of open Q & A Sessions. These meetings will address a variety of critical topics that have been brought to our attention, and aim to support you by the implementation of the HD web services and csv upload for the register projects of healthdata.be (Sciensano) .

In our continual efforts to ensure these sessions are as beneficial as possible, we kindly request that you share any specific concerns, outstanding issues, or valuable feedback ahead of the meeting. This will assist us in tailoring our preparations to meet your needs.

At present, we have scheduled these 1 hour online sessions to occur on a weekly basis, each Friday 10h30-11h30. Depending on the volume of feedback and the progression of the sessions, we might adjust the frequency to a bi-weekly occurrence in the foreseeable future. Changes in the schedule will be communicated in advance.

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.09.29:
- Q&A backlog
- HD4DP2 Metrics
- Incidents Report
- Architecture 2.5
- EAM 3.0
- DCD Updates
- Varia

The link to the session of 2023.09.29:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

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

Go to https://docs.healthdata.be/documentation/hd-ict-information-sessions/hd-ict-information-sessions-qa for an overview of all questions raised and answered (Q&A) during our recurring ICT Information Sessions.

Bart.Servaes ven 29/09/2023 - 10:11

ICT Information Session 2023.09.22

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.09.22:
- Q&A backlog
- HD4DP2 Metrics
- Incidents Report
- Issues MyCareNet
- Updates & communications

The link to the session of 2023.09.22:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

HD-ICT_Information_Session_recording_20230922 Download

Slide deck of the session

HD-ICT_Information_Session_slidedeck_20230922 Download

Questions and answers to the session

Bart.Servaes lun 25/09/2023 - 09:27

ICT Information Session 2023.09.15

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.09.15:
- Q&A
- HD4DP2 Metrics
- Incidents Report
- EAM 3.0
- Updates & communications

The link to the session of 2023.09.15:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

HD-ICT_Information_Session_recording_20230915 Download

Slide deck of the session

HD-ICT_Information Session_slidedeck_20230915 Download

Questions and answers to the session

Bart.Servaes ven 15/09/2023 - 13:20

ICT Information Session 2023.09.08

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.09.08:
- Q&A
- HD4DP2 Metrics
- Incidents Report
- EAM 3.0
- Updates & communications

The link to the session of 2023.09.08:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

HD-ICT_Information_Session_recording 20230908 Download

Slide deck of the session

HD-ICT_Information_Session_slidedeck 20230908 Download

Questions and answers to the session

Bart.Servaes mer 13/09/2023 - 16:28

ICT Information Session 2023.09.01

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.09.01:
- Clarification release 2.5
- Q&A
- Incidents Report
- EAM 3.0
- Updates & communications

The link to the session of 2023.09.01:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

HD-ICT_Information_Session_recording_20230901 Download

Slide deck of the session

HD-ICT_Information_Session_slidedeck_20230901 Download

Questions and answers to the session

Bart.Servaes jeu 07/09/2023 - 13:50

ICT Information Session 2023.08.25

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.08.25:
- Q&A of questions received in the onboarding mailbox and unanswered questions during previous ICT information session
- Issue status reports
- updates (Pitter, eam whitelisting, architecture 2 release)

The link to the session of 2023.08.25:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

HD-ICT_Information_Session_recording_20230825 Download

Slide deck of the session

HD-ICT_Information_Session_slidedeck_20230825 Download

Questions and answers to the session

Bart.Servaes jeu 07/09/2023 - 13:51

ICT Information Session 2023.08.11

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

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

Bart.Servaes ven 22/09/2023 - 12:20

ICT Information Session 2023.08.04

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.08.04:
- Q&A of questions received
- Incident and Request metrics
- Varia

The link to the session of 2023.08.04:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

johanvanbussel ven 22/09/2023 - 12:20

ICT Information Session 2023.07.28

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

The agenda for the session of 2023.07.28:
- Q&A of questions received in the onboarding mailbox and unanswered questions during previous ICT information session
- Update of the next steps of the EAM 3.0
- Communication from Riziv/Inami regarding end of transition period

The link to the session of 2023.07.28:
- https://sciensano.webex.com/sciensano/j.php?MTID=ma64d79a5ca26c3a4bf8f62384065f898

The presentations together with questions and answers will be made available on our https://docs.healthdata.be/hd-ict-information-sessions.

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

Bart.Servaes ven 22/09/2023 - 12:20

ICT Information Session 2023.07.21

Dear Partner,

I hereby inform you that there will be no ICT Information Session on Friday 21^st July (public holiday). The healthdata.be team will resume the sessions as normal on Friday July 28^th, where we will be covering the questions scheduled for this week along with any other questions we receive in the meantime.

Furthermore, we will continue to update the FAQ section of the ICT Information sessions on our documentation portal (https://docs.healthdata.be/hd-ict-information-sessions).

The healthdata.be team wishes you satisfying summer holidays.

Most kind Regards,

Sean Deib

Onboarding Functional Lead

Healthdata.be

Tel : +32 2 642 58 17

Webex Teams https://sciensano.webex.com/meet/sean.deib

Rue Juliette Wytsmanstraat 14 • 1050 Brussels

www.sciensano.be

johanvanbussel mar 01/08/2023 - 12:23

ICT Information Session 2023.07.14

Dear Partner,

I hereby inform you that there will be no ICT Information Session on Friday 14^th July. The healthdata.be team will resume the sessions as normal on Friday July 28^th, where we will be covering the questions scheduled for this week along with any other questions we receive in the meantime.

Furthermore, we will continue to update the FAQ section of the ICT Information sessions on our documentation portal (https://docs.healthdata.be/hd-ict-information-sessions).

The healthdata.be team wishes you satisfying summer holidays.

Most kind Regards,

Sean Deib

Onboarding Functional Lead

Healthdata.be

Tel : +32 2 642 58 17

Webex Teams https://sciensano.webex.com/meet/sean.deib

Rue Juliette Wytsmanstraat 14 • 1050 Brussels

www.sciensano.be

Adelaide.DAmore mar 01/08/2023 - 12:24

ICT Information Session 2023.07.07

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

-- Do not delete or change any of the following text. --

When it's time, join your Webex meeting here. Join meeting More ways to join:
Join from the meeting link https://sciensano.webex.com/sciensano/j.php?MTID=ma44a86e2ef029aa9957d7bbc943119ee .
Join by meeting number Meeting number (access code): 2741 935 2969 Meeting password: MwSJi2iBv83 (69754242 from phones and video systems)
Tap to join from a mobile device (attendees only)
+44-20-3478-5289,,27419352969#69754242# United Kingdom Toll
Some mobile devices may ask attendees to enter a numeric password.

Join by phone
+44-20-3478-5289 United Kingdom Toll
Global call-in numbers
Join from a video system or application
Dial 27419352969@sciensano.webex.com
You can also dial 62.109.219.4 and enter your meeting number. If you are a host, click here and login site to view host information.
Need help? Go to https://help.webex.com

The agenda (questions) and the presentations (with answers) will be made available on our https://docs.healthdata.be/hd-ict-information-sessions

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

Adelaide.DAmore ven 22/09/2023 - 12:24

ICT Information Session 2023.06.30

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

-- Do not delete or change any of the following text. --

The agenda (questions) and the presentations (with answers) will be made available on our https://docs.healthdata.be/hd-ict-information-sessions

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

johanvanbussel ven 22/09/2023 - 12:25

ICT Information Session 2023.06.23

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email the onboarding team of healthdata.be.

-- Do not delete or change any of the following text. --

The agenda (questions) and the presentations (with answers) will be made available on our https://docs.healthdata.be/hd-ict-information-sessions

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Questions and answers to the session

johanvanbussel ven 22/09/2023 - 12:25

ICT Information Session 2023.06.16

INVITATION

Dear colleague,

Questions you share before the end of business on the coming Wednesday, will be addressed.

Please feel free to direct any questions or inquiries to email onboarding.

-- Do not delete or change any of the following text. --

The agenda (questions) and the presentations (with answers) will be made available on our https://docs.healthdata.be/hd-ict-information-sessions

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

expiry date 2023.07.24

Slide deck of the session

(available on demand)

Questions and answers to the session

johanvanbussel ven 22/09/2023 - 12:26

ICT Information Session 2023.06.09

INVITATION

Dear colleague,

In the first session, 09/06/2023 at 10h30-11h30, we will start with answering questions received after previous IT information session of 15/05/2023. Questions you share before the end of business on the coming Wednesday, will also be addressed.

Please feel free to direct any questions or inquiries to email onboarding.

-- Do not delete or change any of the following text. --

The agenda (questions) and the presentations (with answers) will be made available on our https://docs.healthdata.be/hd-ict-information-sessions

We look forward to your presence at our meetings.

Kind Regards,

The healthdata.be team

RESOURCES

Recording of the session

(available on demand)

expiry date 2023.07.24

Slide deck of the session

(available on demand)

Questions and answers to the session

johanvanbussel ven 22/09/2023 - 12:26

ICT Information Session 2023.05.15

INVITATION

Dear Sir, Madam,

I hope that this mail finds you doing well.

The reason that I’m reaching out to you is as follows; Healthdata is organizing a general info session for hospital IT staff covering a number of issues which have been flagged (documentation availability, user account issues, MyCareNet situation and the lack of a test environment).

With this in mind, I was hoping you can attend this meeting. (Webex details have been added at the end of the mail)

It will also give you an opportunity to direct any questions that you might have towards us.

The session will be split into the following sections:

Intro – a brief explanation of why this meeting is being organized and the issues which hospitals have flagged
Test Environment – a presentation on our newly-launched test environment which I’m sure you will all find very interesting.
Technical Documentation – presentation covering technical documentation including planned releases of updated documents
Account issues / EAM – presentation on the current state of affairs, our ticket backlog, common issues which have been reported, actions taken to improve the service, the direction the EAM is going in with the aim of improving user experience.
MyCareNet – short update on where we stand with MyCareNet implementation
Q&A

RESOURCES

Recording of the session

(available on demand)

Slide deck of the session

(available on demand)

Bart.Servaes ven 22/09/2023 - 12:28

ICT Information Session 2023.02.17

INVITATION

Dear Madam, Sir,

We are contacting you in the capacity of service provider of a healthcare institution that participates in projects of the National Institute for Health and Disability (NIHDI) and that is part of the Quality Electronic Registration of Medical acts, Implants and Devices (QERMID) program. We would like to invite you, as the technical staff responsible for healthdata.be (HD4DP contact), to an info session on Friday 17th of February 2023 from 10:00 am until 11:30 am to provide further clarification regarding the technical documentation. This info session will cover the following topics:

Clicking on each of the topics above leads you to the respective documentation pages, so you can already consult them. Do not hesitate to send any questions to onboarding.healthdata@sciensano.be (no later than the 10th of February 2023). We will then address them during the session on the 17th of February.

Kind regards,

RESOURCES

(available on demand)

johanvanbussel ven 22/09/2023 - 12:30

HD ICT Information Sessions - Q&A

Welcome to the docs.healthdata.be page on which we have brought together for you to comfortably browse all questions raised and answered (Q&A) during our recurring ICT Information Sessions as from the 15th of May 2023.

EAM: Entity Access Management; ACC: Online Acceptance Environment; TECH DOC: Technical Documentation; MISC: Miscellaneous

#	Question	Answer	Topic	Date
				2023
Q001	Is combined data transfer via API + Form Entry possible?	Yes combined data transfer is possible. Records can be sent via API and also by form entry. However, these forms of data transfer can't be combined on the same record, since the usage of API results in an automatic submit, rendering manual adaptations impossible. When using CSV upload, there is an option to load the data in draft mode which will not automatically submit the record and allow you to modify the record on the web form. CSV, API and form entry are all possible on the online acceptance environment.	CSV API	09.JUN
Q002	This acceptance environment is only for testing purposes?	Yes, the acceptance environment is only for testing. The data is not send to healthdata.be and will be deleted every week.		09 JUN
Q003	Will acceptance environment become available for all hospitals by default ?	Yes, the acceptance environment is available for all hospitals by default. We will proactively create and send out all credentials by June 16th 2023.		09 JUN
Q004	I can't see my institution in the dropdown list.	We will proactively create and send out all credentials by June 16th 2023.		09 JUN
Q005	Is it possible to upload a portion of the data via CSV and complete the rest through the web form?	Yes. If the CSV data is uploaded data in 'draft' mode, yes, you can make modifications in the web UI. To upload in draft mode, add a new column with header 'STATUS' and value 'DRAFT'. Also, see Q001.		09 JUN
Q006	Can we use the same user for the API, is this by Basic Authentication by Postman	Yes, this is basic authentication in Postman. Each organization will receive 3 sets of credentials: for web form, for API transfer and for CSV upload. The usage of the same user is not possible.		09 JUN
Q007	Is it possible after data transfer via API to alter or complete the register via the web UI?	No, this is only possible when loading data via CSV. Please refer to Q001 and Q006 for more details.		09 JUN
Q008	Can Electronic Health Record (EHR) suppliers also gain access to the online acceptance environment, or do they have to work via the hospital acceptance logins?	Yes, Electronic Health Record (EHR) suppliers can also have a separate account giving them access to the online acceptance environment without making use of a hospital's credentials.		09 JUN
Q009	To view the results in the HD4DP2 online acceptance environment, we have to specify test@sciensano.be as an author in CSV or JSON?	Yes, for the online acceptance environment you need to define the test@sciensano.be as Author and Co-Author for the author group Test group.		09 JUN
Q010	So for production we need a user who has access to all the registers to use the API or is there a special admin user ?	On your local installation you have your own specified (technical) user/password to use the API calls for all registers. This user/password has been provided during the installation. If the user/password is not known anymore, it will be provided again by logging a request via Service Desk.		09 JUN
Q011	The service portal says I need a pasword for every register,and ask it by the eam ?	The Entity Access Management (EAM) portal processes user access requests for specific projects (register). For API user/password and SFTP access is not included in the EAM portal. The API/SFTP credentials are valid for all registries the organization is participating in. These credentials are provided to your organization upon installation. If the user/password is not known anymore, it can be provided again by logging a request via Service Desk.		09 JUN
Q012	Is it possible to get correct CSV sample for testing ?	We have updated the example files with full and correct data and we have supplied extra files so all fields are covered in the example files. Please consult our project DOCS pages with information about each project and links to the updated CSV & API sample files on the FAIR portal.		09 JUN
Q013	About the upload of the stable data of the BCFR register with a CSV file, what is to specify as "TX_AUTHOR_GR" : the email of the author group (author) or the name of the author group (To be filled in the format <first_name last_name> of the author, with just 1 space) ?	TX_AUTHOR_GR should be the name of the Author Group. E.g. "TX_AUTHOR_GR": "Tom Mat", "TX_AUTHOR": "tom.mat@example.com", "TX_COAUTHOR": "tom.mat@example.com"		09 JUN
Q014	For a CSV file, can you tell us which column must be added for a draft file submit?	Add a new column with header 'STATUS' and value 'DRAFT'.		09 JUN
Q015	Is it possible to give end users specific authorisation on their sftp folders? Or is it always for authorisation for all the registers?	Access to the sftp folder (and also API) is organization-based authentication and not user-based. API and CSV upload is intended to be managed by the local IT department.		09 JUN
Q016	Should the folders per project also be available per project on our local installation? I now only have /upload/nippin	To see the folders per project, you need to connect to the port 2222, with username starting with organization-<id>. For more information, please consult the relevant DOCS page. The upload NIPPIN folder is accessed using other connection information.		09 JUN
Q017	How can we be invited to these sessions? We have now received the invitation via via. Can we register somewhere?	All hospitals are automatically invited to these regular sessions via the contact persons registered in our systems. Once you receive an invitation, you're welcome to forward it to any colleague who you think would benefit from attending. If you would like to add an email address to the contact list for the IT sessions, please send an email to onboarding.healthdata@sciensano.be.		09 JUN
Q018	Is Mycarenet already working. We don't get any xml in the sftp folder, no reaction from Service Portal on this question (since 2 weeks) ?	At this moment we are in close collaboration with RIZIV and MyCareNet to get the process up and running as soon as possible. Please refer to the relevant DOCS page for a detailed overview on the whole MyCareNet status.		09 JUN
Q019	According to documentation, there should be a table nippin_message in the local DB. But I do not have/see this table?	The nippin_message is not located in the local database but in the nippin database. Please refer to the relevant DOCS page for more information.		09 JUN
Q020	Is it possible to have correct payload for the API testing?	We have updated the example files with full and correct data and supplied extra files so all fields are covered in the example files. Please consult our project DOCS pages with information about each project and links to the updated CSV & API sample files on the FAIR portal.		09 JUN
Q021	How do we get access to the Local DB?	The read-only postgres user/pasword for the local database and nippin database has been provided during installation. If the user/password is unknown, this can be retrieved via the Service Portal.		09 JUN
Q022	For the CSV upload, if I understand correctly, the name of the group (TX_AUTHOR_GR) is the name of the author (example if the author is Tom Mat, the name of the group will be "Tom Mat")?	Yes, that is correct. TX_AUTHOR_GR should be the name of the author group. E.g. "TX_AUTHOR_GR": "Tom Mat", "TX_AUTHOR": "tom.mat@example.com", "TX_COAUTHOR": "tom.mat@example.com"		09 JUN
Q023	Hello, how to get access to acc env?	A request can be made via our Service Portal, but we will proactively create and send out all credentials to the HD4DP SPOC's by June 16th 2023.		09 JUN
Q024	A lot of login and password are pending .... is there delay?	The user access request process consists of several steps (processing the request, approval by SPOC, account creation). Due to the high amount of requests received recently, there is a delay in each of the different steps. We are working hard to reduce the delay.		09 JUN
Q025	What is currently the delay in answers on issue portal concerning access? Over a week?	On average, the current processing time for a ticket is around a week. The user access request process consists of several steps (processing the request, approval by SPOC, account creation). Due to the high amount of requests received recently, there is a delay in each of the different steps. We are working hard to reduce the delay, by expanding our support team.	EAM	16 JUN
Q026	Could you let me know how to grant a user access to all registries without them being a Local Study Lead?	There are only two ways to give a user access to all registrations. Firstly, to make them a study lead. The second option is to give the user the role of Local Study Associate for all author groups that are participating in the projects. It's important to note that the organization is accountable for granting access to a user to see all registrations.	EAM	16 JUN
Q027	What to do with doctors that have multiple accounts, due to the migration of the pacemaker project?	If there are multiple accounts created, a ticket can be logged via the Service Portal to de-duplicate them. In the future, the SPOC will have the ability to deactivate the account. They need to have a single account, which will then be associated with all relevant registries.	EAM	16 JUN
Q028	Why is there no LDAP integration (like we had in HD4DPv1) ?	LDAP integration has been considered but not yet added to the current roadmap of our end-to-end entity access management program.	EAM	16 JUN
Q029	A lot of users require role changes. How do I manage this?	On the EAM roadmap, it is foreseen to provide more user management actions, one of which will be the change of a user's role.	EAM	16 JUN
Q030	As a Responsible Access Entity (RAE) I would like to also have phone contact.	We are reachable by phone, but due to the high workload at the moment we recommend that you create a ticket in Service Desk so that your request can be addressed in due time.	EAM	16 JUN
Q031	Please provide statuses that also allow to support a workflow on the hospital side. Now, for example, after validation you have absolutely no idea whether the request has been completed or not.	On the EAM roadmap, it is foreseen to provide more user management actions, which will also include better feedback towards the SPOC.	EAM	16 JUN
Q032	How can different departments work on a single registration (e.g. secretary, pharmacy and doctors)? In the previous Orthopride application everybody had their task when filling in the registration.	There are two ways to support this process. First, make all users that need to contribute to registration a Study Lead. The second option is to give all contributing users the role of Local Study Associate for all author groups that are participating in the Orthopride project. It's important to note that the organization is accountable for granting access to a user to see all registrations. Please also note that HD4DP2 has been designed to transfer data from within the EHR (Electronic Health Records) directly towards healthdata.be and is not designed to be a secondary EHR.	EAM	16 JUN
Q033	Can a query be made which exports from all registers the registrations that have been submitted so that the pharmacy can inspect what has to be invoiced? Otherwise, all pharmacists need to be a Local Study Lead.	Local IT can provide you with the required information by accessing the local database of HD4DP2. You can find the instructions here.	DOCS	16 JUN
Q034	I would like to go on vacation. The answer that as a spoc you should just use the rules in your email application is absolutely insufficient. It is not only about requests, but also about following up on requests. Delegation must be possible.	It is foreseen in our EAM application that multiple access managers can be determined.	EAM	16 JUN
Q035	When will this new module be online?	End June-early July.	EAM	16 JUN
Q036	Some of our doctors are waiting for weeks and still have not received their password and username, athough they have opened a ticket. Tickets are closed, without answer. Our doctor received a zip file with an installation software instead of his credentials.	This was clearly a misunderstanding as we don't close tickets without a confirmed resolution. If the ticket was indeed closed, please bring this to our attention (along with the ticket number) so that we can address the situation.	EAM	16 JUN
Q037	Is it possible to consult end-users to check the upgrades in a test environment, together with you before you go into production?	With the new Online Acceptance Environment it will be possible for end users to familiarize themselves and already start developing automatic data transfers before a project will be launched in production. The projects will be made available on the Online Acceptance Environment after the User Acceptance Testing has been finalized.	ACC	16 JUN
Q038	How do you determine an Author Group?	When a user is created with the role of Local Study Associate or Local Study Lead an Author Group is created automatically using the first name and last name of the user. A Local Study Support can be added to an existing Author Group. All these actions can be performed via EAM.	EAM	16 JUN
Q039	All members in the same Author Group can work on the same registration" How do you set this up then? How should this be passed on in the application?	The role of Local Study Support can be requested to add a user to a certain author group, and this is done via the EAM portal.	EAM	16 JUN
Q040	As an ICT department, can we see who all has an account? Anyone in the hospital who knows that HD4DP exists can request an account. We have not received a validation step for many users. How do we deal with offboarding?	All users who are classed as Access Managers will have a full overview of all the users' requests in their hospital on their Request Overview tab in EAM, along with the associated roles and the Author Groups to which they are linked. The Access Managers also have the power to approve or reject any requests for access which have been made. There will be a feature added in the future which will allow for the de-activation of user accounts in an upcoming update of EAM. For the validation step, since the last release of EAM (beginning of May 2023), an automatic mail is sent to the SPOC and the request is added to the Requests tab. Before this upgrade all user requests had to be processed by our Service Desk which resulted in a backlog which has been fully processed by mid-June 2023.	EAM	16 JUN
Q041	Some registrations need to be done urgently, otherwise it is too late. And we will miss the deadline to be valid. Will the deadlines for registration be postponed?	Healthdata.be is charged with the task of being a technical facilitator for data transfers. For business-related questions regarding Qermid registries, we kindly direct you to reach out to the Qermid team of RIZIV/INAMI.	MISC	16 JUN
Q042	How can we add an Author Group?	When a user is created with the role of Local Study Associate or Local Study Lead an Author Group is created automatically using the first name and last name of the user. A Local Study Support can be added to an existing Author Group. All these actions can be performed via EAM.	EAM	16 JUN
Q043	We no longer receive XML files for the registers we encode in HD4DP. This is linked to the MyCareNet data flow.	The MyCareNet data flow is currently not yet in production. We are working in close collaboration with MyCareNet and RIZIV/INAMI to activate this flow as soon as possible. The way that files will be made available in the future is changed from one file per registration to one consolidated file per day. This is why the creation of xml files was discontinued back in March.	MY CARE NET	16 JUN
Q044	Where can I find a mapping table for migrating csv files from Architecture 1 to Architecture 2?	There is no need for a mapping table. You can use your Architecture 1 CSV structure to upload in Architecture 2 as we have embedded the mapping internally in HD4DP2. That said, you will need to add three fields that are specific to Architecture 2: TX_AUTHOR_GR, TX_AUTHOR and TX_COAUTHOR. Any DCD changes requested by the researcher when migrating towards Architecture 2 will also need to be added to the Architecture 1 CSV file. Any irrelevant columns in the CSV file won't generate an error message upon upload, they are simply ignored.	TECH DOC	16 JUN
Q045	Error messages received from CSV uploads are unclear. For example " field with id 3375". Could you make them clearer?	We have added this request to our roadmap. In the meantime, making use of the API call that retrieves the complete technical information of a DCD is an alternative method to retrieve more information about a certain field. API call: "GET /api/dcd/payload/definition?dcd-id={dcdId};version={version};language-id={languagerId}" Detailed information can be found on the following DOCS pages.	TECH DOC	16 JUN
Q046	Can you give us, next to the credentials, also the computer number, the ip address and the port number to log in to the Online Acceptance Environment. We cannot find it.	The publically accessible Online Acceptance Environment can be found on https://hd4dp.acceptance.healthdata.be. The SFTP host name is sftp.acceptance.healthdata.be The port number is 2220 The credentials have to be requested through our service portal at https://sciensano.service-now.com/sp.	ACC	16 JUN
Q047	How can the pharmacy see whether a registration has been 'Submitted'? And under what nomenclature was this registration passed on to Healthdata? This is because the hospital (pharmacy and/or billing service) needs this information in order to proceed with correct billing.	Pharmacies are able to see all registrations (and their corresponding status) within their specific Author Group. It is important that they are appropriately linked to all relevant Author Groups to ensure that they have a full overview of the registrations which concern them. Once they have this full overview, the status of each registration will appear under the 'Progress' field. Registrations which have been sent to us will have Progress = Submitted. The registration code is added upon submitting and can be consulted on the registration. In addition, the IT department can extract the full list of registration codes using Query 5 on the DOCS page explaining how to retrieve data from the local database.	EAM	23 JUN
Q048	Which is the real role for the pharmacy?	There are only two ways to give a user access to all registrations. Firstly, to make them a Study Lead. The second option is to give the user the role of Local Study Associate for all Author Groups that are participating in the projects. It is important to note that the organization is accountable for granting access to a user to see all registrations.	EAM	23 JUN
Q049	How can I change the role of someone in my Author Group?	At the moment the only way to do this is to contact our Service Desk via ticket. As of EAM 3.0, the Access Manager will be able to take care of this action.	EAM	23 JUN
Q050	Can assigning a role be done separately for each registration or can it be set across the organization?	Roles (=accounts) are created on a project basis and can't be applicable across the organization. For privacy reasons, hospitals have to ensure that data access is granted on a case by case basis to avoid unwanted access to a patient's data.	EAM	23 JUN
Q051	Can you be local study lead of hip and knee, and then only local study associate for pacemakers? So is it possible to have different roles for different registers? Can you request that by register?	It is indeed possible to have differing roles across different projects. Roles (=accounts) are created on a project basis.	EAM	23 JUN
Q052	Does Local Study Support sees all the data to complete ?	The Local Study Support can see all the registrations that have been created by someone in the same Author Group to which the Local Study Support has been assigned.	EAM	23 JUN
Q053	When will the new EAM application be available?	EAM 3.0 is scheduled to be launched towards the start of July.	EAM	23 JUN
Q054	As a SPOC (Single Point of Contact), I need to edit the accounts of our users, as well as Author Groups and passwords. Will this feature be available in future EAM systems?	All users who are classed as Access Managers will have a full overview of all the users' requests in their hospital on their Request Overview tab in EAM, along with the associated roles and the Author Groups to which they are linked. The Access Managers also have the power to approve or reject any requests for access which have been made. In the future, features will be added which will allow for changing user roles and passwords, or for managing the Author Groups of Local Study Supports.	EAM	23 JUN
Q055	About the empty 'Author Group' problem. Could you explain the workaround to unblock the users?	There is no workaround for this problem. Each user needs to have an Author Group in order to make registrations. If there is an empty Author Group, our technical teams need to investigate this matter and manually add the Author Group. Measures have been put in place in the current version of EAM to avoid this type of problem from occurring in the future.	EAM	23 JUN
Q056	It is possible to make more than 1 person a Local Study Lead, but this doesn't work. Now 1 of us can see everything and the other one nothing.	It is indeed possible to make multiple people a Study Lead where all Study Leads can see all registrations. If this is not the case in your specific situation, then this means that there is a local problem which needs to be investigated by our technical teams.	EAM	23 JUN
Q057	Can we have multiple access managers for the EAM application?	It is foreseen in our EAM application that multiple access managers can be determined.	EAM	23 JUN
Q058	As study support I can no longer change the forwarded files and I am unable to delete them.	If records are already submitted, they cannot be removed. However, corrections can be done by resending the same registration (with the same business key) again with the corrected values which will become the current active registration within our Data Warehouse.	EAM	23 JUN
Q059	Local Study Support users can't see what has been registered or not, by other colleagues, difficult to follow everything.	If someone needs to view registrations made by other colleagues they need to be assigned the role of Local Study Support within their colleague's corresponding Author Group. Doing so will enable them to see the data which has been provided by others within that same Author Group. A Local Study Support can be part of multiple Author Groups.	EAM	23 JUN
Q060	Can pharmacists still be provided with a CSV file (validated files) so that this can be imported into the pharmacy application?	Hospital IT can provide pharmacies with the required information by accessing the local database of HD4DP2.	HD4DP2	23 JUN
Q061	When I delete a registration in HD4DP2 it still appears in the interface, with progress listed as 'Deleted'. How can I remove these?	At the moment the only course of action is to filter these 'deleted' registrations out. It is foreseen in the future to have these records removed from HD4DP2 to allow for a clearer overview. This comes as a result of substantial user feedback.	HD4DP2	23 JUN
Q062	Is it possible to both upload part of the data via CSV and complete the rest in the form?	This is indeed possible and has become commmon practice among many organizations. When uploading the csv an additional field with header 'Status' and value 'Draft' needs to be added. If you do this, then the data contained in the CSV file will be uploaded onto HD4DP2 from where you can make adjustments as required. It is important to note if a draft mode is used the registration needs to then be submitted manually.	HD4DP2	23 JUN
Q063	Can you leave 'incorrect' registrations in HD4DP2	In case an incorrect registration has not been submitted, it can be deleted. If it has been submitted, however, then it will remain in HD4DP2 and the correction can be sent if needed.	HD4DP2	23 JUN
Q064	Can the entered data from version 2.0 be exported to excel or CSV analogous to the option in version 1.0? (CSV download)	There is no export functionality in the tool as such. Hospital IT can provide users with the required information by accessing the local database of HD4DP2)	HD4DP2	23 JUN
Q065	Why can't we just use the old version to put in the data for pacemakers etc…	The move to HD4DP2 comes as a result of the consolidation of all Qermid projects under one organization, the need to streamline automatic data transfer, the requirement to adopt the single data entry principle (e.g. MyCareNet) and the ability to be scalable in the future.	HD4DP2	23 JUN
Q066	Hello. To view the results in the HD4DP2 acceptance web env, we have to specify test@sciensano.be as an author in the CSV or JSON ?	Yes, the author, co-author and author group will always be the test user. Author Group (TX_AUTHOR_GR) with the value "Test group" Author (TX_AUTHOR) with the value "test@sciensano.be" Coauthor (TX_COAUTHOR) with the value "test@sciensano.be	HD4DP2	23 JUN
Q067	Is there an empty template of a CSV available? With a link to the documentation?	These header CSV files (for the projects featured in one of the slides) are already available on DOCS for all the projects which are in production. Next to the header csv we also provide an example csv containing all the headers along with a row with example inputs which can be made use of for uploading purposes.	TECH DOC	23 JUN
Q068	Why did we complicate matters with all these different user roles?	The old approach was not compliant with GDPR regulations and ISC guidelines. There was a clear need to increase the data security levels by implementing these roles within the overall process of data entry.	MISC	23 JUN
Q069	Will this feedback be given to the privacy commission?	The content of and the feedback received during the IT Info Sessions is available to the general public via our DOCS pages.	MISC	23 JUN
Q070	Please also answer about the deadlines of the registrations. We risk losing revenue due to late registrations, but it is impossible to do them.	Healthdata.be is appointed to be the technical facilitator for collecting healthcare data. We unfortunately can't comment or provide an answer relating to deadlines as this is determined by RIZIV/INAMI.	MISC	23 JUN
Q071	Would it be worthwhile for Sciensano to consider visiting a hospital experiencing technical issues to address them on the spot?	If you, as a data provider, are experiencing specific problems we can address them in a direct online session. If the problems still persist after this session, a live meeting can be organized.	MISC	23 JUN
Q072	Please come up with a clear overview of who has to do what and that this can also be communicated in a clear, timely manner, so that we at the pharmacy know what to do.	We are striving to make improvements to our documentation as well as the the timing of our communications. Exceptional circumstances sometimes obligate us to act very quickly which result in a short notice.	MISC	23 JUN
Q073	Who has the right to make corrections for the pacemaker/Angioplasty registers that have already been validated?	Anybody who can make registrations for the project is able to send corrections after the initial data has been submitted and validated. A record sent containing a business key already known at healthdata.be is considered as a correction, because the latest record will always become the new 'active' record.	EAM	30 JUN
Q074	Is it possible to change the author group for a series of already validated registers?	It isn't possible to change some technical fields of which author, co-author and author group are part of.	EAM	30 JUN
Q075	How can I change the user name and keep the same password? For example, if the e-mail address changes	This isn't possible because the email address is directly linked to the user account. Therefore, a new user account needs to be created if there is a change of email address.	EAM	30 JUN
Q076	What can we do if a user enters records under the wrong role ?	The role the user had upon creating a record is not stored in the metadata of the record. Therefore, there is no negative impact on the record itself.	EAM	30 JUN
Q077	Is it possible to create a user profile AND grant access to users in one single operation in EAM using the upload batch request?	Yes, access managers can upload a csv containing user details in order to both create a profile AND grant the appropriate requested accesses in one single action.	EAM	30 JUN
Q078	If you have a csv file with multiple records and there is an error for one record in the csv. Is the entire csv not uploaded or just the record with the error?	It's just the record with the error	EAM	30 JUN
Q079	I have been waiting a long time to receive my online acceptance environment credentials. Can you help me get them?	All access requests have been sent through to all the hospitals a few weeks ago. If this isn't the case for your hospital, then it's possible the credentials were sent to a contact who might perhaps have left the organization. Please create a ticket in our Service Desk to request these same credentials again.	EAM	30 JUN
Q080	Why doesn't the national registry bring back the patient data as in the first version?	Healthdata.be is not anymore allowed to provide this functionality in our applications by eHealth. The policy eHealth applies is that patient information should be available in the EHS (Electronic Health System) and from within the EHS there is a direct link to ConsultRN to retrieve the patient data. This is, one hand, to protect the patient privacy and, on the other hand, to limit the number of requests to ConsultRN.	EAM	30 JUN
Q081	This question relates to Table localdwh.public.local_dwhmessage_key_value. Does the entry TX_BUSINESS_KEY ensure uniqueness across messages from one project only, or can I expect to have a unique business keys across all projects?	The business key is unique to each DCD, not per project, since a project can consist of multiple DCDs	DCD	07 JUL
Q082	What is the difference between columns “previous_registrationcode” and “current_registrationcode” ?	These two columns were foreseen to implement the functionality to regenerate registration codes. However, this is not needed so these have the same value.	NIPPIN	07 JUL
Q083	Column 'Status': “Archived”: only messages whose status was once « Sent » become archived, or do all messages acquire this status after some time, regardless of their original status ? What does the status 'buffered' exactly mean?	The archived status doesn't exist anymore. The MyCareNet flow was not fully developed during the launch of HD4DP2. We are currently testing the final process together with MyCareNet and RIZIV/INAMI. The records in the NIPPIN database will be regenerated when we go live with the new flow.	NIPPIN	07 JUL
Q084	Same question for status 'Invalid'? Can it happen a registration passes the first-line validation (done by Sciensano), and then still gets blocked by a second-line validation (done by Riziv)?	The "invalid" status refers to the fact that the message structure and/or content is not compliant with the expected message structure and/or content (XSD). A message is only validated locally by HD4DP2. All MyCareNet does is confirm when a message is received. There is no second-line validation at MyCareNet.	NIPPIN	07 JUL
Q085	All Orthopride registries have required fields for “Nom du ciment”. It appears there are 2 separate code lists for cements with antibiotics (CEMENT_NAME_81) and cements without antibiotics (CEMENT_NAME_83). Where can we obtain these two code lists?	These two code lists are currently not in the DCD, but will be added shortly.	Code lists	07 JUL
Q086	Can hospitals already make use of the export function in HD4DP2 for Orthopride? Are there any additional settings required for this?	The export functionality is facilitated by querying the local database. The procedure is documented in our DOCS pages (e.g. Query 1 or 2 - https://docs.healthdata.be/documentation/hd4dp-v2-health-data-data-providers/retrieve-data-local-database-hd4dp-v2)	HD4DP2	07 JUL
Q087	Are we obligated to implement all the projects listed on the roadmap presented on 30th June?	As a technical facilitator, it is not healthdata.be's place to expect a hospital to participate in a specific project. Participation can be mandatory or voluntary (where applicable). Participation is project-specific and is determined by the business, which could be either Qermid or a researcher team and hospital management (for voluntary participation).	Roadmap	07 JUL
Q088	Is it possible for you to modify your platform to accept repeatable group data with ‘fixed’ headers if none of the data rows in a file populate all fields?	Yes, we consider this a bug and we will find a solution to rectify the situation	TECH DOC	07 JUL
Q089	Could you tell us when the new EAM portal will be available?	That will be the beginning of September 2023. More details will be given during next topic.	EAM	28 JUL
Q090	Is a Request the perfect reflection of an account? How can I see the actual status of an account, can I trust this "Requests overview" tab (EAM UI) ? In other words, do request and account share the same DataBase table (or a system of perfect replication in real time) ? I mean if I ask for a change based on the "Requests overview" tab (EAM UI), does it have an impact on the associated account ? (RITM0013319)	In current EAM version: Indeed the request registrations are not similar to the account creations. The EAM database is a central database (at HD) that collects all account requests. Based on the requests, the accounts are created locally. Currently the access manager can only see the status of the request (submission) and do not have access to the list of actual created accounts. At HD we collect the local lists of created accounts to support our technical teams to solve incidents. The technical teams within HD have access to another database that contains the actuals list of accounts and access grants. In EAM version 3.0 it is foreseen that the list of actual accounts and grants will be available for the access managers.	EAM	28 JUL
Q091	Regarding the DCD files for Qermid Orthopride registres, would you be able to provide the code lists for CEMENT_NAME_81 and CEMENT_NAME_83? This question was previousy discussed during the meeting of July 7th, 2023. The two fields mentioned were not included in the DCD, but were to be added shortly. What is the current status?	The code lists have been adapted in the respective DCDs on the FAIR portal, and can be reached via the links on the relevant DOCs pages. The DCDs carry the timestamp 20230712	TECH DOC	28 JUL
Q092	We need the data collection names of the Angio and coronary valves, as used in the local database of the HD4DPv2 server. They should be available on the respective DOCS pages, but they are missing. (RITM0013243)	This request was in our back-log and is now assigned to the proper team and planned to be completed during the current sprint.	TECH DOC	28 JUL
Q093	Regarding the MyCareNet messages, is it possible to give us an indication of when these messages will be available. This will allow us to inform our financial department.	We are still in a test phase with MyCareNet and the insurance companies. As soon we have completed the test phase, we will communicate you accordingly. (Latest target date is the beginning of September.)	MY CARE NET	28 JUL
Q094	We are going live with various registers in the coming weeks. We would like to receive an automated email notification whenever there is an error with any of our submissions. Is this something you could arrange? For instance, could you set up a system to send us an email whenever a file is created in the ERROR folder for Spine? The email should be directed to someone at Saint-Luc.	Thank you for this feature request. This is certainly something that we are willing to investigate. Feedback / proposal will be presented in a weekly ICT meeting. If this proposal is acceptable for HCO’s, we can schedule it in our planning.	MISC	04AUG
Q095	How about the Pitter register is it available on acc, asked ServiceDesk but still no response. Pitter goes live 01/09 (with MyCarenet connector). For testing a thougth we had 2 months for testing before production?	A ticket was created to deploy PITTER on the online HD4DP acceptance environment: target date 8/8/2023. The contact points for PITTER registrations will be informed concerning the availability of the Pitter registrations in this acceptance environment.	PITTER	04AUG
Q096	I have been working on the pacemaker / heart valves registers for several months, and we can now generate the necessary csv files for implantation / followups. I have never been able to submit a file with success, there are bugs that I have reported to the team. How can we be sure that it will be possible by the deadline of 31/08/2023?	Open incidents and their statuses: 1/ [Pacemakers - Primo Implantation][Angio : Hospitalisation with PCI][CSV Upload] CSV Upload DRAFT cannot submit in GUI Status: Dev ongoing - ETA 08/08 2/ [TAVI][Surgical] java.lang.RuntimeException: Error while getting MDM code content for field with name: CD_STE_AORTCVL id: 2224, code: 0 Status: Fixed and tested - production rollout 07/08 3/ [TAVI][Surgical] "Significante disfunctie behandelde klep" fields empty after CSV upload Status: Fixed and tested - production rollout 07/08 4/ [Pacemakers][GUI] "stimulatiemodus" fields uploaded through CSV, not showing in GUI Status: Fixed and tested - production rollout 07/08 5/ TAVI][error MDM id 1953 and code 248153007 Status: Analysis ongoing - ETA TBD	CSV API	04AUG
Q097	Have you received successful angio or orthopride submission through API? If yes, could you provide a written document for the procedure please?	Yes, we have received data for Angio ànd Orthopride via API. In next slides we provide an overview of projects for which we received data via CSV Upload or API. The API documentation for each project is available on https://docs.healthdata.be. Select project >> Select "The [[project name]] data collection" >> Select "HD4DP" >> Select "Technical Manual ..." >> Select "HD4DP v2 S2S API" >> Select "S2S API for [[project name/(dcd)]]".	CSV API	04AUG
Q098	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	11AUG
Q101	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	11AUG
Q102	In Spine Registry (HD0240), we haven’t been able to successfully populate the internal patient ID field (numero d’identification interne du patient) field using a .csv file. Can you please confirm the correct header label for this field? The DCD file indicates that the header is TX_IDC_PAT_INT, but in our tests in Acceptance, we receive the message that the header field cannot be found. We reviewed the example files (listed below) but neither of them appear to contain the header/field to load our internal patient id: HD_DCD_submcsv_HDBP0240_Spine_Surgery_01_20230504_HEADERS.csv HD_DCD_submcsv_HDBP0240_Spine_Surgery_01_20230504_Full.csv	Upon investigating this issue, our IT team discovered that the key could not be found in the MDM, so a ticket has been logged with our development team to resolve the issue.	CSV API	25AUG
Q103	For coronary angioplasty qermid, on test environment, I receive clear answer about incorrect 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 ? Or {TX_BUSINESS_KEY=40.12.28-141.4015/06/2023} {TX_BUSINESS_KEY=44.05.12-095.1914/07/2023} What does that mean and how do I go forward ?	For the first part, its a generic error message which usually means that there was an internal error in the middle of the process (database was not available, connection error…). Most of the time these errors are due to temporary events. However, we would need additional details in order to investigate further. The email featuring this question has been forwarded to the appropriate teams in order for them to dig into. The second part is a bit more straightforward. These are business keys that have been provided in the response of the API call, which means the upload was successful.	TECH DOC	25AUG
Q104	Again about CABGs One patient received CABG on 4 segments. It is not infrequent that a patient receives CABG on 4 or even more segments Nevertheless, I received such an error message (see below) Quid ?? { "details": [ { "message": "Het is niet mogelijk om meer dan 3 segmenten aan te vinken." }, { "message": "Het is niet mogelijk om meer dan 3 segmenten aan te vinken." }, { "message": "Het is niet mogelijk om meer dan 3 segmenten aan te vinken." }, { "message": "Het is niet mogelijk om meer dan 3 segmenten aan te vinken." }	This is a question which will require clarification from the Qermid team as this involves details relating to complex clinical situations for which we have no oversight. In addition to this, a ticket will be created. However, the main input will have to come from Qermid on this particular topic.	HD4DP2	25AUG
Q106	What is the difference between approved and approved_rae?	For all intents and purposes, they are the same thing. Approved state dates from when HD manually approved the requests. Approved_rae is currently when an Access Manager approves a request.	EAM	25AUG
Q107	For HD Information session: I managed to get my first Spine registrations sent via REST API, but I now face an expected problem: I cannot retrieve the Qermid registration code, as there are multiple tuples in local_dwhmessage for the same TX_BUSINESS_KEY and the same data-collection-name, and hence, multiple registration codes for the same businessKey. In an earlier session, I was told the combination {business-key,data-collection-name} should be unique, so I filed a bug for this: INC0212162. But perhaps there is another value to take into account?	You are correct in your statement: the combination (business_key,data_collection_name) is unique and therefore also the link with a registration code. The fact you find different registration codes for the same business_key in the local database results from a bug that for each submitted Qermid registration a new registration code was generated, even if the same business_key was used. This bug has been fixed and released on 7/08/2023. The multiple records for the same business_key probably were created before 7/08. If not, we need to investigate this case further. Extra clarification: - If due to this bug multiple registration codes for the same business_key were generated, the last created registration code will be considered to be the correct one. It is the last created registration code that will be send to NIC.	TECH DOC	01SEP
Q108	How will HD know if we are sending a code or an id (e.g. for postcodes, they look the same) ?	There will be 2 different API end point. - The current end point expects MDM IDs, meaning nothing will change for the current API implementations. - A new end point that expects code values		08SEP
Q109	Data collection names are very important, however they are missing in documentation for several projects. Cf. RITM0013243 : already open for two months now	We apologize for the delay in resolving the ticket. The DCD specifications have been published onto DOCs last week on Friday		08SEP
Q110	We will go live with several registries in St Luc couple We are going live with various registers in the coming weeks. We would like to receive an automated email notification whenever there is an error with any of our submissions. Is this something you could arrange? For instance, could you set up a system to send us an email whenever a file is created in the ERROR folder for Spine? The email should be directed to someone at Saint Luc. Thank you	This feature has been placed onto our roadmap from the moment this feature was suggested the first time some time ago. Unfortunately, we haven’t been able to plan the implementation due to other priorities and incidents. In the meantime, if this feature is of high importance to your organization and since there is full access to this folder by the IT department, it might be worth considering writing a local script to monitor the error folder.		08SEP
Q111	Regarding discharge date TX_TTL_DISCH_DATA: I can understand that you need the information if any CABG has been performed during the hospitalisation CD_CABG_EXEC, one response for the hospitalisation Then, repeatable. I can understand, even if that should not be very frequent, several CABG could take place during the hospitalisation DT_EXEC_CABG One date for each CABG during the hospitalisation I hope I’m not mistaken until now. Then, repeatable in repeatable for CD_BYP_RESTE_STENT, yes or no, TPE_CABG_EXEC, multiple values from list segmenten, multiple values from list It is unclear for me. I don’t understand which repeatable (and which multiple value from list) information is needed *Could you describe me such a complex and multiple clinical situation and the JSON translating this situation ?*	This is a rather complex question which has required some investigating. A new JSON file will soon be created to address the second part of your query. As for providing you with a description of the actual clinical situation, it would be advisable to reach out to Qermid for further information.		15SEP
Q112	The account xxx@yyy.be does not allow us to register (via API) anymore since months, although it worked before. We keep getting : TX_AUTHOR_GR must be correctly informed and exists on DB	This error message indicates that the author group for the account is not present in form.io or that the author group is not configured to participate in the DCD for which registrations are made.	CSV API	22SEP

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 request (type : request for information) via our portal (https://sciensano.service-now.com/sp) 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!

Bart.Servaes ven 22/09/2023 - 09:41