{"push_id":1866710172,"size":154,"distinct_size":1,"ref":"refs/heads/master","head":"8553465521933af36380c5bfaea9bdbb0003237c","before":"8670a97640ddcb5eac39101edae2207dd7382738","commits":[{"sha":"ac1f2faf0c20816ec68831b11c155dae1282f237","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Added the volumetric spreadsheet and some supporting words in-line with what was sent to the principal suppliers via email back at the beginning of September 2016 this resolves #39.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/ac1f2faf0c20816ec68831b11c155dae1282f237"},{"sha":"4377d3038e4cc245b849f66e5632b026786764b7","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixed a cut-and-paste error on the two POST operations that create a new FHIR resource. As per the standard FHIR RESTful model and the published common FHIR API guidance page these should both actually be returning a 201 Created (and not 200 OK).","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/4377d3038e4cc245b849f66e5632b026786764b7"},{"sha":"53e2d48cd8e83152afe7fd10908e9ae337f1a07f","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"#97   - fix inconsistency with HTML in tables\n\nChanges to\naccesrecord_view_medications and\naccessrecord_view_problems","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/53e2d48cd8e83152afe7fd10908e9ae337f1a07f"},{"sha":"b4b83d9ded45a9e304d793b6746c96f405bb9e8c","author":{"name":"Adam Lees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Merge pull request #104 from nhsconnect/gh-pages\n\nBringing develop up to date with gh-pages","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/b4b83d9ded45a9e304d793b6746c96f405bb9e8c"},{"sha":"b2b6fe905e7370a2f3e58c94aa48647a55fa1d72","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Uplift access record version number\n\nupdate accessrecord_sidebar.yml","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/b2b6fe905e7370a2f3e58c94aa48647a55fa1d72"},{"sha":"9da7e6b887cca4b549c8f01aa27bbe417db77c03","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"#71 Clarification on JWT reqs for hosted portals\n\nchanges to integration_cross_organisation_audit_and_provenance and\nintegration\\integration_system_topologies","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/9da7e6b887cca4b549c8f01aa27bbe417db77c03"},{"sha":"9ebad0efd21d2bc05e4b764989bde64298badfc7","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"#87 Guidance on platform-specific escape chars\n\nchange to accessrecord_development_html_implementation_guide","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/9ebad0efd21d2bc05e4b764989bde64298badfc7"},{"sha":"ffc3b72e0dd7a8e308bda1d222a81f1327ca4ace","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Merge remote-tracking branch 'origin/gh-pages' into develop","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/ffc3b72e0dd7a8e308bda1d222a81f1327ca4ace"},{"sha":"96d9b588282db884e77c47587c64f0c0df0782c9","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #89 and #86 by adding more guidance for how provider systems should negotiate secure connections, handle client certificates, populate the no-cache response headers and then be tested for the OWASP top 10 web vulnerabilities.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/96d9b588282db884e77c47587c64f0c0df0782c9"},{"sha":"84fc743346c556fa745ca8e7f51bda23e8c6f7c6","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #40 by adding a new section and example to cover the BAD_REQUEST error code when a client request is rejected by the server as it's considered malformed.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/84fc743346c556fa745ca8e7f51bda23e8c6f7c6"},{"sha":"b210af39ba0ebf0ae3812740c62e4061f7837630","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Fixes #60 by specifying cross-check demographic set\n\nChange to accessrecord_development_html_implementation_guide","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/b210af39ba0ebf0ae3812740c62e4061f7837630"},{"sha":"82eb2af0956d3896233c45652e99e8fc9acb25cb","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #53, fixes #57 and fixes #92 by providing more guidance around Content-Type handling, XML and JSON wire format handling, forwards compatibility and the need to support UTF-8 character encoding in-line with the base FHIR DSTU2 standard.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/82eb2af0956d3896233c45652e99e8fc9acb25cb"},{"sha":"f31df13f0533874209c433344931d3774e491d71","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #49 and fixes #95 by adding more guidance around the use of FHIR data types and the various aspects that warrant further consideration when designing a system (i.e. strings are limited to 1MB in size, so could result in truncation of data from a source system if due consideration is not given).","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/f31df13f0533874209c433344931d3774e491d71"},{"sha":"25eb5280b2b1d2d8dc687fa39c43082aaa48c5bb","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #59 by adding guidance for how to handle oAuth Bearer Token errors in-line with RFC 6750 (which is also used by SMART on FHIR).","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/25eb5280b2b1d2d8dc687fa39c43082aaa48c5bb"},{"sha":"4ce811b6a877e539dbe66e09f49833283301b432","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Fixes #78 by uplift to HTML Implementation Guide\n\nChanged ccessrecord_development_html_implementation_guide","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/4ce811b6a877e539dbe66e09f49833283301b432"},{"sha":"c3dcd3674a08cd704db699d00297330da40d39ce","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixed the \"send a task\" example payloads to use the correct value sets as defined in the Task Management DMS also fixed up the date format and requirement to assert what profile(s) the submitted resource is claiming conformance to (as this is needed for API versioning).","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/c3dcd3674a08cd704db699d00297330da40d39ce"},{"sha":"d80913590c538f0fd485218df7c5b3b14f6213df","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Changed the heading to be \"Near Real Time View\" to reflect the important text details and switched to dashes for the unordered list as this is our style elsewhere.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/d80913590c538f0fd485218df7c5b3b14f6213df"},{"sha":"f358d077954a5df71c6802d5dfbb94ece7c3a1e5","author":{"name":"Michael Measures","email":"9d2418dadd971be26606293985ca7c6cc5cd09f9@yahoo.com"},"message":"Fixes #64 by removing the historic known issues which have now been decided upon/addressed.","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/f358d077954a5df71c6802d5dfbb94ece7c3a1e5"},{"sha":"9d373a955db61b95e6ab147898b6f70a7a5e981e","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Fixes #77 by uplifting guidance on record locking\n\nUplift to accessrecord_design,\naccessrecord_development_implementation_guide","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/9d373a955db61b95e6ab147898b6f70a7a5e981e"},{"sha":"76fe5e78528e55c92c66ee226f50d56fae2fcb9a","author":{"name":"adamjlees","email":"1384a7515258a3c502fae7d4de5a811b24ddc687@nhs.net"},"message":"Merge branch 'develop' of https://github.com/nhsconnect/gpconnect into develop","distinct":false,"url":"https://api.github.com/repos/nhsconnect/gpconnect/commits/76fe5e78528e55c92c66ee226f50d56fae2fcb9a"}]}
{"actor":{"display_login":"briandiggle"}}