Version Published Changed By Comment
CURRENT (v. 13) Jun 20, 2022 21:19

Go to Page History

Use Case Description:

Post Gender Harmony model implementation with mis-naming from the EHR

Patient with EHR Sex for Clinical Use (SfCU) of “female” and a EHR Gender Identity of “male” arrives for check-in at a facility using a DICOM worklist for a PET/CT examination.

Actors:

People

  1. Patient (John Smith) - whose previous records are for studies performed when his EHR Gender Identity was “female”. 
  2. Facility Clerk - admits patient, utilizes DICOM worklist
  3. PET/CT Technician
  4. Exam Prep Team (e.g., nurse)
  5. Recovery Nurse

Systems

  1. Hospital EHR
  2. Worklist Management System (e.g., RIAS, Gateway, Scheduler)
  3. PET/CT System
  4. RDSR

Scope Statement:

Use case covers admission, patient prep, examination, recovery and analysis.

Precondition(s):

  1. John Smith is registered in the hospital record system with his old name of “Janet Smith”
  2. John Smith arrives at an outpatient facility with an appointment
  3. Patient history, Social history, medical history have already been captured upstream and are available in the facility's system
  4. Physician order for examination is utilizing information from the facility
  5. Facility system has not been updated for the name change

Postcondition(s):

  1. PET/CT Examination is completed or cancelled
  2. Report is generated
  3. Discussion to initiate name change correction in the EHR has occurred
  4. DICOM Name to Use is updated based on policy. For example:
    1. EHR name (John Smith) is associated with a Name to Use element whose validity period ends on day of exam
    2. Add a Name to Use (Janet Smith) whose validity period begins on day of exam

Workflow/Storyboard:

Arrival and check-in:

Scenario 1, where patient initiates the discussion

  1. When John arrives at the waiting room for a PET/CT examination he announces himself as “John”.

  2. The clerk asks “John Williams?”, seeing a John Williams in the current worklist. (This example assumes that the DICOM worklist is being used. Similar scenarios apply when HL7 facilities are used.)

  3. Response, “No, Smith”

  4. The clerk asks “Date of birth”

  5. Smith: “month, day, year”

  6. The clerk performs a date of birth based lookup and finds:

    1. A DICOM worklist entry for Janet Smith, with Patient’s Sex (0010,0040) “F” and Patient’s Gender (0010,xxxx) “M”, and with a Preferred Form of Address (0010,xxx3) “Preferred name is John”. Sex Comment (0010,xxx1) contains “Hormonal treatment causes Thrombosis risk”.

    2. The birth dates match

  7. The clerk asks the necessary sex related preparation questions, e.g., most recent menstruation; and checks in the patient.

  8. Based on clinic policies, the clerk asks whether John wants to go through the name change process at the clinic to reflect his preferred name.

Patient Preparation

  1. The prep staff checks their worklist for John, and finds the order for “Janet Smith”, Patient’s Sex (0010,0040) “F” and Patient’s Gender (0010,xxxx) “M”, and with a Preferred Form of Address (0010,xxx2) “John”. Sex Comment (0010,xxx1) contains “Hormonal treatment causes Thrombosis risk”.

  2. The prep staff sets up John’s radiation protection for a female body, confirms menstruation and pregnancy status, and reconfirms birthdate.

Examination

  1. The technician has checked John’s worklist entry and knows to expect a female body for John this does not trigger a wrong patient concern. The technician confirms birthdate and other ID for the patient.

  2. The exam is performed.

  3. The study results and RDSR are stored into the archive

Recovery

  1. Recovery nurse monitors the patient using the thrombosis risk protocol rather than the normal protocol.

  2. Recovery nurse will use the patient's name to use when addressing the patient 

Analysis

  1. The PET/CT application computing the SUV uses the SfCU “F”. It notes the Patient’s Gender (0010,xxxx) “M” and presence of Sex Comment (0010,xxx1), and shows a pop-up to the operator to confirm that this is the correct value to use.

  2. The RDSR is used to prepare a patient dose report. Because the Patient Sex (0010,0040) is F, the female body models are used for dose analysis for John.

Alternative and/or related Workflow(s):

Arrival and check-in:

Scenario 2, where the clerk initiates the discussion

  1. John arrives at the waiting room for a PET/CT examination, and goes to the clerk to check in.

  2. The clerk asks “Date of birth”

  3. Smith: “month, day, year”

  4. The clerk performs a date of birth based lookup and finds:

    1. A DICOM worklist entry for Janet Smith, with Patient’s Sex (0010,0040) “F” and Patient’s Gender (0010,xxxx) “M”, and with a Preferred Form of Address (0010,xxx3) “Preferred name is John”. Sex Comment (0010,xxx1) contains “Hormonal treatment causes Thrombosis risk”.

    2. The birth dates match

  5. The clerk sees John, who appears to be a man, and re- checks the worklist entry. This time the clerk notices Patient’s Gender (0010,xxxx) “M”, Patient’s Sex (0010,0040) “F”,  and a Preferred Form of Address (0010,xxx3) “Preferred name is John”.

  6. The clerk confirms “John Smith? Here for a PET/CT exam?”

  7. John agrees.

  8. The clerk asks the necessary sex related preparation questions, e.g., most recent menstruation; and checks in the patient.

  9. Based on clinic policies, the clerk asks whether John wants to go through the name change process at the clinic to reflect his preferred name.

Alignment and/or Misalignment with Gender Harmony Model:


Current Standard Support:

  • HL7 V2.x   
V2.x Resource: 
  • HL7 V3
V3 Resource:
  • HL7 FHIR
FHIR Resource:
  • DICOM

DICOM Resource:

SOP Classes:

Modality WorkList

all Image Storage SOPs

Attributes:

Patient’s Gender (0010,xxxx)

Patient’s Sex (0010,0040)

  • NCPDP
NCPDP Resource:
  • X12
X12 Resource:
  • Other (please specify standard and resource below)

Other:

Required Additional Standard Support:


  • No labels