slogan621 / tscharts Goto Github PK

Need an API for getting (get) adding (post) and deleting (delete) medications. Also, need a standalone tool for importing the FDA druglist into the database.

It is being moved to station.

Currently, some forms of the surgery types get requests return just an array of names. The return values should always be JSON objects with both id and name. This is because we want to store IDs, not names, in surgery history objects.

See 133d183 for changes that were made for category API that should be same as needed by surgery types API.

2. Prior surgery(ies) and what they were for and approximately when and where they were performed.
   2a. This should be followed up with, were there any problems with the anesthesia or surgery if the answer is yes to 2.

Dental hygiene is a station like X-ray and needs similar support. It will be added to the routing slip as needed by dentists as final station during visit.

Determine a common clock used by clients and the backend. GMT is probably the right answer. Try to come up with a scheme that ensures that they are also sending gmt, and if they send some me other timezone, concert.

But is that once past gmt midnight, clients can no longer find clinic on that day when searching for a clinic.

See other views e.g., patient for examples.

To support surgery history, an API for getting the various surgery names is needed.

A use case where a dentist can send patient to head of x ray line, then upon xrays being taken, is sent back to head of line for that same dentist needs to be supported in the backend.

Right now, Station objects have these names but Station objects should represent a class, while ClinicStation objects represent instances of that class.

E.g., Station named "Dental" might have instances as ClinicStations named Dental Chair 1, Dental Chair 2, etc..

Monitor app reports unable to find clinic in the following case. A quick check shows one of the REST requests generating a 500 return that needs to be looked at.

Steps to reproduce. Start scheduler.
Then run python mockclinic.py -q -h localhost -p 80 -u -w
Run monitor, observe it reports no clinic for todays date. If you were to wireshark the connection, will see that a 500 error is reported (also can see this by setting breakpoints in Android Studio on returns for RESTful requests).

Medicalhistory GET should return array always when containing search terms. A notFound error should return if search terms (clinic/patient) cannot be found. Empty array should return if no medicalhistory associates with the search terms.

Please upload requirements.txt containing every dependency installed with version numbers. This would help to run the server with much ease.

Please also put down steps to install the project with database configurations.

Thank you!

We are gathering this in the registration app but not yet supported in backend. Need a new API that allows us to create, get, delete, and update a table that records this. Foreign keys are the patient and corresponding registration.

GET API for search should return array always, even when only one item is found. If no item is found for search, return an empty array instead of throwing a NotFound error.

Returntoclinic GET should return an empty array if request contains patientid/clinicid/stationid that exists, but no corresponding resource can be found.

Empty array should be returned if no register associates with the search terms. A notFound error should return if search terms (clinic/patient) cannot be found. A badRequest error should return if the search term 'state' is invalid.

While it may be a numeric value (it is unknown at this point), best to store it as a varchar (128 seems long enough, probably more than enough to hold the required number of letters/digits).

Clinicstation GET should return empty array when request contains search terms and no result is found. A notFound error is raised when clinicid is provided but cannot be found.

GET API for search should return array always. The array returned should be empty if no element is found.

Delete all the files inside the migrations folder except for the init.py.

Patient GET should return an empty array if request contains valid search terms and no corresponding resource can be found.

Default of 0 means unknown?

A default of default 0 for each indicates that data not entered yet (we won't want to ask this data at registration, it is gathered once patient is seeing a practitioner).

The scheduler needs to be modified so that if it detects an empty queue, it scans other queues for patients who have that class of station in their routing slips, pull the patient out of the queue, and insert it into the empty queue. It needs to do this without breaking the scheduling priorities of the queues. For example, if surgery screening is empty and there is a patient in the ENT queue that has surgery screening in the routing slip, the patient can only be moved to surgery screening if ENT is not at a higher priority (or there is not a dependency on surgery screening that ENT be visited first).

Surgeryhistory GET should return array always when containing search terms. Empty array should be returned if no surgeryhistory associates with the search terms. A notFound error should return if search terms (surgery/patient) cannot be found.

Address
Contact Info
Emergency Contact Info
CURP

This is mainly for dental patients, but registration app allows for specifying that the above were not known, and this should be recorded in the patient record.

GetRoutingSlip failed
Traceback (most recent call last):
File "scheduler.py", line 688, in
main()
File "scheduler.py", line 685, in main
x.run()
File "scheduler.py", line 646, in run
ret = y["qent"].update()
File "scheduler.py", line 95, in update
q.save()
File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 708, in save
force_update=force_update, update_fields=update_fields)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 736, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 801, in _save_table
forced_update)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/base.py", line 851, in _do_update
return filtered._update(values) > 0
File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 645, in _update
return query.get_compiler(self.db).execute_sql(CURSOR)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 1149, in execute_sql
cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 837, in execute_sql
sql, params = self.as_sql()
File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 1117, in as_sql
val = field.get_db_prep_save(val, connection=self.connection)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/init.py", line 728, in get_db_prep_save
prepared=False)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/init.py", line 2287, in get_db_prep_value
value = self.get_prep_value(value)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/init.py", line 2282, in get_prep_value
return self.to_python(value)
File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/init.py", line 2269, in to_python
params={'value': value},
django.core.exceptions.ValidationError: [u"'1 day, 1:21:56.787552' value has an invalid format. It must be in HH:MM[:ss[.uuuuuu]] format."]