-
Notifications
You must be signed in to change notification settings - Fork 12
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
Import URL from Documents to Problems/Diagnoses #114
Comments
@tony-shannon |
Sorry, I don't understand the issue sufficiently. What API / URL are we talking about? eg is it POST /api/documents/patient/:patientId/:host ? or are you referring to a different API? |
@robtweed Documents Allergies Medications We need these fields to be added: These three fields should be saved on the server with POST and PUT и be returned with GET |
I don't remember enough about how Documents are supposed to work and the mechanics that are supposed to take place. It would be useful to have a short screen cast showing the steps typically involved in importing documents, or a document that steps me through what you do so that I can reproduce the issue and trace through the middle tier code. |
One thing I don't understand is: where do the Discharge Summary records for 9999999000 and 9999999068 come from? I don't see a Create or Add button anywhere that allows one to be added via PulseTile. I'm sure I once knew about this, but I really can't remember how these Documents are supposed to work |
@robtweed |
In current Angular and React versions I don't see URLs, so could we consider this task Done: |
When we import Data using Documents heading (Diagnosis List) for example:
http://prntscr.com/i86vlq
http://prntscr.com/i87oci
When we send POST to create Diagnoses we send these fields to mark these heading that they were created from Documents and have this imported URL :
http://joxi.net/nAyLDXLfYzeoz2
But we get them empty in response:
http://joxi.net/Drl7DO7svgjL3A
Could you check it please?
Related issue: QEWD-Courier/Ripple-Qewd#79
The text was updated successfully, but these errors were encountered: