-
Notifications
You must be signed in to change notification settings - Fork 2
Generate synthetic ADT messages that correlate with synthetic waveform data #145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
so downstream processes have some location visits to look up against. Not generating ADT HL7 because they can only be processed by the hl7-reader, not waveform-reader, and I don't fancy relying on the fake IDS here.
PR checklistDefault guide for a PR (if multiple PRs for the work, only keep one version of it and link to it on the other PRs)
|
|
So far I'm having trouble running this. Comparing logs between
I think this is because my hl7-reader fails with |
The port seems to be coming through as null. Check that your Unrelated to this, I'm about to push a bug fix for null locations into this branch. |
Seem to have got this working, after adding the rabbitmq port. I also had to add values to the |
|
When I say working, I mean running, but it is throwing lots of errors and doesn't seem to put anything in the queue. Errors:
|
This was fixed very recently. Are you definitely running the latest version? |
Anything you add manually to |
I don't think I was. Now I get;
Still doesn't seem to be anything reaching the rabbitmq queue. |
Absent. |
This is a known usability deficit. You have to manually update your global-configuration.yaml when config variables have been added/removed in |
…rson is ambiguous. Better to keep the data and allow it to be resolved later.
|
This "works" for me now, it was just a question of getting my configuration right. However, I now get multiple matches when querying the fakeuds created, this is a log message from the waveform-controller.
In summary the query is returning 29 possible csn matches for the patient in EDIT: After digging around in my fakeuds, I think this may be due to too many entries in the hospital visit table with NULL discharge_datetimes. For example:
returned 20 rows. If I remove the EDIT: I think this happened because my fakeuds was not emptied from previous runs. Clearing the schemas in the fakeuds has solved the problem. (although I couldn't find an easy way to clear the schemas) |
thompson318
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm now able to run this and it works, enabling better development of the waveform controller. I had problems, firstly with getting the global configuration right, but that is mainly lack of familiarity with how emap setup works.
Second problem was caused by there being old data in the fakeuds schema. I was able to clear this out using an SQL script, but it would be good to document this somewhere, and I'm not sure what the best way to do it is. Alternatively, could we pass an option to clear the fakeuds schema on startup?
To allow for testing outside of the GAE.
Implements #136