This page is part of the HL7 Cross Paradigm IG: Gender Harmony - Sex and Gender Representation (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR v5.0.0-ballot. . For a full list of available versions, see the Directory of published versions
This use case is illustrative of how ancillary systems in imaging, downstream from the EHR, are likely to consume and create evidence documents in response to Sex and Gender encoding. In this case, there are three instances of Sex For Clinical Use (SFCU). First, the ordering physicians provides instructions for interpreting lab values within a Sex for Clinical Use comment. In the second SFCU, an Artifical Intelligence (AI) application utilizes the Sex Assigned at Birth for the basis of reference values. Third, the radiologist determines the appropriate sex to use based on the patient’s body composition for a Standard Uptake Value (SUV) calculation. The DICOM (Digital Imaging and COmmunications in Medicine) attributes in this use case are not normative, and details in DICOM are still being defined. If interested in participating in development of DICOM Sex and Gender encoding please contact the DICOM Secretariat.
Public comment, based on this use case is sought on the following Open Issues:
Technologist may be in a position to observe a discrepancy between the current medical record and “observed” information. Where and how is this communicated to other actors? Where and how is reconciliation performed? Considerations include:
Authoritative sources of observations
Official systems of record
See also IHE (Integrating the Healthcare Enterprise) Scheduled Workflow 34.4.2.2 Use Case #2: Patient Update in which upstream systems (ADT / RIS) perform a patient update or merge.
What imaging activities are effected by the discrepant observation, and how should those be handled prior to reconciliation (e.g. protocol selection, post processing, report content)?
In the cross-community scenario:
How to manage the case if one jurisdiction does not recognize the sex/gender attributes of another?
What impact will the patient name change have on the Master Patient Index weighting of search results?
Is this likely to require a manual merge of records? (see IHE ITI-30)
A mix of upgraded and non-upgraded systems may result in a scenario in which one system, does not recognize sex attributes of the other. Priors are likely generated by non-upgraded systems. Search reliability may be negatively impacted when there is discrepant information (patient situation change, attributes within records have changed). How is this handled?
How does this change in an encounter-based activity? Consider direct in-person clinical care vs tele health?
How to deal with the non-communicative patient?
Some machine-based algorithms are tuned based on patient age and sex at birth for the application of established reference values. How should this be considered?
Are there updates that should be considered for the DICOM attribute, Confidentiality constraint on patient data (0040,3001) VR=LO, to support local confidentiality approaches that may be applied to transgender demographics changes?
Should name to use be PN or LT VR? A patient, may want to be referred to as “Commander Bob”.
In this Use Case, a single ADT message is created to communicate the patient name change. Is the order of the repeating elements in PID-5 significant? Should there be one ADT message or two (i.e. one message to communicate the new name, a second message to flag the old name as “NOUSE”)?
Post Gender Harmony model implementation with incorrect 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. The examination is performed, the patient’s demographics are updated, and the report is delivered.
Patient (John Smith) - whose previous records are for studies performed when his EHR Gender Identity was “female”.
Facility Clerk - admits patient, utilizes the Radiology Information System (RIS)
PET/CT Technologist
Recovery Nurse
Hospital EHR (ADT, Order Placer)
RIS (Order Filler)
PET/CT Modality System
Image Manager/Archive (PACS: Picture Archive and Communications System)
Dose Information Reporter
AI (Artificial Intelligence) Task Performer
Use case covers admission, patient prep, examination, recovery, post processing and reporting for a PET/CT examination order.
John Smith is registered in the hospital record system with his old name of “Janet Smith”
Patient ID has not changed
John Smith arrives at an outpatient facility with an appointment
Patient history, social history, medical history has already been captured upstream and are available in the facility’s EHR
Physician order for examination is utilizing information from the facility
Facility system has not been updated for the name change
Relevant prior exams for comparison are retrieved based on rules established by the radiology department, using the name Janet Smith (e.g., body region, patient ID, type of exam).
Technical scan and contrast administration parameters (protocol) are pre-determined based on departmental protocols for a female patient
Example 01 depicts a HL7 v2.9.1 Imaging Order for this patient with mapping to DICOM Modality Worklist attributes.
PET/CT Examination is complete or cancelled
Report is generated and available
Discussion to initiate name change correction in the EHR has occurred
DICOM Name to Use is updated based on policy. For example:
EHR name (John Smith) is associated with a Name to Use element whose validity period ends on day of exam
Add a Name to Use (Janet Smith) whose validity period begins on day of exam
Figure 1 Workflow Storyboard
In this scenario, the patient initiates the discussion with the clerk.
When John arrives at the waiting room for a PET/CT examination he announces himself as “John”.
The clerk asks “John Williams?”, seeing a John Williams in the schedule.
Response, “No, Smith”
The clerk asks “Date of birth”
Smith: “month, day, year”
The clerk performs a date-of-birth based lookup and finds:
A schedule entry for Janet Smith, with Patient’s Sex “F” and Patient’s Gender “M”, and with a Patient Names to Use “John Smith”. Sex Comment contains “Hormonal treatment, use affirmed gender Cr reference ranges[1]”.
The clerk confirms that the birth dates match, confirms the patient’s identity in accordance with local policies, and checks in the patient.
The HL7 v2.9.1 message is converted to DICOM Modality Worklist (MWL) Attributes (partial SOP Instance contents) for the MWL query. After check-in, the order is visible in the MWL
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. Name change is initiated.
The clerk notifies the technologist that the patient has arrived.
Example 02 depicts a HL7 v2.9.1 Demographics Update message for this patient with mapping to DICOM Modality Worklist attributes.
The technologist checks their schedule for John, and finds the order for “Janet Smith”, Patient’s Sex “F” and Patient’s Gender “M”, and with a Patient Names to Use “John Smith”. Sex Comment contains “Hormonal treatment, use affirmed gender Cr reference ranges”.
The technologist greets the patient as “John” and reconfirms birthdate.
The technologist directs the patient to a changing area and instructs the patient to remove jewelry and change into a gown.
When the patient is ready, the technologist asks the necessary related preparation questions, e.g., pregnancy status, most recent menstruation, allergies, history, preferred arm for IV contrast administration, etc.
The technologist explains the procedure to the patient and answers any questions the patient may have.
Since the protocol calls for a contrast-enhanced CT, the technologist reviews the most recent eGFR, bun and creatine.
The technologist confers with the radiologist to discuss acceptable lab values for safe contrast administration, given the Sex Comment, as well as the patient’s GFR, bun and creatine.
The radiologist notes that the provided SFCU of Female, is not consistent with the SFCU Comment and calls the ordering physician to confirm.
After discussing patient history with the ordering physician, the radiologist provides protocol alterations based on the patient’s transgender status.
Note: The pre-identified protocol was based on a female patient (see item 8 in Precondition(s)).
The technologist knows to select the MWL entry for “Janet Smith” and expects a Patient’s Sex of “F”; this does not trigger a wrong patient concern.
Patient demographics are loaded into the scanner demographics interface.
The technologist applies alterations prescribed by the radiologist to scanner and contrast protocol. The radiotracer dose is not changed, as the department standardizes doses regardless of Patient’s Sex.
The technologist starts an IV, administers radiotracer, and connects the contrast injector for the contrast-enhanced CT portion of the procedure.
The study is performed.
During administration of iodinated CT contrast, the patient complained of nausea. The technologist notifies the departmental nurse, who agrees to monitor the patient for an allergic reaction after the procedure.
The images and Radiation Dose Structured Report (RDSR) are transferred to the PACS, Dose Information Reporter and AI Task Performer systems.
The radiologist creates an SUV ROI on the PACS. The application detects the presence of Patient’s Sex (0010,0040) “F”, a Gender Code (0010,xxx4).(0008,0104) “Male” and Sex Assigned at Birth (0010,xx25) of “F” and prompts the radiologist to enter a value “M” or “F”.
The Dose Information Reporter collects the RDSR, without exception since Patient’s Sex or Gender is not likely to influence deterministic risk calculation estimates.
The AI task performer detects the Sex Assigned at Birth (0010,xx25) of “F”, the algorithm processes the images based on female reference values and transfers evidence documents to the PACS.
Note: Sex at Birth is required to determine reference values for AI and non-AI machine algorithims in various domains, such as cardiology and neurology.
The radiologist dictates findings pertaining to the procedure, noting scanner and contrast protocol modifications in the “Request” section of the report.
The report format has been configured to include Patient’s Sex (0010,0040), Patient’s Gender Code (0010,xxx4).(0008,0104), Patient Name (0010,xxx3).(0010,xx12) and SFCU Comment (0010,xxx1) in the report.
Patient’s Name = “Janet Smith”
Patient’s Sex = “F”
Patient’s Gender = “M”
Name to Use = “John Smith”
Patient’s Name = “John Smith”
Patient’s Sex = “F”
Patient’s Gender = “M”
Name to Use = “John Smith”
The final report may be represented in FHIR, HL7 v2, or a CDA.
Below is a HL7 v2.9.1 OMI Imaging Order from precondition(s).
MSH|^~\&|||||20220715090000||OMI^O23|WSA5mY0UBuCGrytRTAFR8UWJ|P|2.9.1
PID|||patientID^^^^MR||Smith^Janet^^^^^B~Smith^John^^^^^D|||F
GSP|1|S||76691-5^Gender identity^LN|446151000124109^Identifies as male gender^SCT|20220715090000
GSC|1|S||248152002^Female^SCT|20220715090000|OBR^4||Hormonal treatment, use affirmed gender Cr reference ranges
ORC|NW||||||||20220715090000|||^Cure^Matt^^^^MD
OBR|1|entityID|fillrtOrderNum|82800-4^PET+CT Heart W contrast IV^LN||||||||||||||||||||NMS|||||||^Reason for Study|
IPC|accessionNum|procedureID|studyInstanceUID|schProcedureStepId|PT^Positron emission tomography^DCM|122793^PET Myocardial Perfusion, Rest and Stress^DCM
This maps to DICOM Modality Worklist as follows:
V2 | Attribute Name | Tag | VR | Value |
---|---|---|---|---|
PID-5 Name Type Code = Birth Name | Patient’s Name | (0010,0010) | PN | Smith\^Janet^^^ |
PID-8 | Patient’s Sex | (0010,0040) | CS | F |
Patient’s Gender | (0010,xxxx) | CS | M | |
Gender Identity Sequence | (0010,xxxx) | SQ | ||
>Gender Code Sequence | (0010,xxx4) | SQ | ||
GSP-5-1 | >>Code Value | (0008,0100) | SH | 446151000124109 |
GSP-5-3 | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
GSP-5-2 | >>Code Meaning | (0008,0104) | LO | Identifies as male gender |
>Validity Period sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | ||
>>Stop DateTime | (0010,xxx7) | DT | ||
>Gender Comment | (0010,xxx8) | LT | ||
Sex Comment | (0010,xxx1) | LT | ||
Sex for Clinical Use Sequence | (0010,xxx2) | SQ | ||
>SFCU Code Sequence | (0010,xxx9) | SQ | ||
GSC-4-1 | >>Code Value | (0008,0100) | SH | 248152002 |
GSC-4-3 | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
GSC-4-2 | >>Code Meaning | (0008,0104) | LO | Female |
>Validity Period sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | 20220715090000 | |
>>Stop DateTime | (0010,xxx7) | DT | ||
GSC-8 | >SFCU Comment | (0010,xxx1) | LT | Hormonal treatment, use affirmed gender Cr reference ranges |
>SFCU Reference | (0010,xx10) | UR | ||
Person Names to Use Sequence | (0010,xxx3) | SQ | ||
PID-5 Name Type Code = Customary | >Name to use | (0010,xx12) | LT | Smith, John |
>Validity Period Sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | 20220715090000 | |
>>Stop DateTime | (0010,xxx7) | DT | ||
>Name to Use Comment | (0010,xx13) | LT | ||
PID-8 (based on local mapping rules) | Sex at Birth Code Sequence | (0010,xx25) | CS | F |
>>Code Value | (0008,0100) | SH | 248152002 | |
>>Coding Scheme Designator | (0008,0102) | SH | SCT | |
>>Code Meaning | (0008,0104) | LO | Female |
Below is a HL7 v2.9.1 ADT Demographics Update from arrival and check-in.
MSH|^~\&|||||20220715010000||ADT^A08|TwxxneTRWE9JGX4U2p3h|P|2.9.1
EVN||20220715151118||01
PID|||patientID^^^^MR||Smith^John^^^^^D~Smith^Janet^^^^^NOUSE|||F|
GSP|1|S||76691-5^Gender identity^LN|446151000124109^Identifies as male gender^SCT|20220715010000
PV1||O
Note: in previous v2 versions, the first occurrence indicated the legal name. In this case, the Customary name is listed first for legacy compatibility.
This maps to DICOM Modality Worklist as follows:
V2 | Attribute Name | Tag | VR | Value |
---|---|---|---|---|
PID-5 Name Type Code = Customary | Patient’s Name | (0010,0010) | PN | Smith\^John^^^ |
PID-8 | Patient’s Sex | (0010,0040) | CS | F |
Patient’s Gender | (0010,xxxx) | CS | M | |
Gender Identity Sequence | (0010,xxxx) | SQ | ||
>Gender Code Sequence | (0010,xxx4) | SQ | ||
GSP-5-1 | >>Code Value | (0008,0100) | SH | 446151000124109 |
GSP-5-3 | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
GSP-5-2 | >>Code Meaning | (0008,0104) | LO | Identifies as male gender |
>Validity Period sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | 20220715010000 | |
>>Stop DateTime | (0010,xxx7) | DT | ||
>Gender Comment | (0010,xxx8) | LT | ||
Sex Comment | (0010,xxx1) | LT | ||
Sex for Clinical Use Sequence | (0010,xxx2) | SQ | ||
>SFCU Code Sequence | (0010,xxx9) | SQ | ||
GSC-4-1 | >>Code Value | (0008,0100) | SH | 248152002 |
GSC-4-3 | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
GSC-4-2 | >>Code Meaning | (0008,0104) | LO | Female |
>Validity Period sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | ||
>>Stop DateTime | (0010,xxx7) | DT | ||
GSC-8 | >SFCU Comment | (0010,xxx1) | LT | Hormonal treatment, use affirmed gender Cr reference ranges |
>SFCU Reference | (0010,xx10) | UR | ||
Person Names to Use Sequence | (0010,xxx3) | SQ | ||
>Name to use | (0010,xx12) | LT | ||
>Validity Period Sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | 20220715009000 | |
>>Stop DateTime | (0010,xxx7) | DT | ||
>Name to Use Comment | (0010,xx13) | LT | ||
PID-8 (based on local mapping rules) | Sex at Birth Code Sequence | (0010,xx25) | CS | F |
>>Code Value | (0008,0100) | SH | 248152002 | |
>>Coding Scheme Designator | (0008,0102) | SH | SCT | |
>>Code Meaning | (0008,0104) | LO | Female |
The patient is referenced as the subject of DiagnosticReport, DocumentReference, ImagingStudy or ImagingSelection. Mapping to DICOM is as follows:
FHIR attribute | Attribute Name | TAG | VR | Value |
---|---|---|---|---|
Patient.name.use=official | Patient’s Name | (0010,0010) | PN | Smith\^John^^^ |
Patient.gender | Patient’s Sex | (0010,0040) | CS | F |
Gender Identity Sequence | (0010,xxxx) | SQ | ||
Patient.genderIdentity.value | >Gender Code | (0010,xxx4) | SQ | |
code | >>Code Value | (0008,0100) | SH | 446151000124109 |
system | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
display | >>Code Meaning | (0008,0104) | LO | Identifies as male gender |
Patient.genderIdentity.period | >Validity Period sequence | (0010,xxx5) | SQ | |
start | >>Start DateTime | (0010,xxx6) | DT | 20220715010000 |
end | >>Stop DateTime | (0010,xxx7) | DT | |
>Gender Comment | (0010,xxx8) | LT | ||
Sex Comment | (0010,xxx1) | LT | ||
Sex for Clinical Use Sequence | (0010,xxx2) | SQ | ||
serviceRequest.sexForClinicalUse.value | >SFCU Code Sequence | (0010,xxx9) | SQ | |
code | >>Code Value | (0008,0100) | SH | 248152002 |
system | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
display | >>Code Meaning | (0008,0104) | LO | Female |
serviceRequest.sexForClinicalUse.period | >Validity Period sequence | (0010,xxx5) | SQ | |
start | >>Start DateTime | (0010,xxx6) | DT | 20220715090000 |
end | >>Stop DateTime | (0010,xxx7) | DT | |
serviceRequest.sexForClinicalUse.comment | >SFCU Comment | (0010,xxx1) | LT | Hormonal treatment, use affirmed gender Cr reference ranges |
>SFCU Reference | (0010,xx10) | UR | ||
Person Names to Use Sequence | (0010,xxx3) | SQ | ||
Patient.name.use=usual | >Name to use | (0010,xx12) | LT | John Smith |
>Validity Period Sequence | (0010,xxx5) | SQ | ||
>>Start DateTime | (0010,xxx6) | DT | ||
>>Stop DateTime | (0010,xxx7) | DT | ||
>Name to Use Comment | (0010,xx13) | LT | ||
Patient.gender (based on local mapping) | Sex at Birth Code Sequence | (0010,xx25) | CS | F |
code | >>Code Value | (0008,0100) | SH | 248152002 |
system | >>Coding Scheme Designator | (0008,0102) | SH | SCT |
display | >>Code Meaning | (0008,0104) | LO | Female |
Below is a HL7 v2.9.1 Unsolicited Observation Result containing the narrative from the final Imaging Report.
MSH|^~\&|||||20220715142240||ORU^R01|WSA5mY0UBuCGrytRTAFR8UWJ|P|2.9.1
PID|||patientID^^^^MR||Smith^John^^^^^D|||F|
GSP|1|S||76691-5^Gender identity^LN|446151000124109^Identifies as male gender^SCT
GSC|1|S||248152002^Female^SCT||OBR^4||Hormonal treatment, use affirmed gender Cr reference ranges
ORC|CN||||||||20220715090000|||^Cure^Matt^^^^MD
OBR|1|accessionNum||82800-4^PET+CT Heart W contrast IV^LN|||20220715110000||||
OBX|1|CWE|55111-9^Current Imaging Procedure Description^LN||Imaging technique (protocol, contrast, radiotracer) described here||||||F|
OBX|2|CWE|19005-8^Impression^LN||Report narrative goes here||||||F|
OBX|3|CWE|55110-1^Conclusion^LN||Conclusion goes here||||||F|
OBX Segments containing Imaging Report Narrative omitted for brevity
Below is a CDA Imaging Report example.
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="CDA.xsl"?>
<!--
Title: Sex for Clinical Use CDA Template Example file
Version: 1.0
Revision History:
31-Jan-2011 source document created
19-Aug-2022 example drafted [Jay Lyle, JP Systems for the VHA;
Rob Horn, Fairhaven Technology;
Steven Nichols, GE Healthcare]
-->
<ClinicalDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:hl7-org:v3"
xmlns:mif="urn:hl7-org:v3/mif" xmlns:voc="urn:hl7-org:v3/voc"
xsi:schemaLocation="urn:hl7-org:v3 CDA.xsd">
<!--
********************************************************
CDA Header
********************************************************
-->
<realmCode code="US"/>
<typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040"/>
<!-- US General Header Template -->
<templateId root="2.16.840.1.113883.10.20.22.1.1"/>
<!-- Diagnostic Imaging Report Template -->
<templateId root="2.16.840.1.113883.10.20.22.1.5"/>
<id root="2.16.840.1.113883.19.4.27" extension="20060828170821659"/>
<code code="18748-4" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"
displayName="Diagnostic Imaging Report"/>
<title>PET/CT Heart W contrast IV</title>
<effectiveTime value="20050329171504+0500"/>
<confidentialityCode code="N" codeSystem="2.16.840.1.113883.5.25"/>
<languageCode code="en-US"/>
<setId extension="111199021" root="2.16.840.1.113883.19"/>
<versionNumber value="1"/>
<recordTarget>
<!--NEW CONF per base CDA - patientRole SHALL be present of [1..*]-->
<patientRole>
<id extension="12345" root="2.16.840.1.113883.19.5"/>
<addr use="HP">
<streetAddressLine>3300 Washtenaw Ave # 227</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(734)555-1212" use="HP"/>
<patient>
<name use="L">
<given>Smith</given>
<family>John</family>
</name>
<administrativeGenderCode code="F" codeSystem="2.16.840.1.113883.5.1"/>
<birthTime value="19541125"/>
<maritalStatusCode code="S" displayName="Single" codeSystem="2.16.840.1.113883.5.2"
codeSystemName="MaritalStatusCode"/>
<religiousAffiliationCode code="1013" displayName="Christian"
codeSystemName="HL7 Religious Affiliation "
codeSystem="2.16.840.1.113883.5.1076"/>
<raceCode code="2106-3" displayName="White" codeSystem="2.16.840.1.113883.6.238"
codeSystemName="Race & Ethnicity - CDC"/>
<ethnicGroupCode code="2186-5" displayName="Not Hispanic or Latino"
codeSystem="2.16.840.1.113883.6.238" codeSystemName="Race & Ethnicity - CDC"/>
<guardian>
<code code="GRFTH" displayName="Grandfather"
codeSystem="2.16.840.1.113883.5.111" codeSystemName="HL7 Role code"/>
<addr use="HP">
<streetAddressLine>3300 Washtenaw Ave # 227</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(734)555-1212" use="HP"/>
<guardianPerson>
<name>
<given>Ralph</given>
<family>Relative</family>
</name>
</guardianPerson>
</guardian>
<birthplace>
<place>
<addr>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
</place>
</birthplace>
<languageCommunication>
<languageCode code="fr-CN"/>
<modeCode code="RWR" displayName="Recieve Written"
codeSystem="2.16.840.1.113883.5.60" codeSystemName="LanguageAbilityMode"/>
<preferenceInd value="true"/>
</languageCommunication>
</patient>
<providerOrganization>
<id root="2.16.840.1.113883.19.5"/>
<name>Good Imaging Clinic</name>
<telecom value="tel:(734)555-1212"/>
<addr>
<streetAddressLine>21 North Ave</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
</providerOrganization>
</patientRole>
</recordTarget>
<author>
<time value="20050329224411+0500"/>
<assignedAuthor>
<id extension="KP00017" root="2.16.840.1.113883.19.5"/>
<addr>
<streetAddressLine>21 North Ave.</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(555)555-1003"/>
<assignedPerson>
<name>
<given>Bill</given>
<family>Roentgen</family>
</name>
</assignedPerson>
</assignedAuthor>
</author>
<dataEnterer>
<assignedEntity>
<id root="2.16.840.1.113883.19.5" extension="43252"/>
<addr>
<streetAddressLine>21 North Ave.</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(555)555-1003"/>
<assignedPerson>
<name>
<given>Bill</given>
<family>Roentgen</family>
</name>
</assignedPerson>
</assignedEntity>
</dataEnterer>
<custodian>
<assignedCustodian>
<representedCustodianOrganization>
<id root="2.16.840.1.113883.19.5"/>
<name>Good Imaging Clinic</name>
<telecom value="tel:(555)555-1212" use="WP"/>
<addr use="HP">
<streetAddressLine>3300 Washtenaw Ave # 227</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
</representedCustodianOrganization>
</assignedCustodian>
</custodian>
<informationRecipient>
<intendedRecipient>
<informationRecipient>
<name>
<given>Bill</given>
<family>Roentgen</family>
</name>
</informationRecipient>
<receivedOrganization>
<name>Good Imaging Clinic</name>
</receivedOrganization>
</intendedRecipient>
</informationRecipient>
<legalAuthenticator>
<time value="20050329224411+0500"/>
<signatureCode code="S"/>
<assignedEntity>
<id extension="KP00017" root="2.16.840.1.113883.19.5"/>
<addr>
<streetAddressLine>21 North Ave.</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(555)555-1003"/>
<assignedPerson>
<name>
<given>Bill</given>
<family>Roentgen</family>
</name>
</assignedPerson>
</assignedEntity>
</legalAuthenticator>
<authenticator>
<time value="20050329224411+0500"/>
<signatureCode code="S"/>
<assignedEntity>
<id extension="KP00017" root="2.16.840.1.113883.19.5"/>
<addr>
<streetAddressLine>21 North Ave.</streetAddressLine>
<city>Ann Arbor</city>
<state>MI</state>
<postalCode>48104</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(555)555-1003"/>
<assignedPerson>
<name>
<given>Bill</given>
<family>Roentgen</family>
</name>
</assignedPerson>
</assignedEntity>
</authenticator>
<inFulfillmentOf>
<order>
<id extension="10523475" root="1.2.840.113619.2.62.994044785528.27"/>
<code code="121022" codeSystem="1.2.840.10008.2.16.4" codeSystemName="DCM"
displayName="Accession Number"/>
</order>
</inFulfillmentOf>
<documentationOf>
<serviceEvent classCode="ACT">
<id root="1.2.840.113619.2.62.994044785528.114289542805"/>
<!-- study instance UID -->
<code code="78814"
displayName="Positron emission tomography (PET) with concurrently acquired computed tomography (CT)"
codeSystem="2.16.840.1.113883.6.12" codeSystemName="CPT4"/>
<effectiveTime value="20060823222400"/>
<performer typeCode="PRF">
<templateId root="2.16.840.1.113883.10.20.6.2.1"/>
<assignedEntity>
<id extension="121008" root="2.16.840.1.113883.19.5"/>
<code code="2085R0202X" codeSystem="2.16.840.1.113883.11.19465"
codeSystemName="NUCC" displayName="Diagnostic Radiology"/>
<addr nullFlavor="NI"/>
<telecom nullFlavor="NI"/>
<assignedPerson>
<name>
<given>Matt</given>
<family>Cure</family>
<suffix>MD</suffix>
</name>
</assignedPerson>
</assignedEntity>
</performer>
</serviceEvent>
</documentationOf>
<relatedDocument typeCode="XFRM">
<parentDocument>
<id root="1.2.840.113619.2.62.994044785528.20060823.200608232232322.9"/>
<!-- SOP Instance UID (0008,0018) -->
</parentDocument>
</relatedDocument>
<componentOf>
<encompassingEncounter>
<id extension="9937012" root="1.3.6.4.1.4.1.2835.12"/>
<effectiveTime value="20060828170821"/>
<encounterParticipant typeCode="ATND">
<templateId root="2.16.840.1.113883.10.20.6.2.2"/>
<assignedEntity>
<id extension="4" root="2.16.840.1.113883.19"/>
<code code="208D00000X" codeSystem="2.16.840.1.113883.11.19465"
codeSystemName="NUCC" displayName="General Practice"/>
<addr nullFlavor="NI"/>
<telecom nullFlavor="NI"/>
<assignedPerson>
<name>
<prefix>Dr.</prefix>
<given>Fay</given>
<family>Family</family>
</name>
</assignedPerson>
</assignedEntity>
</encounterParticipant>
</encompassingEncounter>
</componentOf>
<component>
<structuredBody>
<component>
<!--
**********************************************************************
DICOM Object Catalog Section
**********************************************************************
-->
<section classCode="DOCSECT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.1.1"/>
<code code="121181" codeSystem="1.2.840.10008.2.16.4" codeSystemName="DCM"
displayName="DICOM Object Catalog"/>
<entry>
<!--
**********************************************************************
Study
**********************************************************************
-->
<act classCode="ACT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.6"/>
<id root="1.2.840.113619.2.62.994044785528.114289542805"/>
<code code="113014" codeSystem="1.2.840.10008.2.16.4"
codeSystemName="DCM" displayName="Study"/>
<!--
*****************************************************************
Series and SopInstance UIDs removed for brevity
*****************************************************************
-->
</act>
</entry>
</section>
<!--
**********************************************************************
End of DICOM Object Catalog Section
**********************************************************************
-->
</component>
<component>
<!--
**********************************************************************
Social History Section
**********************************************************************
-->
<section>
<templateId root="2.16.840.1.113883.10.20.22.2.17" extension="2015-08-01"/>
<templateId root="2.16.840.1.113883.10.20.22.2.17"/>
<code code="29762-2" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"/>
<title>Social History</title>
<text> The patient was born female, identifes as male and is currently
undergoing gender affirming hormone therapy. <table border="1" width="100%"
cellpadding="0" cellspacing="0">
<thead>
<tr>
<th>Obs</th>
<th>Value</th>
<th>Kind</th>
<th>Jurisdiction</th>
<th>Date Acquired</th>
</tr>
</thead>
<tbody>
<tr>
<td>Gender Identity</td>
<td>Identifies as male gender</td>
<td/>
<td/>
<td/>
</tr>
<tr>
<td>Pronouns</td>
<td>He, Him, His, Himself</td>
<td/>
<td/>
<td/>
</tr>
<tr>
<td>Recorded Sex or Gender</td>
<td>Female</td>
<td>Sex Assigned at Birth</td>
<td>California</td>
<td>201201011450+0600</td>
</tr>
</tbody>
</table>
</text>
<entry>
<!-- Gender Identity -->
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.15.1" extension="2022-09-01"/>
<code code="76691-5" codeSystem="2.16.840.1.113883.6.1"
displayName="Gender Identity"/>
<statusCode code="completed"/>
<value xsi:type="CD" codeSystem="2.16.840.1.113883.6.96"
codeSystemName="SNOMED CT" code="446151000124109"
displayName="Identifies as male gender"> </value>
</observation>
</entry>
<entry>
<!-- Pronouns -->
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.15.2" extension="2022-09-01"/>
<code code="90778-2" codeSystem="2.16.840.1.113883.6.1"
displayName="Personal pronouns"/>
<statusCode code="completed"/>
<value xsi:type="CD" codeSystem="2.16.840.1.113883.6.1"
codeSystemName="LOINC" code="LA29518-0"
displayName="He, Him, His, Himself"/>
</observation>
</entry>
<entry>
<!-- Recorded Sex or Gender -->
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.15.4" extension="2022-09-01"/>
<code code="99502-7" codeSystem="2.16.840.1.113883.6.1"
displayName="Recorded sex or gender"/>
<derivationExpr>Enter whether the infant is male, female, or if the sex
of the infant is ambiguous, enter “unknown.”</derivationExpr>
<statusCode code="completed"/>
<value xsi:type="CD" code="F">
<translation code="F" codeSystem="2.16.840.1.113883.11.19756"
codeSystemName="International Civil Aviation Organization Sex or Gender"
displayName="Female"/>
</value>
<entryRelationship typeCode="COMP">
<!-- Jurisdiction -->
<observation classCode="OBS" moodCode="EVN">
<code code="77969-4" codeSystem="2.16.840.1.113883.6.1"
displayName="Jurisdiction code"/>
<statusCode code="completed"/>
<value xsi:type="CD" nullFlavor="OTH" codeSystem="NP">
<!-- This may be coded but does not have to be -->
<originalText>California</originalText>
</value>
</observation>
</entryRelationship>
<entryRelationship typeCode="COMP">
<!-- Document Type -->
<observation classCode="OBS" moodCode="EVN">
<code code="92183-3" codeSystem="2.16.840.1.113883.6.1"
displayName="Document type"/>
<statusCode code="completed"/>
<value xsi:type="CD" codeSystem="2.16.840.1.113883.6.1"
codeSystemName="LOINC" code="71230-7"
displayName="Birth Certificate"/>
</observation>
</entryRelationship>
<entryRelationship typeCode="COMP">
<!-- Date of Entry -->
<observation classCode="OBS" moodCode="EVN">
<code code="50786-3" codeSystem="2.16.840.1.113883.6.1"
displayName="Date of entry"/>
<statusCode code="completed"/>
<value xsi:type="TS" value="201201011450+0600"/>
</observation>
</entryRelationship>
</observation>
</entry>
</section>
<!--
**********************************************************************
End of Social History Section
**********************************************************************
-->
</component>
<component>
<!--
**********************************************************************
Reason for study Section
**********************************************************************
-->
<section>
<code code="121109" codeSystem="1.2.840.10008.2.16.4" codeSystemName="DCM"
displayName="Indications for Procedure"/>
<title>Indications for Procedure</title>
<text>Discordant clinical, ECG, and myocardial perfusion SPECT results</text>
</section>
<!--
**********************************************************************
End of Reason for study Section
**********************************************************************
-->
</component>
<component>
<!--
**********************************************************************
History Section
**********************************************************************
-->
<section>
<code code="11329-0" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"
displayName="History"/>
<title>History</title>
<text>
<paragraph>
<caption>History</caption>
<content ID="Fndng1">History goes here...</content>
</paragraph>
</text>
<entry>
<!-- History report element (TEXT) -->
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.12"/>
<code code="121060" codeSystem="1.2.840.10008.2.16.4"
codeSystemName="DCM" displayName="History"/>
<value xsi:type="ED"> History text </value>
</observation>
</entry>
<!--*****************************************************************************
This Substance Administration is supporting information for Sex for Clinical Use. It
is not likely to appear in a PET/CT report but is provided to illustrate the use of
the supporting reference.
*****************************************************************************-->
<entry>
<substanceAdministration classCode="SBADM" moodCode="EVN">
<!-- ** Medication Activity (V2) ** -->
<templateId root="2.16.840.1.113883.10.20.22.4.16"
extension="2014-06-09"/>
<id root="6C844C75-AA34-411C-B7BD-5E4A9F206E29"/>
<statusCode code="active"/>
<effectiveTime xsi:type="IVL_TS">
<low value="20120318"/>
</effectiveTime>
<doseQuantity value="1"/>
<consumable>
<manufacturedProduct classCode="MANU">
<!-- ** Medication information ** -->
<templateId root="2.16.840.1.113883.10.20.22.4.23"
extension="2014-06-09"/>
<id root="2a620155-9d11-439e-92b3-5d9815ff4ee8"/>
<manufacturedMaterial>
<code code="403922"
displayName="168 HR estradiol 0.00156 MG/HR Transdermal System"
codeSystem="2.16.840.1.113883.6.88"
codeSystemName="RxNorm"/>
</manufacturedMaterial>
</manufacturedProduct>
</consumable>
</substanceAdministration>
</entry>
</section>
</component>
<!--
**********************************************************************
End of History Section
**********************************************************************
-->
<!--
**********************************************************************
Imaging Procedure Description Section
**********************************************************************
-->
<component>
<section classCode="DOCSECT" moodCode="EVN">
<templateId root="1.2.840.10008.9.3"/>
<id root="1.2.840.10213.2.62.9940434234785528.11428954534542805"/>
<code code="55111-9" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC"
displayName="Current Imaging Procedure Description"/>
<title>Imaging Procedure Description</title>
<text>
<table border="1" width="100%" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td>Sex For Clinical Use</td>
<td>Female</td>
</tr>
<tr>
<td>Imaging Technique</td>
<td>The patient is a transgender male, undergoing hormonal
treatment. Based on physician instructions, affirmed gender
creatinine reference ranges were confirmed to be within
normal values prior to the administration of non-ionic
iodinated contrast agent.. CT images for attenuation
correction and anatomic localization followed by PET images
were obtained..</td>
</tr>
</tbody>
</table>
</text>
<entry>
<procedure moodCode="EVN" classCode="PROC">
<id root="1.2.840.10213.2.62.7044785528.999999999"/>
<code code="78814"
displayName="Positron emission tomography (PET) with concurrently acquired
computed tomography (CT)"
codeSystem="2.16.840.1.113883.6.12" codeSystemName="CPT4"/>
<!--*****************************************************************************
This is the first instance of Sex for Clinical Use. It is a subentry of the PET scan
procedure for which it is relevant.
*****************************************************************************-->
<entryRelationship typeCode="COMP">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.15.3"
extension="2022-09-01"/>
<code code="99501-9" codeSystem="2.16.840.1.113883.6.1"
displayName="Sex for clinical use"/>
<statusCode code="completed"/>
<value xsi:type="CD" codeSystem="2.16.840.1.113883.4.642.1.983"
codeSystemName="Sex For Clinical Use" code="female"
displayName="Female sex for clinical use"> </value>
<!--*****************************************************************************
This is reference points to supporting information for Sex for Clinical Use. It is
the basis on which the SFCU is assigned.
*****************************************************************************-->
<entryRelationship typeCode="SPRT">
<act classCode="ACT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.122"/>
<id root="6C844C75-AA34-411C-B7BD-5E4A9F206E29"/>
<code nullFlavor="OTH" codeSystem="NP"/>
<statusCode code="completed"/>
</act>
</entryRelationship>
</observation>
</entryRelationship>
</procedure>
</entry>
</section>
</component>
<!--
**********************************************************************
End of Imaging Procedure Description Section
**********************************************************************
-->
<component>
<!--
**********************************************************************
Findings Section
**********************************************************************
-->
<!--
**********************************************************************
SUV value - Radiologist determines relevant sex at time of
measurement and adds as DICOM acquisition context
**********************************************************************
-->
<section>
<templateId root="2.16.840.1.113883.10.20.6.1.2"/>
<code code="121070" codeSystem="1.2.840.10008.2.16.4" codeSystemName="DCM"
displayName="Findings"/>
<title>Findings</title>
<text>
<paragraph>
<caption>Finding</caption>
<content ID="Fndng2">Findings narritive goes here...</content>
</paragraph>
<paragraph>
<caption>Standardized uptake value</caption>
<content ID="Suv2">12g/ml{SUVlbm}</content>
</paragraph>
<paragraph>
<caption>Source of Measurement</caption>
<content ID="SrceOfMeas2">
<linkHtml
href="http://www.example.org/radiology1.2.840.113619.2.62.994044785528.114289542805/series/1.2.250.1.59.40211.789001276.14556172.67789/instances/1.2.250.1.59.40211.2678810.87991027.899772.2;contentType=application/dicom"
>Coronal</linkHtml>
</content>
</paragraph>
</text>
<entry>
<observation classCode="OBS" moodCode="EVN">
<!-- Text Observation -->
<templateId root="2.16.840.1.113883.10.20.6.2.12"/>
<code code="121071" codeSystem="1.2.840.10008.2.16.4"
codeSystemName="DCM" displayName="Finding"/>
<value xsi:type="ED">
<reference value="#Fndng2"/>
</value>
<!-- inferred from measurement -->
<entryRelationship typeCode="SPRT">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.14"/>
<code code="52988006" codeSystem="2.16.840.1.113883.6.96"
codeSystemName="SNOMED" displayName="Lesion">
<originalText>
<reference value="#Suv2"/>
</originalText>
</code>
<!-- no DICOM attribute -->
<statusCode code="completed"/>
<effectiveTime value="20060823223912"/>
<value xsi:type="PQ" value="12" unit="g/ml{SUVlbm}">
<translation code="g/ml{SUVlbm}"
codeSystem="2.16.840.1.113883.6.8" codeSystemName="UCUM"
codeSystemVersion="1.5"/>
</value>
<!--*****************************************************************************
This Substance Administration is supporting information for Sex for Clinical Use. It
is not likely to appear in a PET/CT report but is provided to illustrate the use of
the supporting reference.
*****************************************************************************--> <entryRelationship typeCode="COMP">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.15.3"
extension="2022-09-01"/>
<code code="99501-9" codeSystem="2.16.840.1.113883.6.1"
displayName="Sex for clinical use"/>
<statusCode code="completed"/>
<value xsi:type="CD"
codeSystem="2.16.840.1.113883.4.642.1.983"
codeSystemName="Sex For Clinical Use" code="male"
displayName="Male sex for clinical use"> </value>
</observation>
</entryRelationship>
<!-- inferred from image -->
<entryRelationship typeCode="SUBJ">
<observation classCode="DGIMG" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.8"/>
<!-- (0008,1155) Referenced SOP Instance UID-->
<id
root="1.2.840.113619.2.62.994044785528.20060823.200608232232322.3"/>
<!-- (0008,1150) Referenced SOP Class UID -->
<code code="1.2.840.10008.5.1.4.1.1.128"
codeSystem="1.2.840.10008.2.6.1"
codeSystemName="DCMUID"
displayName="Positron Emission Tomography Image Storage"> </code>
<text mediaType="application/dicom">
<!-- reference to PET DICOM image -->
<reference
value="http://www.example.org/radiology1.2.840.113619.2.62.994044785528.114289542805/series/1.2.250.1.59.40211.789001276.14556172.67789/instances/1.2.250.1.59.40211.2678810.87991027.899772.2;contentType=application/dicom"
/>
</text>
<effectiveTime value="20060823223232"/>
<!-- Referenced Frames -->
<entryRelationship typeCode="COMP">
<observation classCode="ROIBND" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.10"/>
<code code="121190"
codeSystem="1.2.840.10008.2.16.4"
displayName="Referenced Frames"/>
<entryRelationship typeCode="COMP">
<!-- Boundary Observation -->
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.11"/>
<code code="113036"
codeSystem="1.2.840.10008.2.16.4"
displayName="Group of Frames for Display"/>
<value xsi:type="INT" value="1"/>
</observation>
</entryRelationship>
</observation>
</entryRelationship>
<!-- Purpose of Reference -->
<entryRelationship typeCode="RSON">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.6.2.9"/>
<code code="ASSERTION"
codeSystem="2.16.840.1.113883.5.4"/>
<value xsi:type="CD" code="121112"
codeSystem="1.2.840.10008.2.16.4"
codeSystemName="DCM"
displayName="Source of Measurement">
<originalText>
<reference value="#SrceOfMeas2"/>
</originalText>
</value>
</observation>
</entryRelationship>
</observation>
</entryRelationship>
</observation>
</entryRelationship>
</observation>
</entry>
</section>
<!--
**********************************************************************
End of Findings Section
**********************************************************************
-->
</component>
<component>
<!--
**********************************************************************
Impressions Section
**********************************************************************
-->
<section>
<code code="121072" codeSystem="1.2.840.10008.2.16.4" codeSystemName="DCM"
displayName="Impressions"/>
<title>Impressions</title>
<text>
<paragraph>
<caption>Impression</caption>
<content ID="Fndng3">Impression goes here...</content>
</paragraph>
</text>
<entry>
<!-- Impression report element (TEXT) -->
<observation classCode="OBS" moodCode="EVN">
<!-- Text Observation -->
<templateId root="2.16.840.1.113883.10.20.6.2.12"/>
<code code="121073" codeSystem="1.2.840.10008.2.16.4"
codeSystemName="DCM" displayName="Impression"/>
<value xsi:type="ED">
<reference value="#Fndng3"/>
</value>
</observation>
</entry>
<entry>
<act moodCode="EVN" classCode="ACT">
<templateId root="2.16.840.1.113883.10.20.6.2.5"/>
<!-- Procedure Context template -->
<code code="78814"
displayName="Positron emission tomography (PET) with concurrently acquired computed tomography (CT)"
codeSystem="2.16.840.1.113883.6.12" codeSystemName="CPT4"/>
<!-- Note: This code is slightly different than the code used in the header documentationOf and overrides it, which is what this entry is for. -->
<effectiveTime value="20060823222400"/>
</act>
</entry>
</section>
<!--
**********************************************************************
End of Impressions Section
**********************************************************************
-->
</component>
</structuredBody>
</component>
</ClinicalDocument>