[EXT-7] New Extension: Canvas Medical about awell-extensions HOT 15 CLOSED

@radoslawstepinski please document progress here on a daily basis. gracias!

from awell-extensions.

Currently working on implementing actions and transforming data into multi-level structures accepted by Canvas

from awell-extensions.

Actions

• decide on whether to finish getters that have already been written (getPatient, getTask, getAppointment) — do we put them in a separate MR for now, or do we finish them with granular data points (which data points for each getter to be discussed as well)
• work on the create questionnaire responses action using the json body input
• do not work on the read questionnaire responses action yet until @rahulkeerthi confirms approach
• do not work on the notification protocols yet
• @rahulkeerthi to set up access to awell-next for @michal.grzelak and @mateusz.kubiak + ensure extensions can be run/tested locally (with @danijel help) by Tuesday latest
• ensure that all existing create/update actions use a json body input for the 'body' of the update/creation
• feel free to include the 'task update' action since it is already done

from awell-extensions.

@michal.grzelak @mateusz.kubiak I spoke to danijel and I think I know what needs to be done to get the extensions running locally. I will work with you both on Tuesday to get awell-next up and running + running the extensions server with local extensions code so you can test your extensions work locally.

from awell-extensions.

We've decided on a different approach that means you don't need to run awell-next locally next week (yet! that will come soon!)

You can merge minor version of extensions code and this will deploy to our staging environment automatically. I will give you access to staging and show you how it works on Monday.

from awell-extensions.

Instructions are in the README: https://github.com/awell-health/awell-extension-server#readme

from awell-extensions.

Because they require merging support for JSON data type work that we aren’t 100% happy with

from awell-extensions.

Yes, of course! @mateusz.kubiak can you ensure you cherry pick that excess code into another branch so we don’t lose it?

from awell-extensions.

@mateusz.kubiak for now we shouldn't have any actions that use FieldType.JSON — these should not be exported from the index of the extension. Happy to chat about this for a bit if you need more clarity

from awell-extensions.

Yes, sorry you are right — JSON as input field type is 👍, JSON data points as input + outputs is 🚫

from awell-extensions.

@michal.grzelak are you able to do a first review now? I’ll review this after lunchtime anyway

from awell-extensions.

@mateusz.kubiak I've provided a review, as has @michal.grzelak

Let me know any questions you have and once you have made changes, we can always get on a short call to discuss specific questions remaining instead of doing another async review

from awell-extensions.

Demo to be created on Monday by @mateusz.kubiak

from awell-extensions.

The following actions have been released

Demos:

https://htdhealth.slack.com/files/U016FKYJ6AH/F05QX5GDX1A/create-questionnaire-response.mov

https://htdhealth.slack.com/files/U016FKYJ6AH/F05QX5HDFLL/create-update-appointment.mov

https://htdhealth.slack.com/files/U016FKYJ6AH/F05R7B407NV/create-update-patient.mov

https://htdhealth.slack.com/files/U016FKYJ6AH/F05QNMHLT7G/creating-updating-tasks.mov

from awell-extensions.

@Sanne 👆

from awell-extensions.