1. Code4health – Interoperability Developers
11th March 2016

2. Agenda
1. Welcome & Introduction – Richard Kavanagh 2. Appointments and tasks – Richard Kavanagh 3. Get GP Record Requirements – Ian Townend 4. Introduction to FHIR standards – Richard Kavanagh 5. Timelines for publication – Richard Kavanagh 6. Next steps – Richard Kavanagh

3. Welcome & Introduction
Introductions
Purpose of today’s meeting
High level updates on current projects underway
Roadmaps for developments of the above
Signalling for other Interoperability developments underway (or planned)
How to start a community as opposed to a briefing.

4. GP Connect - Appointments
Requirements to build APIs to support the booking of appointments in Primary Care
Primarily based around
Patient Facing Services
Federated Practices
Decision to use FHIR to create RESTful APIs has been made.

5. Current status Early work in this area published a few months ago.
Next development sprint initiates next week with a “draft” delivery for review early next month.

6. Current Specification
Profiled FHIR resources to meets current use cases
Alignment to other data flows within the NHS estate (eRS, NHS Data Dictionary)
Largely focussed on ‘payload’ rather than the ‘API’ aspects

7. Current DMS - #1

8. Current DMS - #2

9. Next version Improved profiles based on current feedback
Specification of the RESTful components of FHIR
HTTP verbs to be used
HTTP response codes
Search parameters
FHIR Conformance statements
Will be published for a more formal “review”

10. GP Connect - Tasks
Requirements for Tasks currently being finalised by GP Connect business team.
Expectations are that tasks API will be very low complexity largely consisting of a narrative description of the task to be performed.

11. GP Connect – Get Record
Requirements : To be able to request a “Summary” record of a Patient’s care record from a Primary Care system.
Decision to use FHIR to create a RESTful API has been made.
Makes use of FHIR ‘Operations”
The API will evolve over a number of iterations.

12. Phase 1 Phase 2 Phase 3 Get Record – Phasing “HTML” - record
Coded – Medications
Coded – Allergies
Coded – Problems
Coded - Diagnoses
Phase 2
Coded – Key Flags
Coded – Investigations
Coded – Observations
Coded - Immunisations
Phase 3
Coded – Procedures
Coded – Encounters
Coded – End of Life

13. Get Record Schematic
Subject of Care
Composition

14. Get Record Schematic Subject of Care Section Section #1 Code
Title
Section #3
Text
Section #4
HTML
One per section

15. Get Record Schematic Subject of Care Section #1 Entry Section #2

16. Get Record Schematic Subject of Care Section #1 Entry Entry Section #2

17. Current Status
Created in “sprints”, each sprint output published on “NHS Developers Network”
First sprint to be published today
Caters for “HTML View” aspects of the delivery
Coded entries for phase 1 will appear shortly afterwards
Coded entries planned to use SNOMED CT

18. Sprint 1 - Release

19. Current delivery schedule
Current working delivery dates (draft only)
Phase 1 - Medications, Allergies, Problems & Diagnoses
Receive baselined requirements
15 Mar 2016
Agile Release #1 – HTML View
11 Mar 2016
Agile Release #2 – First tranche of coded entries
29 Mar 2016
Draft Release – All coded entries
15 Apr 2016
Phase 2 - Key Flags, Investigations, Observations & Immunisations
Receive baselined requirements
15 Apr 2016
Agile Release #1 – First tranche of coded entries
29 Apr 2016
Draft Release – All coded entries
13 May 2016
Phase 3 - Procedures, Encounters & End of Life
Receive baselined requirements
16 May 2016
Agile Release #1 – First tranche of coded entries
01 Jun 2016
Draft Release – All coded entries
17 Jun 2016
It is anticipated that some of the content will arrive earlier that shown above. We will deliver as soon as we have confirmed requirements.

20. Next Steps for GP Connect APIs
Detailed Technical “Deep Dives” into the specifications are being scheduled.
Requests for “review comments” being organised

21. code4health – Next Steps
How do we best support the community in
Creating APIs
Product versioning
Content & format of products
Creating & sharing information models
Reference data
Value Sets
System Ids (old world OIDs)

22. code4health – Next Steps
How do we fold in the knowledge and input of the wider FHIR community
HL7 UK
Regular meetings & technical discussions
IHE UK
Testing, assurance, FHIR based IHE profiles
HL7 International

23. code4health - AOB
Any other Business?