Demographics: gender is enforced and cannot be null

[p2]

I ran into this when working on Indivo's demographics, cross-posting from chb/indivo_server#36

---

The gender can only be male or female once it has been set, it cannot be null again. Removing the gender setting should be allowed. This is important should the patient not want to disclose the gender or is not able to because he/she is inter-sexual.

Related: #89

[jmandel]

Yes. I think there are two things to do:

1. Change the allowed values to "male" or "female" or "undifferentiated" (this simply mirrors the HL7 Administrative Gender value set).
2. Change cardinality to "0 or 1".

Does this capture it?

[p2]

This would definitely be enough, so you'd have 4 possibilities:

• female
• male
• undifferentiated
• unspecified (meaning it's not set)

[nschwertner]

I don't think that we have any restrictions on the values of the gender field defined in the ontology yet (unless I am missing something)... Would it make sense to encode this restriction properly there?

[jmandel]

We don't have any restrictions on string literals in the ontology, as far
as I know. There's a lot we could do here!

On Tue, Sep 25, 2012 at 4:32 PM, nschwertner [email protected]:

I don't think that we have any restrictions on the values of the gender
field defined in the ontology yet (unless I am missing something)... Would
it make sense to encode this restriction properly there?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/91#issuecomment-8874060.

[nschwertner]

Perhaps that could be one of the SMART 0.6 improvements then.

[nschwertner]

• First implemented in smart-classic/smart_sample_apps@21d5969
• Generalized implementation will follow in API Verifier Improvemens #129