To represent a natural father of the fetus, the participant node shall match the production identified in Figure 10.
Figure 10 - Specification for natural father of fetus
<participant typeCode="IND">
<associatedEntity classCode="NOK">
<!-- 1..1 code indicating the relationship shall be x-fatherofbaby -->
<code code="xx-fatherofbaby" displayName="Father of Baby"
codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" />
<!-- 0..n addr elements representing the address of the participant -->
<addr/>
<!-- 0..n telecom elements representing the telcommunications addresses -->
<telecom/>
<!-- 1..1 associatedPerson relationships identifying the person -->
<associatedPerson>
<!-- 1..n names of the participant person -->
<name/>
</associatedPerson>
</associatedEntity>
</participant>
For example, a document which identifies "Mr.Charles Smith" as the natural father of the fetus within an Antepartum History and Physical document would do so as identified in Figure 11.
Figure 11 - Sample natural father of fetus data
<participant typeCode="IND">
<associatedEntity classCode="NOK">
<code code="xx-fatherofbaby" displayName="Father of Baby"
codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" />
<addr>
<streetAddressLine>18 Oak Valley Dr.</streetAddressLine>
<city>Monteagle</city>
<state>TN</state>
<postalCode>37205</postalCode>
<country>USA</country>
</addr>
<telecom value="tel:(999)555-1212" use="WP" />
<associatedPerson>
<name>
<prefix>Mr.</prefix>
<given>Charles</given>
<family>Smith</family>
</name>
</associatedPerson>
</associatedEntity>
</participant>
Overview
Content Tools