1 / 76

eCare Technical Workshop

eCare Technical Workshop. Inverness 23 rd November 2005. Agenda. Introduction Architecture Overview & Technical Context Current Release Features & Demos Next Release Features Hosting Options Partner Perspective Q & A. Agenda. Introduction Architecture Overview & Technical Context

moesha
Télécharger la présentation

eCare Technical Workshop

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. eCare Technical Workshop Inverness 23rd November 2005

  2. Agenda • Introduction • Architecture Overview & Technical Context • Current Release Features & Demos • Next Release Features • Hosting Options • Partner Perspective • Q & A eCare Technical Workshop

  3. Agenda • Introduction • Architecture Overview & Technical Context • Current Release Features & Demos • Next Release Features • Hosting Options • Partner Perspective • Q & A eCare Technical Workshop

  4. Agenda • Introduction • Architecture Overview & Technical Context • Current Release Features & Demos • Next Release Features • Hosting Options • Partner Perspective • Q & A eCare Technical Workshop

  5. Agency Systems are MIS applications within the varying agencies that perform client/patient/person processing functions An Adaptor is a software component that enables communications between agency systems and the eCare Framework […] the Adaptor can be a logical software component built into an agency system or on a separate physical machine eCare Safe Haven or DMZ is a secure perimeter network that connects the Agency networks with the network in which the eCare Framework’s hardware is located. The Messaging Service provides Agency Applications with an interface to the eCare Framework The Multi Agency Store is the repository used to store consented data for the purpose of information being shared between different agencies eCare Technical Workshop

  6. Indexing & Matching • Systems must have a person record prior to sharing or viewing of data in the MAS • Systems must create an index entry in the MAS from a matching solution employing a national process as per the eCare Matching Overview strategy document • eCare maintains a multi-agency index of all connected systems person reference numbers; systems have no access to this index which contains no shared data • Systems must have an index entry to receive MAS notifications • This index permits systems to view data regardless of consent or disclosure authority. The ability to lock a person record in the MAS from viewing is a separate – and currently unrelated – function. eCare Technical Workshop

  7. Consent & Disclosure Authority • Conditions for data sharing are: • Either the Subject (or a proxy for the Subject) has given informed consent to the sharing of data or a competent professional within the disclosing agency has taken a considered decision to override the absence of consent; and • It is necessary and relevant to share the data. eCare Technical Workshop

  8. Consent • Consent is collected once per person in the MAS • A subset of data is stored • A full history of changes is maintained • All systems with an index entry are notified when the status changes • Does not physically enable data sharing eCare Technical Workshop

  9. Systems update their own consent status consent process (cross-partnership) MAS notifies each system with an Index entry that consent has changed MAS maintains a history of all consent eCare Technical Workshop

  10. Disclosure Authority • Authority is stored once per system per person in the MAS • A full history of changes is maintained • All systems with an index entry are notified when the status changes • Physically enables data sharing – no system can send data to the MAS without authority • Does not restrict viewing data from the MAS – all systems with an index entry can retrieve data eCare Technical Workshop

  11. disclosure process MAS notifies system admin thatauthority has changed MAS maintains a history of all authority eCare Technical Workshop

  12. Agenda • Introduction • Architecture Overview & Technical Context • Current Release Features & Demos • Next Release Features • Hosting Options • Partner Perspective • Q & A eCare Technical Workshop

  13. What is the eCare Framework Agency Agency Application NHS Auto Matcher eCare DMZ Adaptor Messaging Services Matching Services Manual Matcher MAS Matching CHI Services eCare Technical Workshop

  14. What are web services • Standards based • Simple Object Access Protocol 1.1 (SOAP) • Web Service Definition Language (WSDL) eCare Technical Workshop

  15. Security • Encryption • SSL Encryption • Authentication • WS-Security (Username Token) • Authorisation • WS-Security / Policy eCare Technical Workshop

  16. WS-Security • Oasis standard • Supported by : • IBM • Microsoft (WSE) • Sun • Oracle • Bea • Message level security • http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf eCare Technical Workshop

  17. Services Documentation Set • Messaging Integration Guide • Messaging Admin Guide • Matching Integration Guide • Matching Admin Guide • Viewer Tool Guide • + Other National Documentation Set…. eCare Technical Workshop

  18. Application Design Decisions • Interoperability • Service Granularity • Authentication and Authorisation • Data Changes • Unique Message Requests • Error Feedback eCare Technical Workshop

  19. Interoperability • Apply best practise • Validate against WS-I Basic Profile WS-I is an open industry organisation chartered to promote Web services interoperability across platforms, operating systems, and programming languages. eCare Technical Workshop

  20. Service Granularity • Document Message Pattern • Coarse grained messages • Simplify message sequencing • Reduce network performance overhead • Simplify transaction management eCare Technical Workshop

  21. Service Granularity… • Standard message formats eCare Technical Workshop

  22. Authentication & Authorisation • Authenticate host application not user • Implemented through WS-Security • Support Role based authorisation (Policy) eCare Technical Workshop

  23. Unique Message Request • All messages must include a unique identifier • Validated on every service request eCare Technical Workshop

  24. Error Feedback • Soap Fault • Client Details – XML formatted error messages & codes • ClientUtilities DLL (for .Net) eCare Technical Workshop

  25. Web Services Supported • Focuses on • Core Demographics • Disclosure Authority • Matching • Processes • Events • Status Episodes eCare Technical Workshop

  26. Agency Boundary 1. New Service User MatchingProcess Host Application 2. Poll for new service users Adaptor 3. New Match Request 8. Match Notification eCare DMZ NHS Boundary Messaging Manual Matcher CHI 4. Store Request Matching MAS 7. Index Created Auto Matcher 6. Search CHI 5. Attempt Match eCare Technical Workshop

  27. Web Services Supported… • Matching Service • NewMatchRequest • Index Service • IsMatched • Not AddIndex etc. eCare Technical Workshop

  28. Matching Process New Match Request MAS Adaptor Match Request Create Index Get Pending Match Request Matching Tool Matching DB Successful Match eCare Technical Workshop

  29. Web Services Supported… • Notifications Service • GetNotifications • AcknowledgeNotifications eCare Technical Workshop

  30. Matching Process Index Created New Match Request MAS Adaptor Get Notifications Acknowledge Notifications eCare Technical Workshop

  31. Matching Demo… • Automatic Matcher • Manual Matcher • CHI Simulator eCare Technical Workshop

  32. Agency Boundary Host Application Adaptor Agency Boundary Data Sharing Host Application 1. Service User Interaction 5. View Shared Data Adaptor Adaptor monitors Changes Viewer 2. Store Disclosure Authorisation 3. Store Service User Data 4. Other Agencies Share Data eCare DMZ Messaging MAS eCare Technical Workshop

  33. Web Services Supported… • Disclosure Service • StoreDisclosureAuthority • StorePartnershipConsent • Person Service (Person, Associate & Professional) • StorePerson • Must be matched first • CurrentData • GetPerson • Current Data Only • GetPersonByMasId • Person Status eCare Technical Workshop

  34. Web Services Supported… • Organisation Service • StoreOrganisation • GetOrganisation • StatusEpisode Service • StoreStatusEpisode • GetStatusEpisodeForSubject • GetStatusEpisode • Process Service • StoreProcess • GetProcessesForSubject • GetProcess • Event Service • StoreEvent • GetEventsForSubject • GetEvent eCare Technical Workshop

  35. Web Services Supported… • Viewer Service • GetPersonView • GetPersonViewXML eCare Technical Workshop

  36. Extensions • Supported by • Processes • Events • Status Episodes • Allows custom data to be stored • E.g. Referral Process: • Reason • Received Date • ConcernFactorCV eCare Technical Workshop

  37. Viewer • What is the Viewer and what can you do? • Access MAS Data • No searching • Embed in web page • .Net User Control (Web Page) • No inherent authentication / authorisation eCare Technical Workshop

  38. Web Service / Embedded Viewer Demo… eCare Technical Workshop

  39. Viewer Usage • ASP.Net page • Parameterised reference data • Access Rights – tab visibility • Configurable Tabs text / CSS eCare Technical Workshop

  40. Version 0.7 Viewer Demo eCare Technical Workshop

  41. eCart Demo eCare Technical Workshop

  42. Agenda • Introduction • Architecture Overview & Technical Context • Current Release Features & Demos • Next Release Features • Hosting Options • Partner Perspective • Q & A eCare Technical Workshop

  43. Forms Web Services • Two Phases • 0.7: Store and Retrieve Completed Form • 0.8(?): Retrieve full Form definition eCare Technical Workshop

  44. Storing a Form • Form Definition must exist in MAS (Excel Tool) • Forms belong to a process • Agencies can collaborate on a single form • Pessimistic locking is implemented • Form ‘updates’ do not overwrite old forms (FormState) eCare Technical Workshop

  45. Storing a Form • New Form • Execute StoreForm web service • Update Form • GetForm (with lock) • StoreForm eCare Technical Workshop

  46. Store Form StoreProcess eCare System A StoreForm (New) Get Form (for edit) Error! Get Form (for edit) Store Form System B eCare Technical Workshop

  47. Webservice Validation • Question mapping – based on Question Code • Definitions validated – e.g. CVs, Validation Types etc. • Mandatory fields not validated – change? • Calculations not validated • Locking validated eCare Technical Workshop

  48. Entities • Form (Form State) • Form Sections (Multiple Occurrences) • Form Question Grouping (Multiple Occurrences) • Responses eCare Technical Workshop

  49. Other Forms Services • GetFormsForProcess • GetForm • UnlockForm • LinkFormToProcess eCare Technical Workshop

  50. 0.7 Enhancements • Logical sorted results (e.g. Processes) • Improved database indexing • Support multiple Person Roles (single operation) • Some new CVs • Various Viewer improvements (cosmetic) • Matching Simulator improvements eCare Technical Workshop

More Related