Our workshop / lab is on the calendar for Friday 1/5. Your assignment is to (re) create one of the Tricefy 3.5 reports (there are links to them in this page). You will need to use most of the Reporting template widgets, namely:
Snippets (snips) with smart text
The structure of the workshop / lab will be similar to last time: you will show your report template and provide feedback. With lots of lively discussion.
So get to work ... and have fun. We really appreciate everyone's time invested in these assignments. It's really so helpful for the team.
The diagram on the left shows how links to images/videos/reports get inserted into an EMR application via HL7 interfaces. Once Tricefy is configured for a specific EMR integration, patient identifying and encounter information along with permanent (non-expiring) links are accumulated by the associated Tricefy HL7 Interface module for the clinic in question. Patient identifying information for a clinic could be a patient identifier or a combination of demographic information (e.g., patient name and patient dob).
The HL7 Interface module builds the HL7 message that contains this information, often including ORC, OBX, PV1, OBR, PID and PV1 HL7 segments. These HL7 messages are then persisted to a secure location where the EMR software can read and process them to be included in the patient's Electronic Medical Record.
The HL7 Interface module can run in the cloud or in the customer's local network.
IAM (Identity and Access Management) controls user and program access to AWS services and resources. This enables Tricefy to support a role and permission structure that limits all access to resources and data.
Virtual Private Cloud (VPC) allows Tricefy to set up a logically isolated network where all the resources are private and not accessible to the internet or other services outside of the Tricefy virtual private network
RDS (cloud Relational Database Service) provides resizable capacity while automating adminstration tasks such as provisioning, setup, patching and backup. Trice uses PostgreSQL database with a fully encrypted disk. All backups are encrypted as well.