Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4

Example MolecularSequence/example (XML)

Clinical Genomics Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Patient

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

Simple sequence example (id = "example")

<?xml version="1.0" encoding="UTF-8"?>

<MolecularSequence xmlns="http://hl7.org/fhir">
    <id value="example"/> 
    <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><p> <b> Generated Narrative: MolecularSequence</b> <a name="example"> </a> </p> <div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px
       solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Resource MolecularSequence &quot;example&quot; </p> </div> <p> <b> type</b> : dna</p> <p> <b> subject</b> : <a href="patient-example.html">Patient/example</a>  &quot;Peter CHALMERS&quot;</p> <h3> Formatteds</h3> <table class="grid"><tr> <td> -</td> <td> <b> ContentType</b> </td> <td> <b> Url</b> </td> <td> <b> Title</b> </td> </tr> <tr> <td> *</td> <td> application/json</td> <td> <a href="http://grch37.rest.ensembl.org/ga4gh/variants/3:rs1333049?content-type=application/json">http://grch37.rest.ensembl.org/ga4gh/variants/3:rs1333049?content-type=application/json</a> </td> <td> GA4GH API</td> </tr> </table> </div> </text> <type value="dna"/> 
    <subject> 
        <reference value="Patient/example"/> 
    </subject> 
    <formatted> 
        <contentType value="application/json"/> 
        <url value="http://grch37.rest.ensembl.org/ga4gh/variants/3:rs1333049?content-type=application/json"/> 
        <title value="GA4GH API"/> 
    </formatted> 
</MolecularSequence> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.