Working on #36, adding documentation as we explore the tutorial slide…

…shows

docs/_source/notes.md

@@ -33,10 +33,10 @@ There are many :-/
 * https://code4health.org -- An incubator group from NHS England
 * There are many references to strategy and ongoing work via the NHS Digital Technology pages - https://www.england.nhs.uk/digitaltechnology/
 * Various data resources can be found on the TRUD (the Technology Reference data Update Distribution site) - https://isd.hscic.gov.uk/trud3/user/guest/group/0/home
- * Look for the UK SNOMED CT! - https://isd.hscic.gov.uk/trud3/user/guest/group/0/pack/26
  * The Interoperability Toolkit - https://isd.hscic.gov.uk/trud3/user/guest/group/41/pack/30
+* http://data.developer.nhs.uk/fhir/eRS/Chapter.1.About/index.html -- FHIR Implementation Guide for the NHS e-Referral Service
 
-### Fhir(base)
+### FHIR(base)
 
 A likely favourite as their data model seems more flexible and saner (see person -> names as an example compared to NHS)
 
@@ -52,24 +52,53 @@ A likely favourite as their data model seems more flexible and saner (see person
 * http://hl7.org/implement/standards/fhir/resourceguide.html -- HL7 standards
 * http://hl7.org/implement/standards/fhir/implementation.html -- Fhir implementation checklist
 
+* Slideshows:
+ * http://www.slideshare.net/ewoutkramer/fhir-tutorial-morning
+ * http://www.slideshare.net/GrahameGrieve/introduction-to-fhir
+
+* Extensions are a key concept to understand, and some work will likely be needed to be done to create relevant ones for Transplantation
+ * https://fhirblog.com/2014/03/06/extensions-are-not-second-class-fhir-citizens/
+ * See also the link to the NHS eRS which uses extensions 
+
 * http://www.hl7.org.uk/doc_store/NHS/HL7%20Integration%20Options%20for%20Trusts.pdf -- HL7 talks about integration strategies, including the need for roadmaps (and steps to create)
 
 * http://www.ehealthnews.eu/emis/4679-emis-health-implements-open-standards-for-interoperability -- EMIS are using Fhirbase with Snomed and NHS DD
 
+* https://www.renalreg.org/wp-content/uploads/2014/10/The-UK-Renal-Data-Collaboration-UKRDC-and-the-Data-Model-by-Dr-Keith-Simpson-and-Peter-Nicklin.pdf - Project to create a UK Renal Registry that communicates with partners via FHIR
+ * https://www.renalreg.org/wp-content/uploads/2014/09/UK_Renal_Data_Collaboration_White_Paper_1.1.pdf
+ * https://www.renalreg.org/data/ - Has a UK Renal Registry Dataset definition
+
 * http://stackoverflow.com/questions/tagged/hl7-fhir -- Stackoverflow has 260 Q&As so far
 
+* https://twitter.com/FHIRnews
+
 * From GNU Health, there's a python reference library for Fhir: https://pypi.python.org/pypi/fhir
 
 * Someone is having a go at merging Django with other techs to get a Fhir stack: https://github.com/videntity/django-fhir
 
+* Lots of FHIR related postings at https://fhirblog.com
+* As well as at: https://thefhirplace.com
+ * https://thefhirplace.com/2016/08/08/create-my-first-fhir-implementation-guide-using-simplifier/ 
+
 * Or from SMARTonFHIR: https://github.com/smart-on-fhir/client-py
+ * https://fhirblog.com/2016/07/08/what-is-smart-and-why-should-you-care/#more-158596
 
 ### OpenEHR
 
 Scotland went a different way earlier on and supported the Open EHR initiative, something started at UCL, but now international. 
 
 * http://www.openehr.org/home
 
+### SNOMED CT
+The NHS National Information Board (NIB) has specified that SNOMED CT is to be used as the single terminology in all care settings in England, with work to be started by all before Dec 2016, and all systems be implemented before 2020.
+
+* https://www.networks.nhs.uk/nhs-networks/snomed-ct/snomed-ct-webinars/why-snomed-ct
+* http://systems.digital.nhs.uk/data/uktc/snomed
+* Look for the UK SNOMED CT! - https://isd.hscic.gov.uk/trud3/user/guest/group/0/pack/26
+* Python has a module for SNOMED - https://pypi.python.org/pypi/PyMedTermino
+ * Docs at http://pythonhosted.org/PyMedTermino/
+* Mapping is not without its issues: http://www.safescript.com/tmt_error_analysis.html
+
 
 ## Infrastructure
 

docs/_source/requirements.md

@@ -13,3 +13,16 @@ This page is going to evolve a lot over the course of this project, mostly becau
  * [http://techwhirl.com/writing-software-requirements-specifications/]()
  * [https://en.wikipedia.org/wiki/Software_requirements_specification]()
 
+
+## Draft Content
+
+### Technical Requirements
+
+1. FHIR used as the standard for data persistence and communication
+ * Interoperability is essential, FHIR embodies this, be it Human Readability for data, through to use of common technologies like REST APIs and good Documentation.
+
+2. SNOMED CT used as the standard for clinical data coding. The NHS National Information Board (NIB) [has specified that](http://systems.digital.nhs.uk/data/uktc/snomed) SNOMED CT is to be used as the single terminology in all care settings in England. The move to using a single common terminology in electronic integrated care records means:
+ * information can be shared consistently within and across all health and care settings
+ * data can be organised for the benefit of the individual's care, for example highlighting current health problems
+ * data can be organised for the benefit of groups of individuals, for example identifying trends resulting from change in clinical practice
+ * the risk of different interpretations of the record between different care settings can be reduced.