Source fileequ

ClassRequirementV2FHIRCDAQuestion
gender identitySupport recording gender identity GSP segment
Gender Identity Template
gender identity associate with personwhere located in the message structure

GI will be an extension on the Patient, RelatedPerson, Person, and Practitioner Resources

responsibility of template container
gender identity zero to many instancesadded as optionally repeatingFor the instance (only one at a time/in the moment), there can be multiple over timeresponsibility of template container
gender identity gender coded type with textSOGI Concept Value (GSP-5), when SOGI Concept (GSP-4) = 76691-5^Gender Identity^LN (CWE)Individual-genderIdentity.valueCD (CONF:4536-48)
gender identity uses designated value setGenderIdentity (https://build.fhir.org/valueset-gender-identity.html)
Gender Identity Core Concepts (CONF:4536-48)
gender identity supports unknownUNK in value set, but can be extended, since example bindingUNK - Unknown. Unknown included (e.g., “was not able to ask” or “person does not want to answer”.)OTH/ASKU (CONF:4536-55)
gender identity supports other values (extensible)example bindingextensible value setshould (CONF:4536-48)
gender identity support validity period (period)Validity Range (GSP-6) (DR)Datatype of periodeffectiveTime (CONF:4536-50)
gender identity support comment (string)Comment (GSP-7) (TX)yes, datatype of CodeableConcepttext (CONF:4536-140)
pronounSupport recording pronounGSP segment
Pronoun Template
pronounassociate with personwhere located in the message structure
responsibility of template container
pronounzero to many instancesadded as optionally repeating
responsibility of template container
pronounpronoun coded type with textSOGI Concept Value (GSP-5), when SOGI Concept (GSP-4) = 90778-2^Personal pronouns - Reported^LN (CWE)
CD (CONF:4536-61)
pronounuses designated value setPronouns (http://build.fhir.org/valueset-pronouns.html)
Pronouns (CONF:4536-61)
pronounsupports unknowncan be extended, since example binding
Asked but Unknown and Other  (CONF:4536-67)
pronounsupports other values (extensible)Example binding
SHOULD (CONF:4536-61)
pronounsupport validity period (period)Validity Range (GSP-6) (DR)
effectiveTime (CONF:4536-69)
pronounsupport comment (string)Comment (GSP-7) (TX)
text (CONF:4536-72)

Support recording name to usePatient Name PID-5 (XPN) 
Record Target name
name to usename type structurePatient Name PID-5 (XPN), where name type code (PID-5.7) is valued 'N'
Patient.name
name to useassociate with personPatient Name PID-5 (XPN) 
Patient.name
name to usezero to many instances[0..*]
[0..*]
name to usesupport validity period (period)not covered
PersonName.validTime
name to usesupport comment (removed)

n/a
Sex for Clinical UseSupport recording Sex for Clinical UseGSC segment
Sex for clinical use Template
Sex for Clinical Useassociate with personwhere located in the message structure
responsibility of template container
Sex for Clinical Usezero to many instancesadded as optionally repeating
responsibility of template container
Sex for Clinical Usecategory coded type with textSex for Clinical Use (GSC-4) (CWE)
value with @xsi:type="CD" (CONF:4536-83)
Sex for Clinical Useuses designated value setSexForClinicalUse (http://hl7.org/fhir/sex-for-clinical-use)
sex-for-clinical-use (CONF:4536-137)
Sex for Clinical Usesupports unknownin value set
in value set
Sex for Clinical Userequires designated value setrequired binding
SHALL (CONF:4536-137)
Sex for Clinical Usesupport validity period (period)Validity Period (GSC-5) (DR)
effectiveTime (CONF:4536-82)
Sex for Clinical Usesupport comment (string)Comment (GSC-8) (TX)
text (CONF:4536-80)
Sex for Clinical Usesupport assertion of linked clinical obs evidence for assignmentEvidence (GSC-7) (ERL)
entryRelationship (CONF:4536-101)
Sex for Clinical Usesupport assertion of context for use: specific context (not modeled)Context (GSC-6) (ERL)
entryRelationship (CONF:4536-103)
Sex for Clinical Usesupport assertion of context for use: patientlocation in message
subject (CONF:4536-138)
Recorded Sex or GenderSupport recording of Recorded Sex or GenderGSR segmentRecorded sex or gender ExtensionRecorded sex or gender Template
Recorded Sex or Genderassociate with personwhere located in the message structurecontext = Patient, Person, RelatedPerson, Practitionerresponsibility of template container
Recorded Sex or Genderzero to many instancesadded as optionally repeating0..*responsibility of template container
Recorded Sex or GenderRSOG coded type or textRecorded Gender or Sex (GSR-4) (CWE) using this value set:  recordedGenderOrSex - values still TBD - example bindingextension: valuevalue with @xsi:type="CE" (CONF:4536-93)put code or field label here as translation
Recorded Sex or Genderinternational equivalent International Equivalent Sex Value (GSR-5) (CWE)extension: internationalEquivalent

Recorded Sex or Gendercoded type or text(CWE)CodeableConcepttranslation (CONF:4536-95)
Recorded Sex or Genderuses designated value sethttp://build.fhir.org/valueset-international-civil-aviation-organization-sex-or-gender.htmlInternational Civil Aviation Organization Sex Or Genderinternational-civil-aviation-organization-sex-or-gender (CONF:4536-95)
Recorded Sex or Genderreference to source document - NEWgapextension:sourceDocumentreference (CONF:4536-129)
Recorded Sex or GenderRecord Description type of document (string)Document Type (GRS-7) (CWE) with value set documentType - still TBD - may just make this a concept domain, unless there is vocab we can point to?in associated DocumentReferencecode="92183-3" Document type  (CONF:4536-119)
value with @xsi:type="CD" (CONF:4536-121)
originalText (CONF:4536-122)
implemented as CD; change to ST?
Recorded Sex or Gendersource field name (string)Source Document Field Label (GSR-5) (ST)extension: type.textTempElementCode originalText (CONF:4536-144)should be independent ST or
originalText for Observation.Code or
original text for Field Type
Recorded Sex or Genderfield type (code) - NEWgap - or we could go back to making Source Document Field Label a coded element?extension: type (CodeableConcept)TempElementCode value with @xsi:type="CD" (CONF:4536-136)An example would be persuasive
re-name to fieldType
Recorded Sex or Gendersource field definition (string)gap?gap?code="TempFieldDefCode" Field Definition (CONF:4536-134)
value with @xsi:type="ST" (CONF:4536-136)
need code;
or use methodCode
or derivationExpr
Recorded Sex or Genderacquisition date (date)Acquisition Date (GSR-9) (DTM)extension: acquisitionDate (dateTime)code="50786-3" Date of entry (CONF:4536-125)
value with @xsi:type="TS" (CONF:4536-128)
Is 'date of entry' close enough?
Recorded Sex or Genderjurisdiction (string)Jurisidiction (GSR-8) (CWE) - still TBD - suggest use of ISO-3166 (HL70347 points to ISO3166-2 for states / provinces; HL70399 to ISO 3166-1 for countries)extension: jurisdiction (CodeableConcept)code "77969-4" Jurisdiction code  (CONF:4536-109)
value with @xsi:type="CD" (CONF:4536-113)
originalText (CONF:4536-114)
implemented as CD; change to ST?
Recorded Sex or Gendersupport validity period (period)Acquisition Date (GSR-10) (DR)extension: effectivePeriod (period)effectiveTime (CONF:4536-94)
Recorded Sex or Gendercomment - NEWComment (GSR-11) (TX)extension: comment (string)
need?
Source Data Model Elements
ElementCaptured in SoftwareTranscribed from DocumentAssigned to software field based on document
Document (or "source artifact"?)
Referencen/aPossibly useful for provenance Possibly useful for provenance 
Typen/a (or "EHR"?)Understand context of collectionUnderstand context of collection
Namen/aUnderstand context of collectionUnderstand context of collection
Identifiern/aPossibly useful for provenancePossibly useful for provenance 
Field


NameUnderstand context of collectionUnderstand context of collectionUnderstand context of collection
TypeUnderstand context of collectionUnlikelyUnderstand current uses
DefinitionUnlikelyUnderstand context of collection
  • No labels