https://wiki.voror.co.uk/api.php?action=feedcontributions&feedformat=atom&user=Jay 2026-10-23T15:20:28Z User contributions MediaWiki 1.46.2 https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4795 2021-05-10T08:40:22Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> Further details explaining the access and authentication levels can be found in the [[Discovery Explorer- Specification]] article.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> == Training Videos ==<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules:<br /> <br /> [https://www.youtube.com/watch?v=4yv0i5W36_o Video]<br /> <br /> [[Discovery Explorer/Access and Navigation|Article]]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> How to create and modify value sets used by queries.:<br /> <br /> [https://www.youtube.com/watch?v=rOqc8H2-52s Video]<br /> <br /> [[Discovery Explorer/Value Set Library|Article]]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4758 2021-05-04T14:51:05Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> == Training Videos ==<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules:<br /> <br /> [https://www.youtube.com/watch?v=4yv0i5W36_o Video]<br /> <br /> [[Discovery Explorer/Access and Navigation|Article]]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> How to create and modify value sets used by queries.:<br /> <br /> [https://www.youtube.com/watch?v=rOqc8H2-52s Video]<br /> <br /> [[Discovery Explorer/Value Set Library|Article]]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4757 2021-05-04T14:48:29Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ===<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules:<br /> <br /> [https://www.youtube.com/watch?v=4yv0i5W36_o Video]<br /> <br /> [[Discovery Explorer/Access and Navigation|Article]]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> How to create and modify value sets used by queries.:<br /> <br /> [https://www.youtube.com/watch?v=rOqc8H2-52s Video]<br /> <br /> [[Discovery Explorer/Value Set Library|Article]]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4756 2021-05-04T14:45:52Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ===<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules:<br /> <br /> [https://www.youtube.com/watch?v=4yv0i5W36_o Video]<br /> <br /> [[Discovery Explorer/Access and Navigation|Article]]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> [https://www.youtube.com/watch?v=rOqc8H2-52s How to create and modify value sets used by queries.]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4755 2021-05-04T14:43:21Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ===<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> [https://youtu.be/4yv0i5W36_o How to logon to the application and navigate around the menus and modules.]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> [https://www.youtube.com/watch?v=rOqc8H2-52s How to create and modify value sets used by queries.]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4754 2021-05-04T14:43:07Z

