Introduction
The GP Connect 0.5.1 release is aimed at consumers, and provides more information to better understand the variance in provider systems. Banner messages have been extracted to help consumers better understand the data being returned. Underlying provider system business rules have been highlighted, where known.
The release also contains some general specification uplifts and improvements.
Please see below for further details.
0.5.1 changes
Separate section related guidance from the general guidance in the html implementation guide
Tickets: #535
Affects: Access Record HTML
Description:
- the HTML implementation guidance has a mix of general/technical guidance and guidance relating to the sections. The decision was taken to spilt the content into a Standards page and a Layout page
Pages changed:
- Standards
- page renamed from HTML Implementation Guide to Standards
- all HTML layout items removed
- remaining content reordered to make more sense
- updated following review #541
- Layout
- all HTML layout items now listed on this new page
- content reordered to make more sense
- Provider variance page added in #604
Design Decision page to be reviewed and updated
Tickets: #540
Affects: Access Record HTML
Description:
- following a review the Design Decision page has been uplifted
Pages changed:
- Design decisions
- all decisions have been given a question/or problem statement that explains the need for the given decision.
- no decisions have been changed
- selected and decision labels have been standardised
Align usage of SHALL and MUST
Tickets: #543
Affects: Access Record HTML
Description:
- all references to SHALL have been replaced with MUST
Pages changed:
- Summary
- Encounters
- Clinical items
- Problems and issues
- Allergies and adverse reactions
- Medications
- Referrals
- Observations
- Immunisations
- Administrative items
- Standards
- Layout
- Retrieve a care record section
S-Flag patients to return Patient Not Found in ARHTML
Tickets: #528
Affects: Access Record HTML
Description:
- version 0.5.0 of ARHTML HTML implementation standards states that demographic details are to be redacted for patients which are S-flagged on Spine e.g. ‘May be redacted if patient is flagged on Spine as Sensitive demographics.’ This has been queried and subsequently changed in other capabilities for providers not to return patient records for S-flagged patients but to return a ‘Patient Not Found’ error.
Pages changed:
- Standards
- a preference for a ‘patient not found’ error message to be returned has been added
- all redacted statements have been removed
- statements added for clarity
Default date range if only a start or end date parameter passed in getCareRecord
Tickets: #114
Affects: Access Record HTML
Description:
- the scenario where only a start or an end date need to be considered and the GP Connect program needs to update the specification to cater for the possibility of someone only sending a start date or an end date
Pages changed:
- Layout
- date banner section uplifted to add more clarity on expected date range behaviours
Default Date Range Banner Message Wording
Tickets: #162
Affects: Access Record HTML
Description:
- change default date range range banner message wording.
Pages changed:
- Layout
- default listed as ‘All relevant items’
Access Record HTML format
Tickets: #214
Affects: Access Record HTML
Description:
-
in the ‘HTML Views’ pages there are ‘HTML View’ sections which show how the HTML should be formatted for all the sections.
these have always been treated as part of the spec, indicating the proposed tag format and structure for the HTML. It was raised that this is not clear and should be updated to specifically say that the format and tags should be followed for the HTML structure.
Pages changed:
- Encounters
- Clinical items
- Problems and issues
- Allergies and adverse reactions
- Medications
- Referrals
- Observations
- Immunisations
- Administrative items
Each of these pages have been uplifted to make the HTML View more clear.
Align 0.5.1 core spec with 1.2.2
Tickets: #603
Affects: Core
Description:
- the 0.5.0 specification is currently out of alignment with the 1.2.2
Pages changed:
Core pages have been uplifted to align with 1.2.2 where it does not change the requirements.
Add Provider Variance page
Tickets: #604
Affects: Access Record HTML
Description:
- add a Provider Variance page to help consumers better understand what is being returned in Access Record HTML
Pages changed:
- Provider variance page added
- this page identifies known variances across banner messages and business rules
ARHTML - IG Reqs Uplift
Tickets: #399
Affects: Access Record HTML
Description:
- stronger wording required to ensure that Access Record HTML is used in real time (meaning, should not be stored)
Pages changed:
- Introduction
- “Access Record HTML is delivering the capability to view a patient record and MUST be used in real time.” wording added
