1 / 10

GP Connect - Workshop

This workshop provides suppliers with an overview of the recently published FHIR and API guidance and documentation packs, as well as the agile approach to developing these packs. It covers the documentation process, design principles, development approach, and more.

alh
Télécharger la présentation

GP Connect - 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. WIFI – Guest / Smokescreen 25th August 2016 12:30 – 16:00 GP Connect - Workshop

  2. GP Connect -25th August 2016 Purpose of Today • To orientate suppliers with the recently published FHIR and API guidance and documentation packs. • This is to provide suppliers with an overview of the work done to date and the agile approach previously agreed with suppliers to iteratively develop the FHIR and API documentation packs.

  3. GP Connect - Workshop Scope • Agenda • Overview of the documentation process • Overview of documentation pack • Re-stating of the Design Principals • Release candidate development approach • Agile Development • GP Connect Maturity Model • Items Specific to the Spine • Out of Scope for today’s workshop • Detailed review of documentation pack content • Structured Data

  4. GP Connect – What have we been up to? Now that we have a good idea of what will be delivered, other work has included: • Clinical Engagement. • Supplier Community Engagement Initiated (INTEROpengroup members and FoT sites) • Information Governance. • Set up of a supplier integration ‘ecosystem’ to: • Help, support and guidance to build GP Connect consumer applications • Assure and safety-test consumers • Built and Tested the Spine Security Proxy. • Development and roll-out of the GP Connect ‘demonstrator’. • Managing API and FHIR decisions through an internal ‘Decision Log’ published to GitHub as part of the documentation pack. • Development of the supplier CCN.

  5. Documentation Pack Overview of the documentation process Overview of documentation pack

  6. Site map & content Design Principles Design Principles Maturity Model Development Principles Open API Principles Data Model Principles Information Governance Principles Clinical Safety Principles Assurance Principles Non Functional Principles Open API Licence Principles CodeSnippet Systems Clinical Demonstrator Technical Reference Task Management Overview Introduction Clinical Scenarios Design Decisions Wireframes Release Notes Known Issues API Use Cases Send a task Test & Assure Testing Assets Accreditation Assurance System Test Stage 1. Test Window Stage 2. Test Window Stage 3. Test Window Path to Live Help & Support Frequently Asked Questions (FAQ) GP Connect Overview Introduction Getting Started News Capabilities Workshops and Timeline First of Type Glossary Design Approach Design Principles Clinical Terminologies Product Versioning Explore Consumer Demonstrator Reference Implementation Swagger API Documentation Development Guidance Development Assets FHIR API Guidance Open Source Server Guidance Common API Guidance Operation Guidance Resource Guidance Error Handling FHIR Data Models Implement A Capability API Foundations Access Record Task Management Appointment Management Integrate With Spine Cross Org Audit & Provenance Personal Demographic Service Spine Directory Services Spine Security Proxy Introduction Spine Security Proxy Implementation Guide … Access Record Overview Introduction Clinical Scenarios Design Decisions Wireframes Release Notes Known Issues API Use Cases Retrieve a care record section Development HTML Implementation Guide HTML Views Summary Encounters Clinical Items Problems Allergies Medications Referrals Observations Investigations Immunisations Administrative Items Patient Details Structured Data Coming Soon FHIR Data Library Overview FHIR Delta Foundations Patient Practitioner Organization Location Access Record Bundle (Searchset) Composition Device Appointment Management Appointment Schedule Slot Foundations Overview Introduction Design Decisions Release Notes API Use Cases Get the FHIR; conformance profile Find a patient Read a patient Find a practitioner Read a practitioner Find an organisation Read an organisation Find a location Read a location Register a patient Task Management Overview Introduction Clinical Scenarios Design Decisions Wireframes Release Notes Known Issues API Use Cases Send a task Appointment Management Overview Introduction Clinical Scenarios Design Decisions Wireframes Release Notes Known Issues API Use Cases Retrieve a patients appointments Search for free slots Read an appointment Book an appointment Amend an appointment Cancel an appointment FHIR DMS Get Care Record Operation Task Management Appointments

  7. Design Principles Detailed walk through

  8. Development Approach Agile Development Design Principles GP Connect Maturity Model

  9. Items specific to spine Detailed walk through

  10. GP Connect – Wrap up • Next Session – TBC • Has today been useful

More Related