docs.healthdata.beICT Information Session 2023.07.07
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.
| -- 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
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 | 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 |
| Q02 | 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 |
| Q03 | 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 |
| Q04 | 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 |
| Q05 | 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 |
| Q06 | 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 |
| Q07 | 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 |
| Q08 | 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 | Repeatable Blocks |
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!