Lomiss Home Care® Physical Therapist provides Physical Therapists in the organization with all relevant information in order to conduct a general visit at a patients house. Among the available information we can find:
Lomiss Home Care® occupational Therapist provides occupational Therapists in the organization with all relevant information in order to conduct a general visit at a patients house. Among the available information we can find:
The Lomiss Studio® is a platform allowing organizations to create the mapping and merging of information from multiple data sources and in multiple technologies, to the Virtual Lomiss database (LDB) this mapping is done via a GUI which means that the person doing the work doesn’t need to have through technical knowledge of the data source technology.
The Studio process is a simplified process helping the organization to plan and build the desired profiles for its distributed workforce.
Project Creation In this phase we will create a new project or select and existing one in order to update
LDB Definition In this phase we will define the properties for the virtual database for the project
Server Connection In this phase we will define the connectivity to the database server which holds multiple databases
Database Selection Once we are connected to the server we will get a list of all available databases on this specific server and will choose the required databases we need for the project
Choose Fields From Tables After selecting the required databases we will get a view into the specific database including all tables and once choosing a table all available fields. Through the GUI we will choose the required fields marking their type (e.g. integer, number etc.), if we move them to the properties buffer or to the calculated buffer (in order to perform further calculation on them) and if this field will be a key in the new virtual DB
Create And Populate LDB Tables After selecting all relevant fields from the source DB and moving them to the buffer we will start building the LDB. We will be able to create new tables, move relevant fields from the buffer to it and define keys for the table
Create Calculated Columns Once we are finished with building the tables and moving the relevant fields from the properties buffer to the LDB we can create calculated columns using fields from the calculated buffer and deploy them with mathematical equations existing in the Studio. This will result in the creation of a new field that doesn’t exist in the source DB
Define Links Between LDB Tables and fields When we finish the definition of the tables we can create links and connections between different fields residing in different tables with in the LDB
Create XML Once the LDB structure is ready we will proceed to create the XML which will contain and define all of the projects characteristics (e.g. data sources, LDB structure etc.)
Create Tables Once the XML is created we can actually create the new LDB database by pressing the “create tables” this process will result in the LDB being created on the target server
Synchronize The last phase of the project is to actually synchronize the LDB with all of the relevant information from the selected data sources this will be done by selecting the Synchronize. On a regular basis during the project the synchronize process will be done automatically as defined in the project design and specification
Profile Definition In this phase we will define the available views that will be available through the web client (e.g. doctor, nurse etc.)
Cellular Definition In this screen we will decide which will be the output devices which will be used. (More devices can be added easily through an XML file)
Views Definition Now we will define the different available views based on profile. We can create a new view (e.g. doctor) and decide from the available fields we defined earlier in the LDB which will be the ones visible to this profile and in which way (e.g. drop down, check box etc.) we will also define the profile ability to view and modify fields
Reports Definition In the same way we have defined views earlier we can now design the different reports which will be available to the users. We will be able to decide which fields will be visible in which report and which profile will have access to which reports.