Feature Request: Add Standard definitions for Reference Data to the Playbook - Gender #6
Description
Why
As a data architect, I need to know the standard definition for Gender so that I can ensure that systems that I support are able to accept the full list of possible genders.
Acceptance Criteria
- Open Data Portal has new classification "Reference Data", and the taxonomy of the Open Data is added to the Playbook
- New section added to the Playbook to address Data Classification and the role of reference data as a means to control the list of values used by systems to describe common data.
- List of Gender codes is published to the Open Data Portal, using the values from HL7 as a starting point
- Fields: Code, Label, Description, Domain (["All"|"Program"|"Industry"|]), Effective Start Date, Effective End Date, Alias-Code, Alias-Label. *Note: Alias fields are CSV snippets that provide cross-walk to other codes or labels that are semantically matched to the given "Code" or "Label"
- list is linked back to the Data Classification section of the Playbook.
Technical Notes
- Captured as a response to inquiry from Chand Gill at DMHC (credit)
- Article on the SFData Playbook: Sexual Orientation & Gender Identity (SOGIE). It doesn’t provide an actual code/label, but it’s useful background. More material linked from that page too. I have copied several folks who may have a canonical answer based on current practice.
- Data Exchange Standards: HL7 and NIEM. NIEM is limited (1, 2), and does not align with medical and social service practices or our SOGIE regulations. I suggest HL7 for DMHC.
- HL7 definition for Gender: http://hl7.org/fhir/gender-identity