1 / 27

Pilot for BelRAI integration in care applications

LOGOS (BelRAI). Pilot for BelRAI integration in care applications. 27 April 2011 Bert Paepen & Kris Berckmans - Pyxima bert.paepen@pyxima.com www.pyxima.com. Agenda. 1. Goals of the BelRAI application integration pilot – summary 2. Scenarios - overview 3. Scenarios for this pilot

gino
Download Presentation

Pilot for BelRAI integration in care applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LOGOS(BelRAI) Pilot for BelRAIintegration in care applications • 27 April 2011Bert Paepen & Kris Berckmans- Pyximabert.paepen@pyxima.com • www.pyxima.com

  2. Agenda 1. Goals of the BelRAI application integration pilot – summary 2. Scenarios - overview 3. Scenarios for this pilot 4. Basic services explained 5. Content mapping 6. Security aspects

  3. BelRAI today Web application with BelRAI assessments Medical record, care data,... e-Health

  4. Application integration • Current disadvantages • Double information • Administrative burden • Purpose • Complete BelRAI assessment from existing applications • Maximal integration • BelRAI web application remains • Central data store across settings

  5. Web service architecture ? e-Health

  6. Web service architecture • Data input in care application • Reusing existing data • Only add missing data • BelRAI web service calculates results • Goals • Minimize time for adding BelRAI data • Minimal impact on care applications • Standard: KMEHR

  7. Scenarios • New client enters care institution • Reuse data from other setting: client admin + latest BelRAI outputs • Create new assessment for a client • Reuse existing data from care application to BelRAI • Other data can be filled in • Add data to existing assessment • Data filled in from care application • Data can be filled in also through website (central data store)

  8. Scenarios • Client returns after a short stay in other care institution • View outputs from BelRAI assessments in that setting • Consult outputs of assessments within your own organisation

  9. Scenarios for this pilot • Focus on data input in BelRAI assessments • Reusing existing data from care apps • Faster assessment creation • Faster data input • Easier login and security procedures • Goal: investigate impact on time needed for completing BelRAI assessment • Compared to web application

  10. Schema web service

  11. Web service Methods • In the pilot • CreateAssessment • PutAssessmentData • CloseAssessment • GetHealthOutputs ??? • Future • GetClientInfo • GetListOfAssessments • Other…

  12. CreateAssessment • Create a new assessment for a client in a given setting • Parameters: • Logged in care giver INSZ + role • Care giver(s) list (INSZ and basic admin data) • Client information (INSZ and basic admin data) • Assessment setting (hospital, home care, nursing home) • Flow • Createscaregiver(s) + clientandinformed consent link ifneeded • Createsnew assessment • Returns: ID and URL of the assessment

  13. PutAssessmentData • Addanswer data toanexisting assessment • Parameters: • Assessment ID • INSZ + Role of care giver who has given the answers • Assessment answers (key, value pairs) • Overwrite existing answers or not (boolean) • Flow • Check if caregiver may give answers in the assessment • Add (or overwrite) the answers to the assessment • Returns URL of the assessment

  14. CloseAssessment • Store final outputs + block all future answer dataMake the outputs availableto all allowed care givers • Parameters: • Assessment ID • INSZ + Role of care giver who is closing the assessment • Flow • Check if care giver may close the assessment • Close the assessment and store the outputs • Returns URL of the assessment

  15. GetHealthOutputs • Calculate the current health outputs of an assessment • Parameters : • User (INSZ + Role) that wants to do the calculation • Assessment ID • Outputs that must be calculated • Returns • List of selected outputs of the assessment • URL where the outputs canbeviewed

  16. GetClientInfo (Future) • Retrieve all administrative client information from BelRAI • Parameters: • INSZ of the client • INSZ + role of the requesting care giver • Returns • Selection of administrative client information (key,value) • Based on care giver role

  17. GetListOfAssessments (Future) • Findall assessments that match the given criteria • Criteria: • Care giver (INSZ + Role) • Client • Setting • Period (start + end date) • Returns • List of assessments that match the given criteria

  18. Other… • Search client • Search caregiver • PutClientInfo • PutUserInfo • GetClientInfo • GetUserInfo • …

  19. Web service vs browser • Web service approach • Data input in local app • Additional BelRAI data fields need to be included • Web service call to start assessment, save data and get results • Data and results are displayed within application • Online and offline (+ sync) • Browser approach • Local app makes web service call to start assessment • Data input and result viewing on BelRAI web app • Shortcuts foreseenby web service • Web component within care app • Minimal development by care app • Only online

  20. Web service vs browser

  21. Web service vs browser

  22. Web service vs browser

  23. Content mapping • BelRAI is an instrument validatedbyInterRAI. • Instrument definitionneedstobefollowed • Ensures assessment quality • Standardisationallowscomparison • BelRAI uses i-matrix codes acrossinstruments • iA2b1 > HCA2b LTCFA3c • Web service data exchange  use i-matrix codes

  24. Content mapping • Provide full instrument definition, including i-matrix codes (Pyxima) • Identifycorresponding data fieldsbetweenlocalapplication/BelRAI • Verifyif field valuesand formats match • Map fieldsto BelRAI i-matrix • Use i-matrix codes in webservicecommunication 2 – 5: Localapplication partners + Lucas

  25. Security aspects HTTPS communication with BelRAI web service Request from “trusted party”: certificate • OR: eID with eHealth single sign-on • OR: eHealth certificate • OR: eHealth authentic sources • OR: local app – based on trusted relationship Validated by local app (trusted relationship) Validated by local app (trusted relationship)

  26. Questions/feedback • Security aspects • Login: eID or certificate • Content mapping BelRAI data <> local app • Which data canbemappedto BelRAI data (assessment + administrative information)

  27. Next steps • Provide slides, designs and full instrument definitionsthrough BelRAI wiki (Pyxima) • Bynext workshop • KMEHR definitions (Pyxima) • Start development web service (Pyxima) • Define content mapping (Application partners + Lucas) • Security (Pyxima / Privacy commission)

More Related