Fhir canonical data_model_1v0
Download as PPTX, PDF1 like527 views
This document discusses using HL7 FHIR standards to build an interagency portal to integrate health and social care records across multiple organizations. It summarizes: - The team assessed different organizations' systems and found varying support for HL7 standards, with some using bespoke or HL7v2 interfaces. FHIR was seen as a way to standardize integration. - The portal goals were a centralized patient record with consent management and document sharing via web services, preferably using FHIR. - Technical discussions focused on FHIR and RESTful APIs to model data exchange. Resources like DocumentReference, Questionnaires, and CarePlan were identified for sharing specific data types between organizations. - An iterative approach was taken
Fhir canonical data_model_1v0
- 1. HL7 FHIR - IN PRACTICE Kevin Mayfield 19/6/2014
- 2. Background (Referral) • Health and Social Care Bill 2012-2013, The Scottish Government • NHS eHealth strategy - must contribute to care integration and support people with long term conditions • Replace shared assessment system with an Interagency Portal. • Build upon existing clinical portal
- 3. Assessment - Me • 1996-2009 EMIS (GP Systems) – 300 baud drug ordering system – MOD 'GPtoGP' late 90’s – Defence Medical Information Capability Programme (DMICP), live streaming of clinical resources to/from operations in Iraq and Afghanistan • 2010- NHS & Council roles (SQL) – Community, Mental Health and Acute. – 2012 First HL7 interface
- 4. Assessment - NHS Team • Using SCIXML and NHS Scotland Data Standards • Many bespoke interfaces and multiple integration engines. • Minimal exposure to HL7 standards. • Steep learning curve to HL7v3 and CDA. • RESTful? • Community care focused around documents (questionnaires/forms)
- 5. Assessment - Social Services • 4 councils • HL7v2 capable (x1) • NHS (England) ITK and CDA interfaces. Keen to use FHIR (x2) • Bespoke (x1) • Organisation using a Care Plan model (x3) • RESTful
- 6. Building The 'Care' Plan • IHE XDS, BPPC and PIX patterns. • Mostly UML focused (seen as too technical, flow charts preferred.) • Use cases very useful but a tendency to go for solution early. • FHIR and RESTful/CRUD used as model for technical discussions. • IHE and FHIR proved to be resistant to project changes (mostly consent and alerts) and change of supplier.
- 7. Goals • Centralised recording of patients and consent • Document sharing with central index • Portal fed data by a variety of methods, mostly web services (HL7 FHIR preferred).
- 8. Activities/Interventions (NHS) • Document Index using FHIR DocumentReference – Documents returned from many (NHS) sources using FHIR Binary – DocumentReference doubled up as a document notification system. • Questionnaires and other unstructured data using FHIR Questionnaires • Encounters, Care Plan, Orders, Appointments, Alert/Observation and Condition resources (NHS only). • Patient with consent extension and HL7v2 A28/31/40
- 9. Progress Notes • Naturally aligning with IHE profiles • Too many new things – FHIR being a major step towards HL7 CDA and IHE profiles – RESTful interfaces scaled down – Standard coding (SNOMED) premature • FHIR 80/20 rule nearly always correct • Resistance due to DSTU status – ReferralRequest – Consent – Appointments
- 10. Review • Patient identity and consent first – Information Governance • Too much IT focus but the information model FHIR uses, especially the CarePlan resource, showed the way. • DocumentReference/Binary allowed the adoption of an XDS pattern and get the metadata correct – Path to HL7 CDA? • Questionnaires useful but need to used only when other resource not available (tended to capture the 20 in the 80/20) • Only suitable for NHS trusts/social services with EPR systems, PAS systems could stick with HL7v2 • SCRUM worked! FHIR allows sprints
- 11. Questions?
Editor's Notes
- #2: This template can be used as a starter file for presenting training materials in a group setting. Sections Right-click on a slide to add sections. Sections can help to organize your slides or facilitate collaboration between multiple authors. Notes Use the Notes section for delivery notes or to provide additional details for the audience. View these notes in Presentation View during your presentation. Keep in mind the font size (important for accessibility, visibility, videotaping, and online production) Coordinated colors Pay particular attention to the graphs, charts, and text boxes. Consider that attendees will print in black and white or grayscale. Run a test print to make sure your colors work when printed in pure black and white and grayscale. Graphics, tables, and graphs Keep it simple: If possible, use consistent, non-distracting styles and colors. Label all graphs and tables.
- #3: Give a brief overview of the presentation. Describe the major focus of the presentation and why it is important. Introduce each of the major topics. To provide a road map for the audience, you can repeat this Overview slide throughout the presentation, highlighting the particular topic you will discuss next.
- #4: Give a brief overview of the presentation. Describe the major focus of the presentation and why it is important. Introduce each of the major topics. To provide a road map for the audience, you can repeat this Overview slide throughout the presentation, highlighting the particular topic you will discuss next.
- #5: What will the audience be able to do after this training is complete? Briefly describe each objective how the audience will benefit from this presentation.
- #6: If there is relevant video content, such as a case study video, demo of a product, or other training materials, include it in the presentation as well.