<p>Jay: Links added</p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ''&lt;u&gt;(links to follow)&lt;/u&gt;''===<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Key features ======<br /> [https://youtu.be/HPk6d_cV6uw Explanation of the key features available in Discovery Explorer.]<br /> <br /> ====== Logon and navigation ======<br /> [https://youtu.be/4yv0i5W36_o How to logon to the application and navigate around the menus and modules.]<br /> <br /> ====== Covid library ======<br /> [https://www.youtube.com/watch?v=uqWROH6UiSY How to use the COVID-19 dashboards.]<br /> <br /> ====== Dashboard library ======<br /> [https://www.youtube.com/watch?v=9MBqcwBsQxQ How to create and view your own dashboards.]<br /> <br /> ====== Maps ======<br /> [https://www.youtube.com/watch?v=i2cpVCd0AY0 How to use the geospatial maps.]<br /> <br /> ====== Query results ======<br /> [https://www.youtube.com/watch?v=echEph4_BPk How to view results of queries and drill-down to records.]<br /> <br /> ====== Query &amp; data set library ======<br /> [https://www.youtube.com/watch?v=7h4d2n7LGyc How to create queries, data sets and visualisations.]<br /> <br /> ====== Query queue ======<br /> [https://www.youtube.com/watch?v=i6eQk3mJpnU Explanation of the query queue module.]<br /> <br /> ====== Value set library ======<br /> [https://www.youtube.com/watch?v=rOqc8H2-52s How to create and modify value sets used by queries.]<br /> <br /> ====== Population counts ======<br /> [https://www.youtube.com/watch?v=tMFBjhGN0As Explanation of the population counts module.]<br /> <br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Access_and_Navigation&diff=4727 2021-04-30T15:34:31Z

<p>Jay: Created page with &quot;== Logging into the Discovery Explorer application and navigating around the menu screens. == &#039;&#039;&lt;small&gt;Prerequisites for logging in:&lt;/small&gt;&#039;&#039; &#039;&#039;&lt;small&gt;Access from your local...&quot;</p> <hr /> <div>== Logging into the Discovery Explorer application and navigating around the menu screens. ==<br /> ''&lt;small&gt;Prerequisites for logging in:&lt;/small&gt;''<br /> <br /> ''&lt;small&gt;Access from your local administrator&lt;/small&gt;''<br /> <br /> ''&lt;small&gt;A mobile phone with a 2 Factor Authentication app such as Google Authenticator or Duo.&lt;/small&gt;''<br /> <br /> ====== Logging in ======<br /> Once you have been granted access you will be issued with the URL for logging onto Explorer. Enter the URL into the address bar in your browser, Discovery Explorer is supported across all the major modern browsers such as Chrome, Firefox, Internet Explorer. We suggest that you use Chrome for the best experience.<br /> <br /> The system will ask you to put in your username and password that you will have already enrolled with and there will be instructions for how to get your username and password [[Discovery Explorer#Access and support|here]].<br /> <br /> If you forget your password, you can click on the forgot my password link where you can put your email address in it will send you a reset link.<br /> <br /> Once your username and password is accepted, Discovery Explorer uses 2 factor authentication so you will need to download the Authenticator application onto mobile phone.<br /> <br /> Each time you log on with your username and password it will ask you for a one-time code that will be presented on the screen on your mobile phone.<br /> <br /> To '''logout''' of the application, you can click out the logout icon on the menu bar below your details or you can drop your username down on the top right and click the logout button there.<br /> <br /> ====== The Menu Bar ======<br /> Across the left-hand side of the application there is the menu bar. If you hover over it, it will fully expand, if you move away from it, it will condense into a narrow bar to save screen space.<br /> <br /> You can also pin the menu bar in place, there is a pin button at the top right of the sidebar where it will remain viewable at all times with slightly less space available to the main screen.<br /> <br /> When you log into the application you get a drop down on the top right which lists the roles that have been assigned to your user account.<br /> <br /> Normally most users would only have one or two different roles depending on their level of access.<br /> <br /> Each of these roles allows you to switch quickly into a new authorised area of the system where you will get access to different organisational data and either patient identifiable data or deidentified data dependent on your permissions. These are controlled by your local administrator.<br /> <br /> For instance you may have a role which only allows you to view data STP level or you may have roles that let you drill down at practise level and view patient identifiable data from queries that you build.<br /> <br /> Then to get to each one of the modules within the system, select them from the menu:<br /> <br /> * '''Covid library''' showing the library available Covid dashboards.<br /> * '''Dashboard Library''' contains the dashboards built by you and other users.<br /> * '''Maps''' contains geospatial Maps<br /> * '''Query results''' contains the main module for viewing all the results of the queries that have been built by you and other users.<br /> * '''Query &amp; Data Set Library''' contains data sets built by you and other users.<br /> * '''Query Queue''' shows what queries have been run and are in progress.<br /> * '''Value Set Library''' contains values sets with all your codes in it that you're going to use to build searches with<br /> * '''Population Counts''' contains statistics for all the different organisations that you have authorised access to.<br /> * '''Audit Log''' allows administrators to view who's been using the system and what data they've been accessing.<br /> * '''Tutorials''' contains video tutorials on how to use each one of these modules in more detail. Links are also available above.<br /> <br /> The layout in many of the screens is consistent, there is:<br /> <br /> * A user bar that is always across the top with your user and role information.<br /> <br /> * The title bar which will show you the module that you're in with a brief explanation of what the module is.<br /> <br /> * A of filter where you can search for items in libraries quickly, for instance if you go onto the Queries and data set library here and wanted to quickly search for any queries related to diabetes you can type “''diabetes”'' and quickly return those queries.<br /> <br /> * Most of the modules have a drop down on a row item with a &gt; where you can see further information about that item, you click on the tool and open and close each row which will show you more information about the information behind that item.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4726 2021-04-30T12:31:37Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ''&lt;u&gt;(links to follow)&lt;/u&gt;''===<br /> Training videos are available within the application to help you to navigate and utilise the system. Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules.<br /> <br /> ====== Covid library ======<br /> How to use the COVID-19 dashboards.<br /> <br /> ====== Dashboard library ======<br /> How to create and view your own dashboards.<br /> <br /> ====== Maps ======<br /> How to use the geospatial maps.<br /> <br /> ====== Query results ======<br /> How to view results of queries and drill-down to records.<br /> <br /> ====== Query &amp; data set library ======<br /> How to create queries, data sets and visualisations.<br /> <br /> ====== Query queue ======<br /> Explanation of the query queue module.<br /> <br /> ====== Value set library ======<br /> How to create and modify value sets used by queries.<br /> <br /> ====== Population counts ======<br /> Explanation of the population counts module.<br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4725 2021-04-30T12:29:23Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ===<br /> Below are videos that will assist you in using Discovery Explorer:<br /> <br /> ====== Logon and navigation ======<br /> How to logon to the application and navigate around the menus and modules.<br /> <br /> ====== Covid library ======<br /> How to use the COVID-19 dashboards.<br /> <br /> ====== Dashboard library ======<br /> How to create and view your own dashboards.<br /> <br /> ====== Maps ======<br /> How to use the geospatial maps.<br /> <br /> ====== Query results ======<br /> How to view results of queries and drill-down to records<br /> <br /> ====== Query &amp; data set library ======<br /> How to create queries, data sets and visualisations<br /> <br /> ====== Query queue ======<br /> Explanation of the query queue module<br /> <br /> ====== Value set library ======<br /> How to create and modify value sets used by queries<br /> <br /> ====== Population counts ======<br /> Explanation of the population counts module<br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4644 2021-04-28T12:24:55Z

<p>Jay: </p> <hr /> <div>== Explorer and it's capabilities ==<br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.<br /> <br /> == Access and support ==<br /> Access and support are controlled by the Discovery Programme team in London. Access is controlled by [mailto:andy.thomas3@nhs.net Andy Thomas] and can be requested using this [https://app.smartsheet.com/b/form/45cfd0c985554afdb8670e459836c4f1 Discovery Explorer User Request Form]<br /> <br /> === Training Videos ===<br /> Below are videos that will assist you in using Discovery Explorer<br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4643 2021-04-28T12:15:53Z

<p>Jay: Jay moved page Discovery Explorer - Capabilities to Discovery Explorer without leaving a redirect</p> <hr /> <div>Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4642 2021-04-28T12:15:28Z

<p>Jay: </p> <hr /> <div>Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4641 2021-04-28T12:15:06Z

<p>Jay: </p> <hr /> <div>{{DISPLAYTITLE:Discovery Explorer}}<br /> <br /> Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4640 2021-04-28T12:14:13Z

<p>Jay: </p> <hr /> <div>Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested.<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4639 2021-04-28T12:13:55Z

<p>Jay: </p> <hr /> <div>Discovery Explorer is a user interface web application which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4256 2021-04-02T14:04:45Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> <br /> [[File:Menu-value_set_library.png|alt=|frameless]]<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To [https://wiki.discoverydataservice.org/index.php?title=Discovery_Explorer/Value_Set_Library#Creating_a_value_set create a value set group], click on the plus button on the header row '''''(3).'''''<br /> <br /> To [https://wiki.discoverydataservice.org/index.php?title=Discovery_Explorer/Value_Set_Library#Populating.2Fediting_a_value_set view and edit a value set group] click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> [[File:Value_Set_Library.png|alt=|frameless|876x876px]]<br /> <br /> === Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use [https://wiki.discoverydataservice.org/index.php?title=Discovery_Explorer/Value_Set_Library#Add_concept_through_find_concepts Find Concepts] '''''(3)''''' to search for all or part of your code, or use the [https://wiki.discoverydataservice.org/index.php?title=Discovery_Explorer/Value_Set_Library#Add_concept_through_plus_icon '''+''' button] '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> <br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through Find Concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the [https://termbrowser.nhs.uk/? SNOMED-CT] browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4255 2021-04-02T13:58:42Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> <br /> [[File:Menu-value_set_library.png|alt=|frameless]]<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> [[File:Value_Set_Library.png|alt=|frameless|876x876px]]<br /> <br /> === Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> <br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4254 2021-04-02T13:57:31Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> <br /> [[File:Menu-value_set_library.png|alt=|frameless]]<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> === [[File:Value_Set_Library.png|alt=|frameless|876x876px]] ===<br /> === Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> <br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4253 2021-04-02T13:40:37Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> <br /> [[File:Menu-value_set_library.png|alt=|frameless]]<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> === [[File:Value_Set_Library.png|alt=|frameless|876x876px]] Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> <br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4252 2021-04-02T13:39:50Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> <br /> [[File:Menu-value_set_library.png|alt=|frameless]]<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> === [[File:Value_Set_Library.png|alt=|frameless|876x876px]] Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4251 2021-04-02T13:39:28Z

<p>Jay: </p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> [[File:Menu-value set library.png|left|frameless]]<br /> &lt;br /&gt;<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> <br /> === [[File:Value_Set_Library.png|alt=|frameless|876x876px]] Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> <br /> [[File:Pencil_icon.png|alt=|frameless]]&lt;br /&gt;<br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> <br /> [[File:Bin_Icon.png|alt=]]<br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> <br /> [[File:Concept_Selector.png|alt=|frameless|897x897px]]<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> <br /> [[File:Value_set_code_editor.png|alt=|frameless|337x337px]]<br /> <br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer/Value_Set_Library&diff=4250 2021-04-02T13:37:40Z

<p>Jay: Created page</p> <hr /> <div>The article describes to navigate the value set library and add, edit and remove value sets and concepts.<br /> <br /> === Accessing the value set library ===<br /> Access the Value set library using menu on the left of the page.<br /> [[File:Menu-value set library.png|left|frameless]]<br /> &lt;br /&gt;<br /> <br /> === The Value set library ===<br /> Search for an existing value set group using &quot;Filter folder&quot; '''''(1)''''' , or by typing all or part of your value set group into the search bar '''''(2).'''''<br /> <br /> To create a value set group, click on the plus button on the header row '''''(3).'''''<br /> <br /> To view and edit a value set group click on the value set group's name in the row '''''(4).'''''<br /> <br /> Use the check boxes to use the multiselect functionality '''''(5).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(6).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(7).'''''<br /> [[File:Value Set Library.png|left|frameless|876x876px]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;br /&gt;<br /> <br /> === Creating a value set ===<br /> Type in a value set folder name, create a new folder or assign your value set to an existing folder using the existing name.<br /> <br /> Give your value set group a name, both of these fields are required.<br /> <br /> Clicking save will create the group, you then need to locate the group to populate the value set group.<br /> <br /> [[File:Value Set Editor.png|frameless|411x411px]]<br /> <br /> === Populating/editing a value set ===<br /> The columns in the value set group window displays the Value set name, data type, original code, original term, and when it was last updated within the value set group.<br /> <br /> Data types can be Observation, Ethnicity, Encounter or Medication.<br /> <br /> Select individual or sub groups of value sets by clicking on filter value sets '''''(1).'''''<br /> <br /> Search for value sets or codes using all or part of any column '''''(2).'''''<br /> <br /> If you wish to add a code use Find Concepts '''''(3)''''' to search for all or part of your code, or use the '''+''' button '''''(4)''''' if you have the full details of the code.<br /> <br /> Edit a code by clicking on the check box '''''(5)''''' and clicking on the pencil icon that appears in the header row. <br /> [[File:Pencil icon.png|left|frameless]]<br /> <br /> <br /> To remove a code from the value set and group click on the check box '''''(5)''''' and use the bin icon to remove your selection.<br /> [[File:Bin Icon.png|left]]<br /> <br /> <br /> You can download the value set group into a CSV file for use elsewhere by clicking on the download button '''''(6).'''''<br /> <br /> To add more items in view per page, use the items per page function '''''(7).'''''<br /> <br /> To manually move between pages, use the next page/previous page buttons '''''(8).'''''<br /> &lt;br /&gt;<br /> [[File:Concept Selector.png|left|frameless|897x897px]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;br /&gt;<br /> <br /> === Add concept through find concepts ===<br /> Use the search bar to search for all or part of your code term '''''(1).'''''<br /> <br /> The search will return any matches, present the original code, original term, the use count for that code to tell you how frequent that code is in use.<br /> <br /> Multiple codes can be selected to be added at once using the check boxes '''''(2).'''''<br /> <br /> When added single or multiple codes, you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously used name '''''(3).'''''<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication '''''(4).'''''<br /> <br /> Confirm your selection by clicking on Add selected concepts, this cannot be selected until the value set name and data type is confirmed '''''(5)'''''.<br /> <br /> [[File:Concept browser.png|frameless|889x889px]]<br /> <br /> === Add concept through plus icon ===<br /> To add a code through the Value set code editor you must select the value set name. Create a value set typing a new name or add to a value set by matching a previously<br /> <br /> used name.<br /> <br /> Select a data type of Observation, Ethnicity, Encounter or Medication.<br /> <br /> Type in the correct original code and then the original term, use the link to the SNOMED-CT browser to confirm your code.<br /> [[File:Value set code editor.png|left|frameless|337x337px]]<br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Concept_browser.png&diff=4249 2021-04-02T13:36:56Z

<p>Jay: </p> <hr /> <div>Concept browser</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Value_set_code_editor.png&diff=4248 2021-04-02T13:33:45Z

<p>Jay: </p> <hr /> <div>Value set code editor</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Concept_Selector.png&diff=4247 2021-04-02T13:30:15Z

<p>Jay: </p> <hr /> <div>Concept Selector</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Bin_Icon.png&diff=4246 2021-04-02T13:27:04Z

<p>Jay: </p> <hr /> <div>Bin Icon</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Pencil_icon.png&diff=4245 2021-04-02T13:24:54Z

<p>Jay: </p> <hr /> <div>Pencil icon</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Value_Set_Editor.png&diff=4244 2021-04-02T13:21:28Z

<p>Jay: </p> <hr /> <div>Value Set Editor</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Value_Set_Library.png&diff=4243 2021-04-02T13:17:46Z

<p>Jay: </p> <hr /> <div>Value Set Library</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Menu-value_set_library.png&diff=4242 2021-04-02T13:11:36Z

<p>Jay: </p> <hr /> <div>Menu/value set library</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Explorer&diff=4194 2021-03-25T12:04:48Z

<p>Jay: Created page</p> <hr /> <div>Discovery Explorer is a user interface web application on top which allows users to build queries, dashboards and view results without any knowledge needed of the database structure or of the SQL language.<br /> <br /> Explorer will by nature produce more accurate results because it ‘understands’ the database structures and clinical model, and the machine generates the SQL that’s already been pre-tested<br /> <br /> The features and benefits of using Discovery Explorer are:<br /> <br /> * Create and build your own value sets with an inbuilt browser.<br /> * Bulk upload your value sets from a CSV file.<br /> * Create your own detailed queries with our intuitive query engine that is able to handle highly sophisticated queries in a user friendly experience - no SQL skills required.<br /> * Build queries to identify patients at risk or in need of further intervention.<br /> * View historical trends of query results.<br /> * View registries to show compliance of QOF and other data sets, easily comparing, practices, CCGS and hospitals.<br /> * Drill-down to lists of patients behind query results.<br /> * View each patient’s complete integrated care record.<br /> * Use our dashboard suit or create a csv output for your query to interrogate in 3rd party applications.<br /> * Create outputs containing demographic, medication, encounter or clinical data.<br /> * View intuitive dashboards at STP, CCG, PCN or practice level, patient identifiable or de identifiable dependent on your permission level.<br /> * View geospatial maps show prevalence of diseases, conditions or vaccination up take by area.</div>

Jay https://wiki.voror.co.uk/index.php?title=Data_%26_Analytics_passport_and_accelerator_challenge&diff=2762 2020-09-23T16:40:07Z

<p>Jay: Created page with &quot;We have been asked to share this message with Data and Analytical teams so that they are able to contribute to the shaping of the solution. If you have any other contacts whi...&quot;</p> <hr /> <div>We have been asked to share this message with Data and Analytical teams so that they are able to contribute to the shaping of the solution.<br /> <br /> If you have any other contacts which you think might be interested in taking part please do share this further. <br /> <br /> === '''''Have your say on upcoming analytics initiatives: Passport and Accelerator challenge''''' === <br /> <br /> ''We would really appreciate your thoughts on a project which has the ambition to develop the Data and Analytical workforce throughout health and social care, ensuring it becomes a recognised  professional body of people with clearly defined and progressive career pathways to support that ambition.  We are interested in capturing your thoughts on the potential of a Data and Analyst Passport to enable mobility from within health and care analytics by recording qualifications, skills and key work experiences etc. '' <br /> <br /> ''We are also interested in learning whether you think a Data and Analytics Accelerator challenge would be of interest to you – this would involve forming virtual teams (NHS, Local Authority, Public health, commercial orgs, etc.) as a competitive and collective power to help solve a complex issue, with the winning team being rewarded in some way – financially or other.  We’d like to understand your views on what would make the competition both successful and fun – what should the prize be, how would the winning team be decided and what would make you want to take part.'' <br /> <br /> ''A very brief survey can be found here'' https://www.menti.com/5dgzc6tjbz<br /> &lt;br /&gt;</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_(RSD)_Schema_(Compass_1)&diff=2703 2020-09-16T16:17:44Z

<p>Jay: Added encounter_additional &amp; encounter_event tables</p> <hr /> <div><br /> == Table: allergy_intolerance ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |<br /> <br /> |<br /> <br /> |-<br /> <br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> <br /> |encounter_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |<br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the clinical code is recorded for<br /> |<br /> <br /> |-<br /> <br /> |date_precision_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> |-<br /> <br /> |snomed_concept_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The SNOMED code<br /> |<br /> <br /> |-<br /> <br /> |original_code<br /> |varchar(100) CHARACTER SET utf8 COLLATE utf8_bin<br /> |DEFAULT NULL<br /> |The original code from the source system<br /> |<br /> <br /> |-<br /> <br /> |original_term<br /> |varchar(1000)<br /> |DEFAULT NULL<br /> |The original code term from the source system<br /> |<br /> <br /> |-<br /> <br /> |is_review<br /> |tinyint(1)<br /> |NOT NULL<br /> |Is this instance of the code a review of a previous encounter<br /> |<br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY allergy_intolerance_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY allergy_intolerance_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY allergy_intolerance_snomed_concept_id (snomed_concept_id)<br /> |-<br /> <br /> | colspan=&quot;5&quot; | <br /> <br /> |}<br /> <br /> == Table: appointment ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |schedule_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The schedule the patient was put on to book multiple appointments. ID unique to the applied schedule <br /> |schedule.id<br /> |-<br /> <br /> |start_date <br /> |datetime <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |planned_duration <br /> |int(11) <br /> |DEFAULT NULL <br /> |The time allocated for the appointment, not necessarily the actual duration always in minutes<br /> |<br /> <br /> <br /> |-<br /> <br /> |actual_duration <br /> |int(11) <br /> |DEFAULT NULL <br /> |Time between sent in and left always in minutes<br /> |<br /> <br /> <br /> |-<br /> <br /> |appointment_status_id <br /> |smallint(6) <br /> |NOT NULL <br /> |The status of the appointment e.g. arrived/sent in/left/DNA<br /> |appointment.status.id<br /> |-<br /> <br /> |patient_wait <br /> |int(11) <br /> |DEFAULT NULL <br /> |How long the patient waited from being marked as arrived to being sent in<br /> |<br /> <br /> <br /> |-<br /> <br /> |patient_delay <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |sent_in <br /> |datetime <br /> |DEFAULT NULL <br /> |Date and time the patient was sent into the practitioner<br /> |<br /> <br /> <br /> |-<br /> <br /> |left <br /> |datetime <br /> |DEFAULT NULL <br /> |Date and time the patient left the practitioner<br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY appointment_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY appointment_patient_id (patient_id)<br /> |}<br /> == Table: appointment_status ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: date_precision ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(11) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: encounter ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id<br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |appointment_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |appointment.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |The date the clinical code is recorded for<br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |snomed_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The SNOMED code<br /> |<br /> <br /> <br /> |-<br /> <br /> |original_code <br /> |varchar(100) <br /> |DEFAULT NULL <br /> |The original code from the source system<br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |The original code term from the source system<br /> |<br /> <br /> <br /> |-<br /> <br /> |episode_of_care_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |Is this instance of the code a review of a previous encounter<br /> |<br /> <br /> <br /> |-<br /> <br /> |service_provider_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY encounter_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY encounter_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fki_encounter_appointment_id (appointment_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fki_encounter_patient_id_organization_id (patient_id,organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY encounter_snomed_concept_id_clinical_effective_date (snomed_concept_id,clinical_effective_date),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY snomed_concept_id_clinical_effective_date_patient_id (snomed_concept_id,clinical_effective_date,patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY patient_id_clinical_effective_date_snomed_concept_id (patient_id,clinical_effective_date,snomed_concept_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY encounter_snomed_concept_id (snomed_concept_id)<br /> |}<br /> <br /> == Table: encounter_additional ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> |id<br /> |bigint <br /> |NOT NULL<br /> |Same as the id column on the encounter table or encounter_event id column (sub encounters)<br /> |<br /> |-<br /> |property_id<br /> |varchar(255)  <br /> |NOT NULL<br /> |IM reference (i.e. Admission method)<br /> |<br /> |-<br /> |value_id<br /> |varchar(255) <br /> |NOT NULL<br /> |IM reference (i.e. Emergency admission)<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |PRIMARY KEY (id, property_id)<br /> |}<br /> <br /> == Table: encounter_detail ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |Same as the id column on the encounter table <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |episode_of_care_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |The date the clinical code is recorded for<br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> |<br /> <br /> |-<br /> <br /> |recording_practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |Who recorded the encounter <br /> |<br /> <br /> <br /> |-<br /> <br /> |recording_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> |-<br /> <br /> |appointment_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The unique reference for that appointment<br /> |appointment.id<br /> |-<br /> <br /> |service_provider_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |Organisation that performed the encounter <br /> |<br /> <br /> <br /> |-<br /> <br /> |location_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |Where the encounter took place <br /> |location.id<br /> |-<br /> <br /> |end_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |duration_minutes <br /> |int(11) <br /> |DEFAULT NULL <br /> |Duration always in minutes <br /> |<br /> <br /> <br /> |-<br /> <br /> |completion_status_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |healthcare_service_type_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |interaction_mode_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |administrative_action_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |purpose_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |disposition_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |site_of_care_type_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |patient_status_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY ix_encounter_detail_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_encounter_detail_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_encounter_detail_appointment_id (appointment_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_encounter_detail_patient_id_organization_id (patient_id,organization_id)<br /> |}<br /> <br /> == Table: encounter_event ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |<br /> <br /> |<br /> <br /> |-<br /> <br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> <br /> |encounter_id<br /> |bigint<br /> |NOT NULL<br /> |<br /> <br /> |registration.type.id<br /> |-<br /> <br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> <br /> |practitioner.id<br /> <br /> |-<br /> <br /> |appointment_id<br /> |bigint<br /> |DEFAULT NULL<br /> |<br /> <br /> |appointment.id<br /> <br /> |-<br /> <br /> |clinical_effective_date<br /> |datetime<br /> |DEFAULT NULL<br /> |<br /> <br /> |<br /> |-<br /> <br /> |date_precision_id<br /> |smallint<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> <br /> |<br /> |-<br /> |snomed_concept_id<br /> |bigint<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |original_code<br /> |varchar(100) binary<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |original_term<br /> |varchar(1000)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |episode_of_care_id<br /> |bigint<br /> |DEFAULT NULL<br /> |<br /> |episode.of.care.id<br /> |-<br /> |service_provider_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |location_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Where the encounter took place<br /> |location.id<br /> |-<br /> |finished<br /> |boolean<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |}<br /> == Table: episode_of_care ==<br /> <br /> 0PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |registration_type_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |registration.type.id<br /> |-<br /> <br /> |date_registered <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_registered_end <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |usual_gp_practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |practitioner.id<br /> |-<br /> <br /> |registration_status_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |registration.status<br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY episode_of_care_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_registration_type_id (registration_type_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_date_registered (date_registered),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_date_registered_end (date_registered_end),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_person_id (person_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY episode_of_care_organization_id (organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY reg_type_id_patient_id_date_registered_date_registered_end (registration_type_id,patient_id,date_registered,date_registered_end)<br /> |}<br /> == Table: ethnicity_lookup ==<br /> <br /> PRIMARY KEY (ethnic_code)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> <br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |ethnic_code <br /> |char(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ethnic_name <br /> |varchar(100) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (ethnic_code)<br /> |}<br /> == Table: flag ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |<br /> <br /> <br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |is_active<br /> |tinyint(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |flag_text<br /> |text<br /> | <br /> |This is a warning set by the publisher regarding he patient <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY flag_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fk_flag_patient_id_organization_id (patient_id,organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fk_flag_date_precision (date_precision_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY flag_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | CONSTRAINT fk_flag_date_precision FOREIGN KEY (date_precision_id) REFERENCES <br /> |-<br /> <br /> | colspan=&quot;5&quot; | CONSTRAINT fk_flag_patient_id_organization_id FOREIGN KEY (patient_id, organization_id) REFERENCES patient (id, organization_id)<br /> |}<br /> <br /> == Table: local_authority_lookup ==<br /> <br /> PRIMARY KEY (local_authority_code)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |local_authority_code <br /> |varchar(9) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |local.authority.code<br /> |-<br /> <br /> |local_authority_name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (local_authority_code)<br /> |}<br /> == Table: location ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |The name of a location set by the publisher. E.g. ward, clinic, domiciliary<br /> |<br /> <br /> <br /> |-<br /> <br /> |type_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |type_desc <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |postcode <br /> |varchar(10) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |managing_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY location_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fk_location_managing_organisation_id (managing_organization_id)<br /> |}<br /> == Table: Isoa_lookup ==<br /> <br /> PRIMARY KEY (lsoa_code)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> |lsoa_code <br /> |char(9)<br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |lsoa_name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |imd_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Index of Multiple Deprivation (IMD) Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |imd_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Index of Multiple Deprivation (IMD) Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |imd_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Index of Multiple Deprivation (IMD) Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |income_score <br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Income Score (rate) <br /> |<br /> <br /> <br /> |-<br /> <br /> |income_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |income_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |employment_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Employment Score (rate) <br /> |<br /> <br /> <br /> |-<br /> <br /> |employment_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Employment Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |employment_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Employment Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |education_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Education Skills and Training Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |education_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Education Skills and Training Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |education_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Education Skills and Training Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |health_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Health Deprivation and Disability Score <br /> |<br /> <br /> |-<br /> <br /> |health_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Health Deprivation and Disability Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |health_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Health Deprivation and Disability Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |crime_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Crime Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |crime_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Crime Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |crime_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Crime Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |housing_and_services_barriers_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Barriers to Housing and Services Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |housing_and_services_barriers_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Barriers to Housing and Services Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |housing_and_services_barriers_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Barriers to Housing and Services Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |living_environment_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Living Environment Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |living_environment_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Living Environment Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |living_environment_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Living Environment Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaci_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Children Index (IDACI) Score (rate) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaci_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Children Index (IDACI) Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaci_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Children Index (IDACI) Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaopi_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Older People (IDAOPI) Score (rate) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaopi_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Older People (IDAOPI) Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |idaopi_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Income Deprivation Affecting Older People (IDAOPI) Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |children_and_young_sub_domain_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Children and Young People Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |children_and_young_sub_domain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Children and Young People Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |children_and_young_sub_domain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Children and Young People Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |adult_skills_sub_somain_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Adult Skills Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |adult_skills_sub_somain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Adult Skills Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |adult_skills_sub_somain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Adult Skills Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |geographical_barriers_sub_domain_score <br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Geographical Barriers Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |geographical_barriers_sub_domain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Geographical Barriers Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |geographical_barriers_sub_domain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Geographical Barriers Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |wider_barriers_sub_domain_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Wider Barriers Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |wider_barriers_sub_domain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Wider Barriers Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |wider_barriers_sub_domain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Wider Barriers Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |indoors_sub_domain_score <br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Indoors Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |indoors_sub_domain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Indoors Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |indoors_sub_domain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Indoors Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |outdoors_sub_domain_score<br /> |decimal(53) <br /> |DEFAULT NULL <br /> |Outdoors Sub-domain Score <br /> |<br /> <br /> <br /> |-<br /> <br /> |outdoors_sub_domain_rank <br /> |int(11) <br /> |DEFAULT NULL <br /> |Outdoors Sub-domain Rank (where 1 is most deprived) <br /> |<br /> <br /> <br /> |-<br /> <br /> |outdoors_sub_domain_decile <br /> |int(11) <br /> |DEFAULT NULL <br /> |Outdoors Sub-domain Decile (where 1 is most deprived 10% of LSOAs) <br /> |<br /> <br /> <br /> |-<br /> <br /> |total_population <br /> |int(11) <br /> |DEFAULT NULL <br /> |Total population: mid 2012 (excluding prisoners) <br /> |<br /> <br /> <br /> |-<br /> <br /> |dependent_children_0_to_15 <br /> |int(11) <br /> |DEFAULT NULL <br /> |Dependent Children aged 0-15: mid 2012 (excluding prisoners) <br /> |<br /> <br /> <br /> |-<br /> <br /> |population_16_to_59 <br /> |int(11) <br /> |DEFAULT NULL <br /> |Population aged 16-59: mid 2012 (excluding prisoners) <br /> |<br /> <br /> <br /> |-<br /> <br /> |older_population_60_and_over <br /> |int(11) <br /> |DEFAULT NULL <br /> |Older population aged 60 and over: mid 2012 (excluding prisoners) <br /> |<br /> <br /> <br /> |-<br /> <br /> ! colspan=&quot;5&quot; | PRIMARY KEY (lsoa_code)<br /> |}<br /> == Table: medication_order ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |encounter_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |dmd_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |dose <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |quantity_value <br /> |double<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |quantity_unit <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |duration_days <br /> |int(11) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |estimated_cost <br /> |double<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |medication_statement_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id)<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY medication_order_id (id)<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY medication_order_patient_id (patient_id)<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY medication_order_dmd_id (dmd_id)<br /> |}<br /> == Table: medication_statement ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |encounter_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |dmd_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |is_active<br /> |tinyint(4) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |cancellation_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |dose <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |quantity_value<br /> |double<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |quantity_unit <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |medication_statement_&lt;br /&gt;authorisation_type_id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY medication_statement_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY medication_statement_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY medication_statement_dmd_id (dmd_id)<br /> |}<br /> == Table: medication_statement_authorisation_type ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: msoa_lookup ==<br /> <br /> PRIMARY KEY (msoa_code)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |msoa_code char(9) <br /> |NOT NULL<br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |msoa_name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (msoa_code) <br /> |}<br /> == Table: observation ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |encounter_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |snomed_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |result_value <br /> |double<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |result_value_units <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |result_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |result_text<br /> |text<br /> | <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |result_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_code <br /> |varchar(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |is_problem<br /> |tinyint(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |is_review<br /> |tinyint(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |problem_end_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |parent_observation_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY observation_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY observation_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY observation_snomed_concept_id (snomed_concept_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY observation_snomed_concept_id_is_problem (snomed_concept_id,is_problem),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY observation_snomed_concept_id_value (snomed_concept_id,result_value),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_observation_organization_id (organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_observation_clinical_effective_date (clinical_effective_date),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_observation_person_id (person_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY observation_original_code (original_code)<br /> |}<br /> == Table: organization ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ods_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |type_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |type_desc <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |postcode <br /> |varchar(10) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |parent_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |latitude<br /> |decimal(108) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |longitude<br /> |decimal(118) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY organization_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY fki_organization_parent_organization_id (parent_organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY organization_id_parent_organization_id (id,parent_organization_id)<br /> |}<br /> == Table: patient ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |patient_gender_id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |pseudo_id <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_years <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_months <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_weeks <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_of_death <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |postcode_prefix <br /> |varchar(20) <br /> |DEFAULT NULL <br /> |First part of the postcode<br /> |<br /> <br /> <br /> |-<br /> <br /> |lsoa_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |msoa_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |msoa.lookup.id<br /> |-<br /> <br /> |ethnic_code <br /> |char(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ward_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |local_authority_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |registered_practice_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |organisation.id<br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY patient_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY patient_person_id (person_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY organization_id (organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY patient_id_organization_id (id,organization_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY organization_id_date_of_death_id (organization_id,date_of_death,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY patient_date_of_death (date_of_death),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY postcode_prefix (postcode_prefix),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY pseudo_id (pseudo_id)<br /> |}<br /> == Table: patient_gender ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(10) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: patient_uprn ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organisation.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |lsoa_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |Isoa.lookup<br /> |-<br /> <br /> |pseudo_uprn <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |qualifier <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |algorithm <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |match <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |no_address<br /> |tinyint(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |invalid_address<br /> |tinyint(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |missing_postcode<br /> |tinyint(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |invalid_postcode<br /> |tinyint(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |should_be_ignored <br /> |bit(1) <br /> |DEFAULT b'0' <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |property_class <br /> |varchar(10) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ncmp_uprn <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ncmp_pid <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ncmp_pid_valid<br /> |tinyint(4) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY patient_uprn_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix_patient_uprn_patient_org_uprn (patient_id,organization_id,pseudo_uprn),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY ix1 (patient_id)<br /> |}<br /> == Table: person ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |patient_gender_id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |pseudo_id <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_years <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_months <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |age_weeks <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_of_death <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |postcode_prefix <br /> |varchar(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |lsoa_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |lsoa.lookup.id<br /> |-<br /> <br /> |msoa_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |msoa.lookup.id<br /> |-<br /> <br /> |ethnic_code <br /> |char(1)<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ward_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |ward.code.id<br /> |-<br /> <br /> |local_authority_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |registered_practice_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY person_id (id)<br /> |}<br /> == Table: practitioner ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organisation.id<br /> |-<br /> <br /> |name <br /> |varchar(1024) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |role_code <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |role_desc <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY practitioner_id (id)<br /> |}<br /> == Table: procedure_request ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |encounter_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |snomed_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |procedure_request_status_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_code <br /> |varchar(100) CHARACTER SET utf8 COLLATE utf8_bin <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY procedure_request_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY procedure_request_patient_id (patient_id)<br /> |}<br /> == Table: procedure_request_status ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: referral_request ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Unique individual across all organisations <br /> |person.id<br /> |-<br /> <br /> |encounter_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |encounter.id<br /> |-<br /> <br /> |practitioner_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> <br /> |clinical_effective_date <br /> |date <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |date_precision_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> <br /> <br /> |-<br /> <br /> |snomed_concept_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |requester_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |recipient_organization_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |priority_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |referral.request.priority<br /> |-<br /> <br /> |type_id <br /> |smallint(6) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |referral.request.type<br /> |-<br /> <br /> |mode <br /> |varchar(50) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |outgoing_referral *<br /> |tinyint(1) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_code <br /> |varchar(100) CHARACTER SET utf8 COLLATE utf8_bin <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |original_term <br /> |varchar(1000) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |is_review<br /> |tinyint(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY referral_request_id (id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY referral_request_patient_id (patient_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | KEY referral_request_snomed_concept_id (snomed_concept_id)<br /> |}<br /> == Table: referral_request_priority ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: referral_request_type ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |value <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id) <br /> |}<br /> == Table: registration_status ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |code <br /> |varchar(10) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |description <br /> |varchar(50) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |is_active<br /> |tinyint(1) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: registration_status_history ==<br /> <br /> PRIMARY KEY (organization_id,person_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id <br /> |bigint(20) <br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |patient_id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |patient.id<br /> |-<br /> <br /> |person_id <br /> |bigint(20) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |person.id<br /> |-<br /> <br /> |episode_of_care_id <br /> |bigint(20) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |episode.of.care.id<br /> |-<br /> <br /> |registration_status_id <br /> |int(11) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |registration.status.id<br /> |-<br /> <br /> |start_date <br /> |datetime <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |end_date <br /> |datetime <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,id,patient_id,person_id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY ux_registration_status_history_id (id)<br /> |-<br /> <br /> | colspan=&quot;5&quot; | ENGINE=InnoDB DEFAULT CHARSET=latin1 COMMENT='stores registration status history for GP registrations';<br /> |}<br /> == Table: registration_type ==<br /> <br /> PRIMARY KEY (id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id <br /> |smallint(6) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |code <br /> |varchar(10) <br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |description<br /> |varchar(30)<br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (id)<br /> |}<br /> == Table: schedule ==<br /> <br /> PRIMARY KEY (organization_id,id)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |id<br /> |bigint(20)<br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL <br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> <br /> |practitioner_id bigint(20) <br /> |bigint(20)<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |practitioner.id<br /> |-<br /> <br /> |start_date <br /> |date<br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |type<br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |location<br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |location.id<br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (organization_id,id),<br /> |-<br /> <br /> | colspan=&quot;5&quot; | UNIQUE KEY schedule_id (id)<br /> |}<br /> == Table: ward_lookup ==<br /> <br /> PRIMARY KEY (ward_code)<br /> <br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot; border=&quot;1&quot;<br /> !Column name<br /> !Data type<br /> !Constraint<br /> !Comments<br /> !References<br /> |-<br /> <br /> |ward_code<br /> |varchar(9)<br /> |NOT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> |ward_name <br /> |varchar(255) <br /> |DEFAULT NULL <br /> |<br /> <br /> <br /> |<br /> <br /> <br /> |-<br /> <br /> | colspan=&quot;5&quot; | PRIMARY KEY (ward_code)<br /> |}</div>

Jay https://wiki.voror.co.uk/index.php?title=EMIS_Notification_of_Essential_Bulk_Extracts_Maintenance_this_28th-31st_August&diff=2582 2020-08-26T14:03:48Z

<p>Jay: Created page with &quot;The following is a notification we have received from EMIS Health regarding their bulk extract service for maintenance this weekend 28th-31st August. This will affect customer...&quot;</p> <hr /> <div>The following is a notification we have received from EMIS Health regarding their bulk extract service for maintenance this weekend 28th-31st August. This will affect customers using a Discovery Data Service Remote Subscriber Database. Please review the notification below and contact your Account Manager if you have any queries.<br /> <br /> <br /> '''Notification from EMIS Health as follows:'''<br /> <br /> ''EMIS are required to undertake essential maintenance on the underlying architecture supporting Bulk Extract Interface in order to maintain service performance and availability, and keep within the boundaries of their support agreements with vendors.''<br /> <br /> <br /> ''This work is being planned to take place urgently over this coming Bank Holiday weekend, with the expectation that this will minimise disruption. The work is expected to take up to four days whilst we work with the system vendors (Microsoft and HPe) carrying out the maintenance.''<br /> <br /> <br /> ''As a result, EMIS do not expect to generate any extracts from 28th August – 31st August inclusive. When extract generation restarts on 1st September, there will be a risk of a reduced service and suspension of bulk and rebulks for up to 1 week whilst the extract servers catch up with the data processing. No data will be lost.''<br /> <br /> <br /> ''EMIS apologise for the disruption that this may cause, it is unfortunately unavoidable and wholly necessary to ensure future service continuity.''<br /> <br /> <br /> ''We will send a further communication once the work has completed.''</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_(RSD)_Schema_(Compass_2)&diff=2248 2020-08-14T13:04:14Z

<p>Jay: Added comments provided by Stu</p> <hr /> <div>== Table: allergy_intolerance ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the allergy<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the encounter this allergy was record in<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |Date<br /> |DEFAULT NULL<br /> |The date the clinical code is recorded for<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |Int<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |is_review<br /> |boolean<br /> |NOT NULL<br /> |Is this instance of the code a review of a previous encounter<br /> |<br /> |-<br /> |core_concept_id<br /> |Int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the allergy<br /> |<br /> |-<br /> |non_core_concept_id<br /> |Int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the allergy<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age the patient was at the time of this event<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |NOT NULL<br /> |The date the allergy was recorded<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_allergy_intolerance_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_allergy_intolerance_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_allergy_intolerance_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_allergy_intolerance_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: appointment ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the appointment<br /> |<br /> |-<br /> |organization_id<br /> |varchar(36)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |varchar(36)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |schedule_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The schedule the patient was put on to book multiple appointments. ID unique to the applied schedule<br /> |schedule.id<br /> |-<br /> |start_date<br /> |date<br /> |DEFAULT NULL<br /> |The start date of the appointment<br /> |<br /> |-<br /> |planned_duration<br /> |int<br /> |DEFAULT NULL<br /> |The time allocated for the appointment, not necessarily the actual duration always in minutes<br /> |<br /> |-<br /> |actual_duration<br /> |int<br /> |DEFAULT NULL<br /> |Time between sent in and left always in minutes<br /> |<br /> |-<br /> |appointment_status_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |The status of the appointment e.g. arrived/sent in/left/DNA<br /> |<br /> |-<br /> |patient_wait<br /> |int<br /> |DEFAULT NULL<br /> |How long the patient waited from being marked as arrived to being sent in<br /> |<br /> |-<br /> |patient_delay<br /> |int<br /> |DEFAULT NULL<br /> |How long the patient was delayed for<br /> |<br /> |-<br /> |date_time_sent_in<br /> |datetime<br /> |DEFAULT NULL<br /> |Date and time the patient was sent into the practitioner<br /> |<br /> |-<br /> |date_time_left<br /> |datetime<br /> |DEFAULT NULL<br /> |Date and time the patient left the practitioner<br /> |<br /> |-<br /> |source_id<br /> |varchar(36)<br /> |DEFAULT NULL<br /> |Unique reference to the source of the appointment<br /> |<br /> |-<br /> |cancelled_date<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the appointment was cancelled<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_appointment_id PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_appointment_organization_id FOREIGN KEY (organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_appointment_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: appointment_status ==<br /> PRIMARY KEY (id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the appointment status<br /> |<br /> |-<br /> |Value<br /> |varchar(50)<br /> |NOT NULL<br /> |The value of the appointment status<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: concept ==<br /> PRIMARY KEY (dbid)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Dbid<br /> |int(11)<br /> |NOT NULL<br /> |Unique Id of the concept<br /> |<br /> |-<br /> |Document<br /> |int(11)<br /> |NOT NULL<br /> |Concept grouping construct, deprecated<br /> |<br /> |-<br /> |Id<br /> |varchar(150)<br /> |NOT NULL<br /> |Unique concept identifier<br /> |<br /> |-<br /> |Draft<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether its draft/autocreated or confirmed as a &quot;proper&quot; concept<br /> |<br /> |-<br /> |Name<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Short name<br /> |<br /> |-<br /> |Description<br /> |varchar(400)<br /> |DEFAULT NULL<br /> |Full name (or term for ontological concepts)<br /> |<br /> |-<br /> |Scheme<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The coding scheme for the code (Read, CTV3, SNOMED etc)<br /> |<br /> |-<br /> |Code<br /> |varchar(40)<br /> |DEFAULT NULL<br /> |The code (non-unique unless coupled with a scheme)<br /> |<br /> |-<br /> |use_count<br /> |bigint(20)<br /> |NOT NULL DEFAULT 0<br /> |Rough indicator of number of occurences of the concept<br /> |<br /> |-<br /> |updated datetime<br /> |datetime<br /> |NOT NULL<br /> |The timestamp of the last update to the concept<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (dbid),<br /> |}<br /> <br /> == Table: concept_map ==<br /> PRIMARY KEY (legacy)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Legacy<br /> |int(11)<br /> |NOT NULL<br /> |the legacy (read 2, ctv3, icd10, opcs4, emis local, etc) concept<br /> |<br /> |-<br /> |Core<br /> |int(11)<br /> |NOT NULL<br /> |the core (snomed, discovery) concept that the legacy concept maps to<br /> |<br /> |-<br /> |Updated<br /> |datetime<br /> |NOT NULL<br /> |Timestamp the map was last updated/added<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (legacy)<br /> |}<br /> <br /> == Table: concept_property_object ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |dbid<br /> |int(11)<br /> |NOT NULL<br /> |Unique Id of the concept<br /> |<br /> |-<br /> |group<br /> |int(11)<br /> |NOT NULL<br /> |Grouping identifier<br /> |<br /> |-<br /> |property<br /> |int(11)<br /> |NOT NULL<br /> |The property concept<br /> |<br /> |-<br /> |value<br /> |int(11)<br /> |NOT NULL<br /> |The value concept for the given concepts property<br /> |<br /> |-<br /> |updated<br /> |datetime<br /> |NOT NULL<br /> |Timestamp the property value was updated/added<br /> |<br /> |}<br /> <br /> == Table: concept_tct ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Source<br /> |int(11)<br /> |DEFAULT NULL<br /> |Source concept<br /> |<br /> |-<br /> |Property<br /> |int(11)<br /> |DEFAULT NULL<br /> |Property concept<br /> |<br /> |-<br /> |Level<br /> |int(11)<br /> |DEFAULT NULL<br /> |The &quot;distance&quot; of the from source (1=parent, 2=grandparent, etc)<br /> |<br /> |-<br /> |Target<br /> |int(11)<br /> |DEFAULT NULL<br /> |The target<br /> |<br /> |-<br /> |Status<br /> |int(11)<br /> |DEFAULT NULL<br /> |Whether the concept is active<br /> |<br /> |-<br /> |created_date<br /> |datetime<br /> |DEFAULT NULL<br /> |When the concept was created<br /> |<br /> |}<br /> <br /> == Table: consent_code ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |STATUS<br /> |varchar(10)<br /> |DEFAULT NULL<br /> |Whether the consent code is active<br /> |<br /> |-<br /> |DESCRIPTION<br /> |varchar(100)<br /> |DEFAULT NULL<br /> |Description of the consent code<br /> |<br /> |-<br /> |CODE<br /> |varchar(20)<br /> |DEFAULT NULL<br /> |The actual consent code<br /> |<br /> |-<br /> |TERM_CODE<br /> |varchar(20)<br /> |DEFAULT NULL<br /> |The clinical term code<br /> |<br /> |-<br /> |TERM<br /> |varchar(100)<br /> |DEFAULT NULL<br /> |The clinical term<br /> |<br /> |}<br /> <br /> == Table: date_precision ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |<br /> |<br /> |-<br /> |Value<br /> |varchar(11)<br /> |NOT NULL<br /> |<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: diagnostic_order ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the diagnostic order<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |<br /> |-<br /> |encounter_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the encounter the observation was recorded at<br /> |<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the diagnostic order was identified by a clinician<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |result_value<br /> |real<br /> |DEFAULT NULL<br /> |The value of the result of the observation<br /> |<br /> |-<br /> |result_value_units<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The units of the result of the observation<br /> |<br /> |-<br /> |result_date<br /> |date<br /> |DEFAULT NULL<br /> |The date of the result<br /> |<br /> |-<br /> |result_text<br /> |text<br /> |DEFAULT NULL<br /> |Any text associated with the result<br /> |<br /> |-<br /> |result_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the result<br /> |<br /> |-<br /> |is_problem<br /> |boolean<br /> |NOT NULL<br /> |Whether the observation is marked as a problem<br /> |<br /> |-<br /> |is_review<br /> |boolean<br /> |NOT NULL<br /> |Whether the observation is a review of an existing problem<br /> |<br /> |-<br /> |problem_end_date<br /> |date<br /> |DEFAULT NULL<br /> |The end date of the problem<br /> |<br /> |-<br /> |parent_observation_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the parent observation in a complex observation eg systolic and diastolic blood pressures will have a parent observation of Blood pressure<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the observation<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the observation<br /> |<br /> |-<br /> |age_at_event<br /> |decimal (5,2)<br /> |DEFAULT NULL<br /> |The age of the patient at the time of the observation<br /> |<br /> |-<br /> |episodicity_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the episodicity of the problem eg First, review, flare<br /> |<br /> |-<br /> |is_primary<br /> |boolean<br /> |DEFAULT NULL<br /> |Whether the diagnostic order is a primary order<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_diagnostic_order_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_diagnostic_order_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_diagnostic_order_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_diagnostic_order_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: encounter ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the encounter<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |<br /> |-<br /> |appointment_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the appointment this encounter took part on<br /> |<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the clinical code is recorded for<br /> |<br /> |-<br /> |<br /> <br /> <br /> date_precision_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the precision of the date of the encounter<br /> |<br /> |-<br /> |episode_of_care_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Is this instance of the code a review of a previous encounter<br /> |<br /> |-<br /> |service_provider_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the service provider organisation<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the type of encounter<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the type of encounter<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age the patient was when this encounter took place<br /> |<br /> |-<br /> |Type<br /> |text<br /> |DEFAULT NULL<br /> |Unused<br /> |<br /> |-<br /> |sub_type<br /> |text<br /> |DEFAULT NULL<br /> |Unused<br /> |<br /> |-<br /> |admission_method<br /> |varchar(40)<br /> |DEFAULT NULL<br /> |The admission method of the encounter<br /> |<br /> |-<br /> |end_date<br /> |date<br /> |DEFAULT NULL<br /> |The end date of the encounter<br /> |<br /> |-<br /> |institution_location_id<br /> |text<br /> |DEFAULT NULL<br /> |Reference to the institution the encounter took place at<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the encounter was recorded<br /> |<br /> |-<br /> |service_provider_organization_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the service provider organisation<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |<br /> <br /> <br /> CONSTRAINT pk_encounter_id PRIMARY KEY (organization_id,person_id,id),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_appointment_id FOREIGN KEY (appointment_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES appointment (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,*/<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_episode_of_care_id FOREIGN KEY (episode_of_care_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES episode_of_care (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_service_provider_organization_id FOREIGN KEY (service_provider_organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: encounter_additional ==<br /> PRIMARY KEY (id, property_id, value_id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |same as the id column on the encounter table<br /> |<br /> |-<br /> |property_id<br /> |bigint<br /> |NOT NULL<br /> |IM reference (i.e. Admission method)<br /> |<br /> |-<br /> |value_id<br /> |bigint<br /> |NOT NULL<br /> |IM reference (i.e. Emergency admission)<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_encounter_additional_id PRIMARY KEY (id, property_id, value_id)<br /> |}<br /> <br /> == Table: encounter_event ==<br /> PRIMARY KEY (organization_id, person_id, id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the encounter event<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The patient this event belongs to<br /> |<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |The person this event belongs to<br /> |<br /> |-<br /> |encounter_id<br /> |bigint<br /> |NOT NULL<br /> |Reference to the parent encounter record<br /> |<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |<br /> |-<br /> |appointment_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the appointment this encounter took part on<br /> |<br /> |-<br /> |clinical_effective_date<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the encounter took place<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the precision of the date of the encounter<br /> |<br /> |-<br /> |episode_of_care_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the episode of care this encounter belongs to<br /> |<br /> |-<br /> |service_provider_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the service provider organisation<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the type of encounter<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the type of encounter<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age of the patient at the time of the encounter<br /> |<br /> |-<br /> |type<br /> |text<br /> |DEFAULT NULL<br /> |Unused<br /> |<br /> |-<br /> |sub_type<br /> |text<br /> |DEFAULT NULL<br /> |Unused<br /> |<br /> |-<br /> |admission_method<br /> |varchar(40)<br /> |DEFAULT NULL<br /> |The admission method of the encounter<br /> |<br /> |-<br /> |end_date<br /> |date<br /> |DEFAULT NULL<br /> |The end date of the encounter<br /> |<br /> |-<br /> |institution_location_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the institution the encounter took place at<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the encounter was recorded<br /> |<br /> |-<br /> |finished<br /> |boolean<br /> |DEFAULT NULL<br /> |Whether the encounter is finished<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_encounter_event_id PRIMARY KEY (organization_id, person_id, id),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_event_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_event_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_event_episode_of_care_id FOREIGN KEY (episode_of_care_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES episode_of_care (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_encounter_event_service_provider_organization_id FOREIGN KEY (service_provider_organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: episode_of_care ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the episode of care<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |registration_type_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the registration type of the patient<br /> |registration.type.id<br /> |-<br /> |registration_status_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the registration status of the patient<br /> |<br /> |-<br /> |date_registered date<br /> |date<br /> |DEFAULT NULL<br /> |The date the registration was started  for this episode of care<br /> |<br /> |-<br /> |date_registered_end date<br /> |date<br /> |DEFAULT NULL<br /> |The date the registration was ended  for this episode of care<br /> |<br /> |-<br /> |usual_gp_practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the usual GP for this episode of care<br /> |Practitioner.id<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_episode_of_care_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_episode_of_care_patient_id_organisation_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_episode_of_care_practitioner_id FOREIGN KEY (usual_gp_practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: ethnicity_lookup ==<br /> PRIMARY KEY(ethnic_code)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |ethnic_code<br /> |char(1)<br /> |NOT NULL<br /> |Ethnic code<br /> |<br /> |-<br /> |ethnic_name<br /> |varchar(100)<br /> |DEFAULT NULL<br /> |Corresponding ethnicity name<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (ethnic_code)<br /> |}<br /> <br /> == Table: event_log ==<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |dt_change<br /> |datetime(3)<br /> |NOT NULL<br /> |date time the change was made to this DB<br /> |<br /> |-<br /> |change_type<br /> |tinyint<br /> |NOT NULL<br /> |type of transaction 0=insert, 1=update, 2=delete<br /> |<br /> |-<br /> |table_id<br /> |tinyint<br /> |NOT NULL<br /> |identifier of the table changed<br /> |<br /> |-<br /> |record_id<br /> |bigint<br /> |NOT NULL<br /> |id of the record changed<br /> |<br /> |}<br /> <br /> == Table: flag ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the flag<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the flag was entered onto the patients record<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |is_active<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the flag is active or not<br /> |<br /> |-<br /> |flag_text<br /> |text<br /> |<br /> |This is a warning set by the publisher regarding he patient<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_flag_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_flag_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: location ==<br /> PRIMARY KEY (pk_location_id PRIMARY KEY id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the location<br /> |<br /> |-<br /> |name<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The name of a location set by the publisher. E.g. ward, clinic, domiciliary<br /> |<br /> |-<br /> |type_code,<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The type of location<br /> |<br /> |-<br /> |type_desc<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Textual description of the type of location eg GP Practice<br /> |<br /> |-<br /> |postcode<br /> |varchar10)<br /> |DEFAULT NULL<br /> |The postcode of the location<br /> |<br /> |-<br /> |managing_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the managing organisation of the location<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_location_id PRIMARY KEY (id)<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_location_organisation_id FOREIGN KEY (managing_organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id)<br /> |-<br /> | colspan=&quot;5&quot; |MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: medication_order ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the medication order<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the encounter the medication order was issued in<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the medication order was issued<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |dose<br /> |varchar(1000)<br /> |DEFAULT NULL<br /> |Textual description of the dose<br /> |<br /> |-<br /> |quantity_value<br /> |real<br /> |DEFAULT NULL<br /> |The value of the medication that was prescribed eg 50<br /> |<br /> |-<br /> |quantity_unit<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The unit of the medication that was prescribed eg tablets<br /> |<br /> |-<br /> |duration_days<br /> |int<br /> |DEFAULT NULL<br /> |How many days the medication is prescribed for<br /> |<br /> |-<br /> |estimated_cost<br /> |real<br /> |DEFAULT NULL<br /> |The estimated cost of the medication<br /> |<br /> |-<br /> |medication_statement_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the medication statement.  A medication statement can have many medication orders<br /> |medication.statement.id<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the medication<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the medication<br /> |<br /> |-<br /> |bnf_reference<br /> |varchar(6)<br /> |DEFAULT NULL<br /> |A reference to the drug in the BNF dictionary<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age the patient was at the time of this event<br /> |<br /> |-<br /> |issue_method<br /> |text<br /> |DEFAULT NULL<br /> |The issue method of the medication eg hand written<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_medication_order_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_order_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_order_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_order_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: medication_statement ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the medication<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the encounter this medication was recorded in<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the medication was clinical relevant<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |is_active<br /> |tinyint(4)<br /> |DEFAULT NULL<br /> |Whether the medication is active or not<br /> |<br /> |-<br /> |cancellation_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the medication was cancelled<br /> |<br /> |-<br /> |dose<br /> |varchar(1000)<br /> |DEFAULT NULL<br /> |Texual description of the dose of the medication<br /> |<br /> |-<br /> |quantity_value<br /> |double<br /> |DEFAULT NULL<br /> |The value of the medication that was prescribed eg 50<br /> |<br /> |-<br /> |quantity_unit<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The unit of the medication that was prescribed eg tablets<br /> |<br /> |-<br /> |authorisation_type_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the authorisation type<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the medication<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the medication<br /> |<br /> |-<br /> |bnf_reference<br /> |varchar(6)<br /> |DEFAULT NULL<br /> |A reference to the drug in the BNF dictionary<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age the patient was at the time of this event<br /> |<br /> |-<br /> |Issue_method<br /> |text<br /> |DEFAULT NULL<br /> |The issue method of the medication eg hand written<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_medication_statement_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_statement_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_statement_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_medication_statement_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: observation ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the observation<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the encounter the observation was recorded at<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the observation was identified by a clinician<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |result_value<br /> |double<br /> |DEFAULT NULL<br /> |The value of the result of the observation<br /> |<br /> |-<br /> |result_value_units<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The units of the result of the observation<br /> |<br /> |-<br /> |result_date<br /> |date<br /> |DEFAULT NULL<br /> |The date of the result<br /> |<br /> |-<br /> |result_text<br /> |text<br /> |<br /> |Any text associated with the result<br /> |<br /> |-<br /> |result_concept_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the result<br /> |<br /> |-<br /> |is_problem<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the observation is marked as a problem<br /> |<br /> |-<br /> |is_review<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the observation is a review of an existing problem<br /> |<br /> |-<br /> |problem_end_date<br /> |date<br /> |DEFAULT NULL<br /> |The end date of the problem<br /> |<br /> |-<br /> |parent_observation_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the parent observation in a complex observation eg systolic and diastolic blood pressures will have a parent observation of Blood pressure<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the observation<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the observation<br /> |<br /> |-<br /> |age_at_event<br /> |decimal (5,2)<br /> |DEFAULT NULL<br /> |The age of the patient at the time of the observation<br /> |<br /> |-<br /> |episodicity_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the episodicity of the problem eg First, review, flare<br /> |<br /> |-<br /> |is_primary<br /> |boolean<br /> |DEFAULT NULL<br /> |Whether the observation is a primary observation<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the observation was recorded in the system<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_observation_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_observation_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_observation_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_observation_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: organization ==<br /> PRIMARY KEY (pk_organization_id PRIMARY KEY (id))<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the organisation<br /> |<br /> |-<br /> |ods_code<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |ODS Code of the organisation<br /> |<br /> |-<br /> |Name<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Name of the organisation<br /> |<br /> |-<br /> |type_code<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The type of organisation<br /> |<br /> |-<br /> |type_desc<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Textual description of the type of organisation eg GP Practice<br /> |<br /> |-<br /> |Postcode<br /> |varchar(10)<br /> |DEFAULT NULL<br /> |The postcode of the organisation<br /> |<br /> |-<br /> |parent_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |The id of the parent organisation<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |PRIMARY KEY pk_organization_id PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: patient ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the patient<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |person_id<br /> |bigint<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |title<br /> |varchar(50)<br /> |<br /> |The title of the patient<br /> |<br /> |-<br /> |first_names<br /> |varchar(255)<br /> |<br /> |The first names of the patient<br /> |<br /> |-<br /> |last_name<br /> |varchar(255)<br /> |<br /> |The last name of the patient<br /> |<br /> |-<br /> |gender_concept_id<br /> |int<br /> |<br /> |Reference to the gender of the patient<br /> |patient.gender.id<br /> |-<br /> |nhs_number<br /> |varchar(255)<br /> |<br /> |The NHS number of the patient<br /> |<br /> |-<br /> |date_of_birth<br /> |date<br /> |<br /> |The date of birth of the patient<br /> |<br /> |-<br /> |date_of_death<br /> |date<br /> |<br /> |The date of death of the patient<br /> |<br /> |-<br /> |current_address_id<br /> |bigint<br /> |<br /> |Reference to the current address of the patient<br /> |<br /> |-<br /> |ethnic_code_concept_id<br /> |int<br /> |<br /> |Reference to the ethnicity of the patient<br /> |<br /> |-<br /> |registered_practice_organization_id<br /> |bigint<br /> |<br /> |Reference to the organisation the patient is registered at<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_patient_id_organization_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_patient_organization_id FOREIGN KEY (organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |}<br /> <br /> == Table: patient_address ==<br /> PRIMARY KEY (organization_id,id,patient_id,person_id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the address<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organisation.id<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |address_line_1<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The first line of the address<br /> |<br /> |-<br /> |address_line_2<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The second line of the address<br /> |<br /> |-<br /> |address_line_3<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The third line of the address<br /> |<br /> |-<br /> |address_line_4<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The fourth line of the address<br /> |<br /> |-<br /> |city<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The city<br /> |<br /> |-<br /> |postcode<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The postcode<br /> |<br /> |-<br /> |use_concept_id<br /> |int<br /> |NOT NULL<br /> |use of address (e.g. home, temporary)<br /> |<br /> |-<br /> |start_date<br /> |Date<br /> |NOT NULL<br /> |The start date of this address being relevant<br /> |<br /> |-<br /> |end_date<br /> |Date<br /> |DEFAULT NULL<br /> |The end date of this address being relevant<br /> |<br /> |-<br /> |lsoa_2001_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |A reference to the LSOA_2001 code<br /> |<br /> |-<br /> |lsoa_2011_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |A reference to the LSOA_2011 code<br /> |<br /> |-<br /> |msoa_2001_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |A reference to the MSOA_2001 code<br /> |<br /> |-<br /> |msoa_2011_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |A reference to the MSOA_2011 code<br /> |<br /> |-<br /> |ward_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |The ward the address belongs to<br /> |<br /> |-<br /> |local_authority_code<br /> |varchar(9)<br /> |DEFAULT NULL<br /> |The local authority the address belongs to<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_organization_id_id_patient_id_person_id<br /> |-<br /> | colspan=&quot;5&quot; |PRIMARY KEY (`organization_id`,`id`,`patient_id`,`person_id`)<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_patient_address_patient_id_organization_id<br /> |-<br /> | colspan=&quot;5&quot; |FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |COMMENT 'stores address details for patients'<br /> |}<br /> <br /> == Table: patient_address_match ==<br /> PRIMARY KEY(id, uprn)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |bigint(20)<br /> |NOT NULL<br /> |Reference to the patient_address table<br /> |<br /> |-<br /> |Uprn<br /> |varchar(255)<br /> |NOT NULL<br /> |The Unique Propery Reference Number of the address<br /> |<br /> |-<br /> |Status<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Whether the UPRN is active<br /> |<br /> |-<br /> |Classification<br /> |varchar(45)<br /> |DEFAULT NULL<br /> |Building type eg flat, pub, house etc<br /> |<br /> |-<br /> |Latitude<br /> |double<br /> |DEFAULT NULL<br /> |The latitude of the UPRN<br /> |<br /> |-<br /> |Longitude<br /> |double<br /> |DEFAULT NULL<br /> |The longitude of the UPRN<br /> |<br /> |-<br /> |Xcoordinate<br /> |double<br /> |DEFAULT NULL<br /> |The x coordinate of the UPRN<br /> |<br /> |-<br /> |Ycoordinate<br /> |double<br /> |DEFAULT NULL<br /> |The y coordinate of the UPRN<br /> |<br /> |-<br /> |Qualifier<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |How the match is determined eg equivalent match, near match etc<br /> |<br /> |-<br /> |Algorithm<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Which algorithm was used to match the address to the UPRN<br /> |<br /> |-<br /> |match_date<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the match was made<br /> |<br /> |-<br /> |abp_address_number<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The number value of the address in the ABP dictionary<br /> |<br /> |-<br /> |abp_address_street<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The street value of the address in the ABP dictionary<br /> |<br /> |-<br /> |abp_address_locality<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The locality value of the address in the ABP dictionary<br /> |<br /> |-<br /> |abp_address_town<br /> |varchar(10)<br /> |DEFAULT NULL<br /> |The town value of the address in the ABP dictionary<br /> |<br /> |-<br /> |abp_address_postcode<br /> |varchar(10)<br /> |DEFAULT NULL<br /> |The postcode value of the address in the ABP dictionary<br /> |<br /> |-<br /> |abp_address_organization<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The organization value of the address in the ABP dictionary<br /> |<br /> |-<br /> |match_pattern_postcode<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The qualifier used to match the postcode<br /> |<br /> |-<br /> |match_pattern_street<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The qualifier used to match the street<br /> |<br /> |-<br /> |match_pattern_number<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The qualifier used to match the number<br /> |<br /> |-<br /> |match_pattern_building<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The qualifier used to match the building<br /> |<br /> |-<br /> |match_pattern_flat<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The qualifier used to match the flat<br /> |<br /> |-<br /> |algorithm_version<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |What version of the algorithm was used to make the match<br /> |<br /> |-<br /> |Epoc<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The version of the ABP files the addresses were matched against<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id,uprn)<br /> |}<br /> <br /> == Table: patient_contact ==<br /> PRIMARY KEY (organization_id,id,patient_id,person_id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the patient contact<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |use_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |use of contact (e.g. mobile, home,work<br /> |<br /> |-<br /> |type_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |type of contact (e.g. phone, email)<br /> |<br /> |-<br /> |start_date date<br /> |date<br /> |DEFAULT NULL<br /> |The start date of the contact being valid<br /> |<br /> |-<br /> |end_date date<br /> |date<br /> |DEFAULT NULL<br /> |The end date of the contact being valid<br /> |<br /> |-<br /> |value<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The value of the contact information eg phone number, email address<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_organization_id_id_patient_id_person_id PRIMARY KEY (`organization_id`,`id`,`patient_id`,`person_id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_patient_contact_patient_id_organisation_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |COMMENT 'stores contact details (e.g. phone) for patients'<br /> |}<br /> <br /> == Table: patient_gender ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the gender lookup<br /> |<br /> |-<br /> |Value<br /> |varchar(10)<br /> |NOT NULL<br /> |Value of the gender lookup<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: patient_pseudo_id ==<br /> PRIMARY KEY(organization_id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the patient pseudo id<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Reference to the patient this registration status history belongs to<br /> |<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Reference to the person this registration status history belongs to<br /> |<br /> |-<br /> |salt_name<br /> |varchar(50)<br /> |NOT NULL<br /> |The name of the salt used to create the pseudo id<br /> |<br /> |-<br /> |Skid<br /> |varchar(255)<br /> |NOT NULL<br /> |&quot;Secure Key IDentifier&quot; - the pseudonymised ID generated for this patient using the salt specified in the salt_name column. Typically generated from patient NHS number, but is configurable on a case by case basis (e.g. may include date of birth)<br /> |<br /> |-<br /> |is_nhs_number_valid<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the nhs number is valid<br /> |<br /> |-<br /> |is_nhs_number_verified_by_publisher<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the nhs number has been verified by the publisher<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (organization_id)<br /> |}<br /> <br /> == Table: patient_uprn ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organisation.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |Uprn<br /> |bigint<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |qualifier<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |algorithm<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |match<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |no_address<br /> |tinyint(1)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |invalid_address<br /> |tinyint(1)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |missing_postcode<br /> |tinyint(1)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> |invalid_postcode<br /> |tinyint(1)<br /> |DEFAULT NULL<br /> |<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_patient_id_organization_id PRIMARY KEY (`organization_id`,`person_id`,`patient_id`),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_patient_uprn_patient_id_organisation_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: person ==<br /> PRIMARY KEY (id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the person<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |title<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The title of the person<br /> |<br /> |-<br /> |first_names<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The first names of the person<br /> |<br /> |-<br /> |last_name<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The last name of the person<br /> |<br /> |-<br /> |gender_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the gender of the person<br /> |<br /> |-<br /> |nhs_number<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The NHS number of the person<br /> |<br /> |-<br /> |date_of_birth date,<br /> |date<br /> |DEFAULT NULL<br /> |The date of birth of the person<br /> |<br /> |-<br /> |date_of_death date,<br /> |date<br /> |DEFAULT NULL<br /> |The date of death of the person<br /> |<br /> |-<br /> |current_address_id,<br /> |bigint<br /> |NOT NULL<br /> |Reference to the current address of the person<br /> |<br /> |-<br /> |ethnic_code_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the ethnicity of the person<br /> |<br /> |-<br /> |registered_practice_organization_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the organisation the person is registered at<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_person_id PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: practitioner ==<br /> PRIMARY KEY (id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the practitioner<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organisation.id<br /> |-<br /> |name<br /> |varchar(1024)<br /> |DEFAULT NULL<br /> |Name of the practitioner<br /> |<br /> |-<br /> |role_code<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The code representing the role of the practitioner<br /> |<br /> |-<br /> |role_desc<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Textual description of the role of the practitioner eg General Medical Practitioner<br /> |<br /> |-<br /> |gmc_code<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The GMC code of the practitioner<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_practitioner_id PRIMARY KEY (id),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_practitioner_organisation_id FOREIGN KEY (organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: procedure_request ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the procedure<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the encounter the procedure was administered at<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the procedure was administered by a clinician<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |status_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the status of the procedure<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the procedure<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the procedure<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age of the patient at the time of the procedure<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the procedure was recorded in the source system<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_procedure_request_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |/*got an Emis procedure request referring to a confidential encounter, so can't enforce this<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_procedure_request_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,*/<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_procedure_request_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_procedure_request_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: procedure_request_status ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the procedure request status lookup<br /> |<br /> |-<br /> |Value<br /> |varchar(50)<br /> |NOT NULL<br /> |The value of the procedure request status lookup<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: pseudo_id ==<br /> PRIMARY KEY (patient_id, salt_key_name)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the pseudo Id<br /> |<br /> |-<br /> |patient_id<br /> |bigint<br /> |NOT NULL<br /> |Reference to the patient the pseudo Id belongs to<br /> |<br /> |-<br /> |salt_key_name<br /> |varchar(50)<br /> |NOT NULL<br /> |The name of the salt key used to create the pseudo id<br /> |<br /> |-<br /> |pseudo_id<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The pseudo id<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_pseudo_id PRIMARY KEY (patient_id, salt_key_name)<br /> |}<br /> <br /> == Table: referral_request ==<br /> PRIMARY KEY (organization_id,person_id,id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the referral<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |The organisations record for this person’s registration. Patients may have multiple records across clinical systems and may have registered at an organisation multiple times<br /> |patient.id<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique individual across all organisations<br /> |person.id<br /> |-<br /> |encounter_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the encounter the referral was made in<br /> |encounter.id<br /> |-<br /> |practitioner_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |The clinician the activity is recorded against<br /> |practitioner.id<br /> |-<br /> |clinical_effective_date<br /> |date<br /> |DEFAULT NULL<br /> |The date the referral was made<br /> |<br /> |-<br /> |date_precision_concept_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Identifies the precision of the clinical effectiveness date to either year (1) month (2) day (5) minute (12) second (13) millisecond (14)<br /> |<br /> |-<br /> |requester_organization_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the organisation that made the refereral request<br /> |<br /> |-<br /> |recipient_organization_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the organization receiving the referral<br /> |<br /> |-<br /> |referral_request_priority_concept_id<br /> |smallint(6)<br /> |DEFAULT NULL<br /> |Reference to the priority of the referral<br /> |referral.request.priority<br /> |-<br /> |referral_request_type_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the type of referral request<br /> |referral.request.type<br /> |-<br /> |Mode<br /> |varchar(50)<br /> |DEFAULT NULL<br /> |The mode of the referral<br /> |<br /> |-<br /> |outgoing_referral<br /> |boolean<br /> |DEFAULT NULL<br /> |Whether this is an outgoing referral<br /> |<br /> |-<br /> |is_review<br /> |boolean<br /> |DEFAULT NULL<br /> |Whether this referral is a review<br /> |<br /> |-<br /> |core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the referral<br /> |<br /> |-<br /> |non_core_concept_id<br /> |int<br /> |DEFAULT NULL<br /> |Reference to the clinical coding of the referral<br /> |<br /> |-<br /> |age_at_event<br /> |decimal(5,2)<br /> |DEFAULT NULL<br /> |The age of the patient at the time of the referral<br /> |<br /> |-<br /> |date_recorded<br /> |datetime<br /> |DEFAULT NULL<br /> |The date the referral request was added to the source system<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_referral_request_id PRIMARY KEY (`organization_id`,`person_id`,`id`),<br /> |-<br /> | colspan=&quot;5&quot; |/*got an Emis referral request referring to a confidential encounter, so can't enforce this<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_referral_request_encounter_id FOREIGN KEY (encounter_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES encounter (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,*/<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_referral_request_patient_id_organization_id FOREIGN KEY (patient_id, organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES patient (id, organization_id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_referral_request_practitioner_id FOREIGN KEY (practitioner_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES practitioner (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_referral_request_recipient_organization_id FOREIGN KEY (recipient_organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION,<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_referral_request_requester_organization_id FOREIGN KEY (requester_organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> == Table: referral_request_priority ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the referral request priority lookup<br /> |<br /> |-<br /> |Value<br /> |varchar(50)<br /> |NOT NULL<br /> |The value of the referral request priority lookup<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: referral_request_type ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the referral request type<br /> |<br /> |-<br /> |Value<br /> |varchar(50)<br /> |NOT NULL<br /> |The value of the referral request lookup<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: registration_status ==<br /> PRIMARY KEY(id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |smallint(6)<br /> |NOT NULL<br /> |Unique Id of the registration status<br /> |<br /> |-<br /> |Code<br /> |varchar(10)<br /> |NOT NULL<br /> |The registration status code<br /> |<br /> |-<br /> |Description<br /> |varchar(50)<br /> |NOT NULL<br /> |The description of the registration status<br /> |<br /> |-<br /> |is_active<br /> |tinyint(1)<br /> |NOT NULL<br /> |Whether the registration status is active<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (id)<br /> |}<br /> <br /> == Table: registration_status_history ==<br /> PRIMARY KEY(organization_id,id,patient_id,person_id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |Id<br /> |bigint(20)<br /> |NOT NULL<br /> |Unique Id of the registration status history<br /> |<br /> |-<br /> |organization_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |<br /> |-<br /> |patient_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Reference to the patient this registration status history belongs to<br /> |<br /> |-<br /> |person_id<br /> |bigint(20)<br /> |NOT NULL<br /> |Reference to the person this registration status history belongs to<br /> |<br /> |-<br /> |episode_of_care_id<br /> |bigint(20)<br /> |DEFAULT NULL<br /> |Reference to the episode of care this status history belongs to<br /> |<br /> |-<br /> |registration_status_concept_id<br /> |int(11)<br /> |DEFAULT NULL<br /> |Reference to the registration status<br /> |<br /> |-<br /> |start_date<br /> |datetime<br /> |DEFAULT NULL<br /> |The start date for the period this registration status history was valid<br /> |<br /> |-<br /> |end_date<br /> |datetime<br /> |DEFAULT NULL<br /> |The end date for the period this registration status history was valid<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT PRIMARY KEY (organization_id,id,patient_id,person_id)<br /> |}<br /> == Table: schedule ==<br /> PRIMARY KEY (organization_id, id)<br /> {| class=&quot;wikitable sortable mw-collapsible mw-collapsed&quot;<br /> |'''Column name'''<br /> |'''Data type'''<br /> |'''Constraint'''<br /> |'''Comments'''<br /> |'''References'''<br /> |-<br /> |id<br /> |bigint<br /> |NOT NULL<br /> |Unique Id of the schedule<br /> |<br /> |-<br /> |organization_id<br /> |bigint<br /> |NOT NULL<br /> |Owning organisation (i.e. publisher)<br /> |organization.id<br /> |-<br /> |practitioner_id<br /> |bigint<br /> |DEFAULT NULL<br /> |Reference to the practitioner who owns the schedule<br /> |practitioner.id<br /> |-<br /> |start_date<br /> |date<br /> |DEFAULT NULL<br /> |The start date of the schedule<br /> |<br /> |-<br /> |type<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |The type of schedule eg Timed Appointments<br /> |<br /> |-<br /> |Location<br /> |varchar(255)<br /> |DEFAULT NULL<br /> |Textual description of the location the schedule was held at<br /> |location.id<br /> |-<br /> |Name<br /> |varchar(150)<br /> |DEFAULT NULL<br /> |The name of the schedule<br /> |<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT pk_schedule_id PRIMARY KEY (organization_id, id),<br /> |-<br /> | colspan=&quot;5&quot; |CONSTRAINT fk_schedule_organization_id FOREIGN KEY (organization_id)<br /> |-<br /> | colspan=&quot;5&quot; |REFERENCES organization (id) MATCH SIMPLE<br /> |-<br /> | colspan=&quot;5&quot; |ON UPDATE NO ACTION ON DELETE NO ACTION<br /> |}<br /> <br /> &lt;br /&gt;<br /> __FORCETOC__<br /> __INDEX__<br /> __NONEWSECTIONLINK__</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Remote_Subscriber_Database_Familiarisation&diff=2177 2020-08-04T13:13:55Z

<p>Jay: </p> <hr /> <div>== Overview ==<br /> The purpose of this article is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system.<br /> <br /> It includes testing guidance, hints and tips from LHS developers who have experience with the system and guidance on how to use tools share knowledge and record issues.<br /> <br /> == End User Acceptance Testing ==<br /> [[Remote Subscriber Database Testing and Assurance|Follow this link]] to go to the article that outlines the strategy to be used for end user testing and assurance of data published to a remote data distribution service.  <br /> <br /> == Remote Subscriber Database User Forum ==<br /> All organisations accessing DDS on remote subscriber database are invited to a user forum to share knowledge and learning from their experience using the product. The forum communicates using our Jira board and a regular conference call which will be attended by a developer who is experienced at creating SQL queries on data held in the DDS from LHS.<br /> <br /> [https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=43 Follow this link] to access our Extract &amp; Queries Forum.<br /> <br /> [[Extract &amp; Queries Forum and Issue Logging|Follow this link]] for our user guide to our Extract &amp; Queries Forum.<br /> <br /> == Data Mapping ==<br /> The links below take you to our schemas which list the contents and references for each table in the Compass databases.<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 1)|Compass 1 Schema]]<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 2)|Compass 2 Schema]]<br /> <br /> This is an example of a schema table.<br /> [[File:Schema table example.jpg|none|thumb|Schema table example]]<br /> <br /> == Remote Discovery Database SQL Guides ==<br /> The articles below were written by our developers, who are experts with the DDS, to introduce you to how they create cohorts, build datasets and call store procedures.<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 1)|Compass 1 SQL Guide]]<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 2)|Compass 2 SQL Guide]]</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Remote_Subscriber_Database_Familiarisation&diff=2176 2020-08-04T13:12:14Z

<p>Jay: </p> <hr /> <div>== Overview ==<br /> The purpose of this article is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system.<br /> <br /> It includes testing guidance, hints and tips from LHS developers who have experience with the system and guidance on how to use tools share knowledge and record issues.<br /> <br /> == End User Acceptance Testing ==<br /> [[Remote Subscriber Database Testing and Assurance|Follow this link]] to go to the article that outlines the strategy to be used for end user testing and assurance of data published to a remote data distribution service.  <br /> <br /> == Remote Subscriber Database User Forum ==<br /> All organisations accessing DDS on remote subscriber database are invited to a user forum to share knowledge and learning from their experience using the product. The forum communicates using our Jira board and a regular conference call which will be attended by a developer who is experienced at creating SQL queries on data held in the DDS from LHS.<br /> <br /> [https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=43 Follow this link] to access our Extract &amp; Queries Forum.<br /> <br /> [[Extract &amp; Queries Forum and Issue Logging|Follow this link]] for our user guide to our Extract &amp; Queries Forum.<br /> <br /> == Data Mapping ==<br /> The links below take you to our schemas for the Compass 1 and Compass 2 databases respectively.<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 1)|Compass 1 Schema]]<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 2)|Compass 2 Schema]]<br /> <br /> This is an example of a schema table.<br /> [[File:Schema table example.jpg|none|thumb|Schema table example]]<br /> <br /> == Remote Discovery Database SQL Guide ==<br /> The articles below were written by our developers, who are experts with the DDS, to introduce you to how they create cohorts, build datasets and call store procedures.<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 1)|Compass 1 SQL Guide]]<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 2)|Compass 2 SQL Guide]]</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Remote_Subscriber_Database_Familiarisation&diff=2175 2020-08-04T12:59:43Z

<p>Jay: </p> <hr /> <div>== Overview ==<br /> The purpose of this article is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system.<br /> <br /> It includes testing guidance, hints and tips from LHS developers who have experience with the system and guidance on how to use tools share knowledge and record issues.<br /> <br /> == End User Acceptance Testing ==<br /> [[Remote Subscriber Database Testing and Assurance|Follow this link]] to go to the article that outlines the strategy to be used for end user testing and assurance of data published to a remote data distribution service.  <br /> <br /> == Remote Subscriber Database User Forum ==<br /> All organisations accessing DDS on remote subscriber database are invited to a user forum to share knowledge and learning from their experience using the product. The forum communicates using our Jira board and a regular conference call which will be attended by a developer who is experienced at creating SQL queries on data held in the DDS from LHS.<br /> <br /> [https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=43 Follow this link] to access our Extract &amp; Queries Forum.<br /> <br /> [[Extract &amp; Queries Forum and Issue Logging|Follow this link]] for our user guide to our Extract &amp; Queries Forum.<br /> <br /> == Data Mapping ==<br /> The links below take you to our schemas for the Compass 1 and Compass 2 databases respectively.<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 1)|Compass 1 Schema]]<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 2)|Compass 2 Schema]]<br /> <br /> This is an example of a table from that document.<br /> [[File:Schema table example.jpg|none|thumb|Schema table example]]<br /> <br /> == Remote Discovery Database SQL Guide ==<br /> The articles below were written by our developers, who are experts with the DDS, to introduce you to how they create cohorts, build datasets and call store procedures.<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 1)|Compass 1 SQL Guide]]<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 2)|Compass 2 SQL Guide]]</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Remote_Subscriber_Database_Familiarisation&diff=2174 2020-08-04T12:52:27Z

<p>Jay: </p> <hr /> <div>== Overview ==<br /> The purpose of this page is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system.<br /> <br /> It includes testing guidance, hints and tips from LHS developers who have experience with the system and guidance on how to use tools share knowledge and record issues.<br /> <br /> == End User Acceptance Testing ==<br /> [[Remote Subscriber Database Testing and Assurance|Follow this link]] to go to the page that outlines the strategy to be used for end user testing and assurance of data published to a remote data distribution service.  <br /> <br /> == Remote Subscriber Database User Forum ==<br /> All organisations accessing DDS on remote subscriber database are invited to a user forum to share knowledge and learning from their experience using the product. The forum communicates using our Jira board and a regular conference call which will be attended by a developer who is experienced at creating SQL queries on data held in the DDS from LHS.<br /> <br /> [https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=43 Follow this link] to access our Extract &amp; Queries Forum.<br /> <br /> [[Extract &amp; Queries Forum and Issue Logging|Follow this link]] for our user guide to our Extract &amp; Queries Forum.<br /> <br /> == Data Mapping ==<br /> The links below take you to our schemas for the Compass 1 and Compass 2 databases respectively.<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 1)|Compass 1 Schema]]<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 2)|Compass 2 Schema]]<br /> <br /> This is an example of a table from that document.<br /> [[File:Schema table example.jpg|none|thumb|Schema table example]]<br /> <br /> == Remote Discovery Database SQL Guide ==<br /> The pages below were written by our developers, who are experts with the DDS, to introduce you to how they create cohorts, build datasets and call store procedures.<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 1)|Compass 1 SQL Guide]]<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 2)|Compass 2 SQL Guide]]</div>

Jay https://wiki.voror.co.uk/index.php?title=Discovery_Remote_Subscriber_Database_Familiarisation&diff=2173 2020-08-04T12:51:55Z

<p>Jay: Created page with &quot;= Overview = The purpose of this page is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system. It includes...&quot;</p> <hr /> <div>= Overview =<br /> The purpose of this page is to assist users of the DDS Remote Subscriber Database in testing understanding and maximising the benefits of the system.<br /> <br /> It includes testing guidance, hints and tips from LHS developers who have experience with the system and guidance on how to use tools share knowledge and record issues.<br /> <br /> == End User Acceptance Testing ==<br /> [[Remote Subscriber Database Testing and Assurance|Follow this link]] to go to the page that outlines the strategy to be used for end user testing and assurance of data published to a remote data distribution service.  <br /> <br /> = Remote Subscriber Database User Forum =<br /> All organisations accessing DDS on remote subscriber database are invited to a user forum to share knowledge and learning from their experience using the product. The forum communicates using our Jira board and a regular conference call which will be attended by a developer who is experienced at creating SQL queries on data held in the DDS from LHS.<br /> <br /> [https://endeavourhealth.atlassian.net/secure/RapidBoard.jspa?rapidView=43 Follow this link] to access our Extract &amp; Queries Forum.<br /> <br /> [[Extract &amp; Queries Forum and Issue Logging|Follow this link]] for our user guide to our Extract &amp; Queries Forum.<br /> <br /> = Data Mapping =<br /> The links below take you to our schemas for the Compass 1 and Compass 2 databases respectively.<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 1)|Compass 1 Schema]]<br /> <br /> [[Remote Subscriber Database (RSD) Schema (Compass 2)|Compass 2 Schema]]<br /> <br /> This is an example of a table from that document.<br /> [[File:Schema table example.jpg|none|thumb|Schema table example]]<br /> <br /> = Remote Discovery Database SQL Guide =<br /> The pages below were written by our developers, who are experts with the DDS, to introduce you to how they create cohorts, build datasets and call store procedures.<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 1)|Compass 1 SQL Guide]]<br /> <br /> [[Remote Subscriber Database (RSD) SQL guide (Compass 2)|Compass 2 SQL Guide]]</div>

Jay https://wiki.voror.co.uk/index.php?title=File:Schema_table_example.jpg&diff=2172 2020-08-04T12:49:01Z

<p>Jay: </p> <hr /> <div>Schema table example</div>

Jay https://wiki.voror.co.uk/index.php?title=Extract_%26_Queries_Forum_and_Issue_Logging&diff=2171 2020-08-04T12:34:16Z

<p>Jay: </p> <hr /> <div>The purpose of the Extract &amp; Queries Forum and Issue Logging board is to capture discussion points, hints and tips and to be a single source of information in relation to issues that affect the running of extracts and queries.<br /> <br /> Where an issue is specific to a project (it must be entered on the relevant Jira board) if it then becomes apparent that it affects other projects (current or future) it should be linked to this board.<br /> <br /> LHS are committed to this and will check the board daily for any new tickets raised that need to be triaged and to also update ongoing tickets. We ask that you raise tickets on the board for ideas, questions that may be answered by other users, hints &amp; tips for LHS and other users and to alert the LHS team of bugs affecting the overall system.<br /> <br /> This document will outline what is required from the forum users and how we will work collaboratively. In order for this process to work, anyone who has an action or question assigned to them on the board needs to respond promptly. If a ticket is raised that could affect other projects, this will be dealt with as a priority.<br /> <br /> == Issue logging ==<br /> <br /> === How to raise a ticket ===<br /> In order to raise a ticket, you need to log into the Jira board. Once logged in:<br /> <br /> 1. Click the ‘+’ sign in the left menu<br /> <br /> 2. Complete the relevant fields in the new ticket screen<br /> <br /> 3. Save<br /> <br /> Note: This will raise a ticket and give it a Hints &amp; Tips status. If this ticket is not for this category, it can be dragged and dropped into the relevant one.<br /> <br /> === Hints &amp; Tips/Discussion Points ===<br /> Tickets raised in this category could be pieces of knowledge that would be beneficial for others to know, or it could be a generic question on the data that is not specific to an existing project.<br /> <br /> New Issues/Progressing Issues/Resolved Issues<br /> <br /> Issues are only to be raised on the board if they are not specific to an existing project. If you are working on a project and come across an issue that could affect more than just your project, a new ticket needs raising on the board and linking to your project specific ticket.<br /> <br /> When a new ticket is raised, it will follow the process as laid out below.<br /> [[File:EQFIL column headings.jpg|none|thumb|EQFIL column headings]]<br /> <br /> <br /> Issue tickets are only to be raised with a New Issue status, where it will then be triaged and allocated to the relevant person. LHS will check the board daily for any new tickets and allocate these out as necessary. Once allocated, the ticket will move to Progressing Issue. Tickets can only be moved to a Resolved Issue status with the approval of the original reporter.<br /> <br /> If this issue has already been raised and you want to add more information, this can be done by commenting on the original ticket.<br /> <br /> === Linking a ticket ===<br /> Linking a ticket from one Jira board to the other, or within the same Jira board can only be done with a ticket that has already been logged. You can’t do this when first creating a ticket.<br /> <br /> To link two or more tickets together you need to:<br /> <br /> 1. Open the ticket you are wanting to link to/from<br /> <br /> 2. Click Link issue<br /> <br /> 3. Select why the issue is being linked (first drop down field)<br /> <br /> 4. In the search for issues field, start to type in either;<br /> <br /> a. Ticket ID, or<br /> <br /> b. Ticket name<br /> <br /> 5. Click the relevant ticket<br /> <br /> 6. Save<br /> [[File:How to link an issue.jpg|thumb|How to link an issue|alt=|none]]<br /> === Action a ticket ===<br /> When a ticket is assigned, the assignee will receive an email alert from Jira. The ticket needs to be picked up within one working day and the responsibility for actioning and progressing the ticket sits with the assignee until the ticket is complete.<br /> <br /> If there is an action for someone other than the current assignee, that person needs tagging into the comments (using the @ symbol before their name) and the ticket also needs assigning to them. Once that action is complete, it needs assigning back to the original assignee.<br /> <br /> Once the ticket is resolved, it needs assigning to the reporter who will then change the ticket status if they are satisfied with the outcome.<br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=Extract_%26_Queries_Forum_and_Issue_Logging&diff=2170 2020-08-04T12:33:38Z

<p>Jay: Created page with &quot;The purpose of the Extract &amp; Queries Forum and Issue Logging board is to capture discussion points, hints and tips and to be a single source of information in relation to issu...&quot;</p> <hr /> <div>The purpose of the Extract &amp; Queries Forum and Issue Logging board is to capture discussion points, hints and tips and to be a single source of information in relation to issues that affect the running of extracts and queries.<br /> <br /> Where an issue is specific to a project (it must be entered on the relevant Jira board) if it then becomes apparent that it affects other projects (current or future) it should be linked to this board.<br /> <br /> LHS are committed to this and will check the board daily for any new tickets raised that need to be triaged and to also update ongoing tickets. We ask that you raise tickets on the board for ideas, questions that may be answered by other users, hints &amp; tips for LHS and other users and to alert the LHS team of bugs affecting the overall system.<br /> <br /> This document will outline what is required from the forum users and how we will work collaboratively. In order for this process to work, anyone who has an action or question assigned to them on the board needs to respond promptly. If a ticket is raised that could affect other projects, this will be dealt with as a priority.<br /> <br /> == Issue logging ==<br /> <br /> === How to raise a ticket ===<br /> In order to raise a ticket, you need to log into the Jira board. Once logged in:<br /> <br /> 1. Click the ‘+’ sign in the left menu<br /> <br /> 2. Complete the relevant fields in the new ticket screen<br /> <br /> 3. Save<br /> <br /> Note: This will raise a ticket and give it a Hints &amp; Tips status. If this ticket is not for this category, it can be dragged and dropped into the relevant one.<br /> <br /> === Hints &amp; Tips/Discussion Points ===<br /> Tickets raised in this category could be pieces of knowledge that would be beneficial for others to know, or it could be a generic question on the data that is not specific to an existing project.<br /> <br /> New Issues/Progressing Issues/Resolved Issues<br /> <br /> Issues are only to be raised on the board if they are not specific to an existing project. If you are working on a project and come across an issue that could affect more than just your project, a new ticket needs raising on the board and linking to your project specific ticket.<br /> <br /> When a new ticket is raised, it will follow the process as laid out below.<br /> [[File:EQFIL column headings.jpg|none|thumb|EQFIL column headings]]<br /> <br /> <br /> Issue tickets are only to be raised with a New Issue status, where it will then be triaged and allocated to the relevant person. LHS will check the board daily for any new tickets and allocate these out as necessary. Once allocated, the ticket will move to Progressing Issue. Tickets can only be moved to a Resolved Issue status with the approval of the original reporter.<br /> <br /> If this issue has already been raised and you want to add more information, this can be done by commenting on the original ticket.<br /> <br /> === Linking a ticket ===<br /> Linking a ticket from one Jira board to the other, or within the same Jira board can only be done with a ticket that has already been logged. You can’t do this when first creating a ticket.<br /> <br /> To link two or more tickets together you need to:<br /> <br /> 1. Open the ticket you are wanting to link to/from<br /> <br /> 2. Click Link issue<br /> <br /> 3. Select why the issue is being linked (first drop down field)<br /> <br /> 4. In the search for issues field, start to type in either;<br /> <br /> a. Ticket ID, or<br /> <br /> b. Ticket name<br /> <br /> 5. Click the relevant ticket<br /> <br /> 6. Save<br /> [[File:How to link an issue.jpg|left|thumb|How to link an issue]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> === Action a ticket ===<br /> When a ticket is assigned, the assignee will receive an email alert from Jira. The ticket needs to be picked up within one working day and the responsibility for actioning and progressing the ticket sits with the assignee until the ticket is complete.<br /> <br /> If there is an action for someone other than the current assignee, that person needs tagging into the comments (using the @ symbol before their name) and the ticket also needs assigning to them. Once that action is complete, it needs assigning back to the original assignee.<br /> <br /> Once the ticket is resolved, it needs assigning to the reporter who will then change the ticket status if they are satisfied with the outcome.<br /> __FORCETOC__</div>

Jay https://wiki.voror.co.uk/index.php?title=File:How_to_link_an_issue.jpg&diff=2169 2020-08-04T12:31:36Z

<p>Jay: </p> <hr /> <div>How to link an issue</div>

Jay https://wiki.voror.co.uk/index.php?title=File:EQFIL_column_headings.jpg&diff=2168 2020-08-04T12:28:45Z

<p>Jay: </p> <hr /> <div>EQFIL column headings</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_Testing_and_Assurance&diff=2167 2020-08-04T10:57:17Z

<p>Jay: </p> <hr /> <div>== Introduction ==<br /> The Purpose of this section is to outline the strategy to be used for end user testing and assurance of data published to a remote data distribution service. <br /> <br /> Ideally the customer would be able to provide the source system data which would be used for assurance of the data provided in the RSD and confirm that IG is in place.<br /> <br /> == Roles and Responsibilities ==<br /> The customer will provide two types of data:<br /> <br /> • Statistical data to enable all teams to cross reference data, as it appears in the source system, the DDS and the remote transactional data bases. E.g. six GP practices providing numbers of: - Over 65s, plus a sample of numbers of patients on Diabetic, COPD, Asthma registers.<br /> <br /> • Specific patient data from a cross section of practices and patients. Taken as a screen shots of the patient’s medical record summary.<br /> [[File:Example_of_patient_specific_data.jpg|alt=|none|thumb|402.8x402.8px]]<br /> Each team has committed to responding to their testing requirements in a timely way.<br /> <br /> The DDS project manager will document this information, to be shared across teams, create Jira boards for communications and share lessons learned via the user forum.</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_Testing_and_Assurance&diff=2166 2020-08-04T10:51:05Z

<p>Jay: </p> <hr /> <div>== Introduction ==<br /> The Purpose of this section is to outline the strategy to be used for end user testing and assurance of data published to a remote data distribution service. <br /> <br /> Ideally the customer would be able to provide the source system data which would be used for assurance of the data provided in the RSD and confirm that IG is in place.<br /> <br /> == Roles and Responsibilities ==<br /> The customer will provide two types of data:<br /> <br /> • Statistical data to enable all teams to cross reference data, as it appears in the source system, the DDS and the remote transactional data bases. E.g. six GP practices providing numbers of: - Over 65s, plus a sample of numbers of patients on Diabetic, COPD, Asthma registers<br /> <br /> • Specific patient data from a cross section of practices and patients. Taken as a screen shots of the patient’s medical record summary.<br /> [[File:Example_of_patient_specific_data.jpg|alt=|none|thumb|402.8x402.8px]]<br /> Each team has committed to responding to their testing requirements in a timely way.<br /> <br /> The DDS project manager will document this information, to be shared across teams, create Jira boards for communications and share lessons learned via the user forum.</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_Testing_and_Assurance&diff=2165 2020-08-04T10:50:52Z

<p>Jay: </p> <hr /> <div>== Introduction ==<br /> The Purpose of this section is to outline the strategy to be used for end user testing and assurance of data published to a remote data distribution service. <br /> <br /> Ideally the customer would be able to provide the source system data which would be used for assurance of the data provided in the RSD and confirm that IG is in place.<br /> <br /> == Roles and Responsibilities ==<br /> The customer will provide two types of data:<br /> <br /> • Statistical data to enable all teams to cross reference data, as it appears in the source system, the DDS and the remote transactional data bases. E.g. six GP practices providing numbers of: - Over 65s, plus a sample of numbers of patients on Diabetic, COPD, Asthma registers<br /> <br /> • Specific patient data from a cross section of practices and patients. Taken as a screen shots of the patient’s medical record summary.<br /> [[File:Example_of_patient_specific_data.jpg|alt=|none|thumb|516.2x516.2px]]<br /> Each team has committed to responding to their testing requirements in a timely way.<br /> <br /> The DDS project manager will document this information, to be shared across teams, create Jira boards for communications and share lessons learned via the user forum.</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_Testing_and_Assurance&diff=2164 2020-08-04T10:45:20Z

<p>Jay: </p> <hr /> <div>== Introduction ==<br /> The Purpose of this section is to outline the strategy to be used for end user testing and assurance of data published to a remote data distribution service. <br /> <br /> Ideally the customer would be able to provide the source system data which would be used for assurance of the data provided in the RSD and confirm that IG is in place.<br /> <br /> == Roles and Responsibilities ==<br /> The customer will provide two types of data:<br /> <br /> • Statistical data to enable all teams to cross reference data, as it appears in the source system, the DDS and the remote transactional data bases. E.g. six GP practices providing numbers of: - Over 65s, plus a sample of numbers of patients on Diabetic, COPD, Asthma registers<br /> <br /> • Specific patient data from a cross section of practices and patients. Taken as a screen shots of the patient’s medical record summary.<br /> [[File:Example_of_patient_specific_data.jpg|alt=|none|frame]]<br /> Each team has committed to responding to their testing requirements in a timely way.<br /> <br /> The DDS project manager will document this information, to be shared across teams, create Jira boards for communications and share lessons learned via the user forum.</div>

Jay https://wiki.voror.co.uk/index.php?title=Remote_Subscriber_Database_Testing_and_Assurance&diff=2163 2020-08-04T10:44:05Z

<p>Jay: </p> <hr /> <div>== Introduction ==<br /> The Purpose of this section is to outline the strategy to be used for end user testing and assurance of data published to a remote data distribution service. <br /> <br /> Ideally the customer would be able to provide the source system data which would be used for assurance of the data provided in the RSD and confirm that IG is in place.<br /> <br /> == Roles and Responsibilities ==<br /> The customer will provide two types of data:<br /> <br /> • Statistical data to enable all teams to cross reference data, as it appears in the source system, the DDS and the remote transactional data bases. E.g. six GP practices providing numbers of: - Over 65s, plus a sample of numbers of patients on Diabetic, COPD, Asthma registers<br /> <br /> • Specific patient data from a cross section of practices and patients. Taken as a screen shots of the patient’s medical record summary.<br /> [[File:Example of patient specific data.jpg|left|thumb|573x573px|Example of patient specific data]]<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> Each team has committed to responding to their testing requirements in a timely way.<br /> <br /> The DDS project manager will document this information, to be shared across teams, create Jira boards for communications and share lessons learned via the user forum.</div>

Jay