docs.healthdata.beICT Information Session 2023.08.25
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.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:
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
EAM: Entity Access Management; ACC: Online Acceptance Environment; TECH DOC: Technical Documentation; MISC: Miscellaneous.
| # | Question | Answer | Topic |
|---|---|---|---|
| Q01 | 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. | |
| Q02 | 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. | |
| Q03 | 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. | |
| Q04 | 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. |