| 3:30pm | Update for Gender Codes requested by Public Health
| Rob McClure | - Craig: Folks contacted us saying provider orgs are upgrading their EHRs and will be able to collect non-binary gender. 5 known including Colorado. Not sure what the IIS want to collect. We do not have a code for PID-8. Looking for guidance on how we handle this e.g. perhaps a new harmonisation proposal? Is Table 1 the right place for non-binary? Complexity with different kinds of gender and sex codes. Different product families deal with things differently e.g. tables, value sets, etc. In short, need guidance on how to handle non-binary in V2. Bound to table V2-0001.
- RobM: There is a technical issue. There is a need to represent information that people need e.g. the code 'X' in drivers licence in Colorado.
- Craig: Received input from EHR vendors, but not at the point that PID-8 is the right place for a values like non-binary. Different EHR providers are collecting subtly different things. If we expand that values in Table 0001
- RobM: Intent in agreeing to chair session, that we launch a process (that will not conclude in this quarter). However, can solve the immediate problem that does not conflict with the broader process. Hopefully this will be easier than negation.
- Cooper: Legal Sex means different things in different US States.
- Sarah: CDA has administrative gender, and birth sex template (with two values - Male and Female). I am interested because national healthcare services who wish to add gender identity.
- Reuben: Australian national standard AS 4846-2014 includes Gender Identity as a field with values: Male, Female Intersex, Indeterminate, Other, Person prefers not to say, Unknown/Inadequately Described
- Sarah: Happy to add a template for gender identity in CDA, but I need a value set.
- Steve: Its been reported that insurers are not paying due to labs sex/gender not aligning with what the patient told the doctor.
- Craig: This information is sometimes held in OBX segments. LOINC codes exist for these.
- RobM: Perhaps the best option is to add 'X' to table V2-0001
- Craig: Another option is to introduce a new table with Gender Identity values
- Ted: Difficult to add the code to table V2-0001 as a backwards errata. However, you can make changes to the current table.
- MOTION by Craig Newman:
- The advice of the vocabulary group is as follows:
- O is the best option to represent non-binary in the existing value set
- A harmonization proposal will be created to added X for non-binary (potentially including a clarification of other terms in the table) in the most current version of Table HL70001
- Do we include transgender codes?
- The vocabulary group will continue to pursue a more comprehensive solution to the problem of documenting and exchanging gender concepts across product families
Motion passes: 17-0-3
|
