generated from Birmingham-and-Solihull-ICS/BSOLproject
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ethnicity coding #17
Labels
question
Further information is requested
Comments
To lowest common denominator as NHS has not mandate 20 categories we have to stick with 16 NHS ones.
Richard Wilson (hear name<https://9ghd13g2.r.eu-west-1.awstrack.me/L0/https:%2F%2Fnamedrop.io%2Frichardwilson/1/0102018b235be771-9c0236f7-02ad-4e88-8355-b6a5af3ed5e1-000000/_A1GDkFKXYnnSz9S7TE83BDeZOg=343>)
Chief Analyst
Birmingham and Solihull ICB
First Floor | Wesleyan | Colmore Circus | Birmingham | B4 6AR
Phone: 07796 695127
[Icon Description automatically generated]
Find out more about how we are caring about healthier lives: www.birminghamandsolihullics.org.uk<http://www.birminghamandsolihullics.org.uk/>
From: Chris Mainey ***@***.***>
Sent: Thursday, May 9, 2024 4:59 PM
To: Birmingham-and-Solihull-ICS/BSOL_Outcomes_Framework ***@***.***>
Cc: Richard Wilson ***@***.***>; Mention ***@***.***>
Subject: [Birmingham-and-Solihull-ICS/BSOL_Outcomes_Framework] Ethnicity coding (Issue #17)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message originated from outside of NHSmail. Please do not click links or open attachments unless you recognise the sender and know the content is safe.
In the underlying data, how should we code the ethnicity: according to census or NHS?
@richardi7<https://github.com/richardi7> has uploaded a translation table in to the repo in /data/ folder, and I've added to the SQL Server environment too.
Currently if patient BSOL resident, ethnicity comes from the spine. If not, it comes hierarchically, based on data quality, from other sources.
-
Reply to this email directly, view it on GitHub<#17>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AROYSCTAV5ET4EX2EVABYNDZBOMLVAVCNFSM6AAAAABHPCDPTKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DOOJZGI2TGNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
************************************************************************************** ******************************
This message may contain confidential information. If you are not the intended recipient please:
i) inform the sender that you have received the message in error before deleting it; and
ii) do not disclose, copy or distribute information in this e-mail or take any action in relation to its content (to do so is strictly prohibited and may be unlawful).
Thank you for your co-operation.
NHSmail is the secure email, collaboration and directory service available for all NHS staff in England. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.
For more information and to find out how you can switch visit Joining NHSmail - NHSmail Support<https://support.nhs.net/article-categories/joining-nhsmail/>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the underlying data, how should we code the ethnicity: according to census or NHS?
@richardi7 has uploaded a translation table in to the repo in /data/ folder, and I've added to the SQL Server environment too.
Currently if patient BSOL resident, ethnicity comes from the spine. If not, it comes hierarchically, based on data quality, from other sources.
The text was updated successfully, but these errors were encountered: