A complete example in Java: Oncology

This example shows how to create the Phenopacket that was explained here.


We create an object to represent the proband as an Individual.

private Individual subject() {
      return Individual.newBuilder()
              .setDatasetId("urology cohort")


There are two categories of phenotypes that can be of interest with cancer data. Firstly, there are constitutional phenotypes such as weight loss that are related to the disease of cancer. Second, the tumor, and is applicable metasases, each have their own phenotypes including histology and grade. The Phenopacket standard represents constitutional Phenotypes using a list of rstphenotype elements, and represents phenotypes of the tumor and metastases in Biosample elements. In the present case, the patient was found to have hematuria and severe dysuria, which are coded as follows.

PhenotypicFeature hematuria = PhenotypicFeature.newBuilder().
PhenotypicFeature dsyuria = PhenotypicFeature.newBuilder().


We use three HtsFile objects in this Phenopacket. One represents the pair normal germline whole-genome sequence (WGS) VCF file, one one each represents somatic WGS data from the bladder carcinoma specimen and from the metastasis specimen. All three packets are created analogously. Here is the code for the bladder carcinoma WGS file.

public HtsFile createSomaticHtsFile() {
    // first create a File
    // We are imagining there is a reference to a VCF file for a normal germline genome seqeunce
    String path = "/data/genomes/urothelial_ca_wgs.vcf.gz";
    String description = "Urothelial carcinoma sample";
    File file = File.newBuilder().setPath(path).setDescription(description).build();
    // Now create an HtsFile object
    return HtsFile.newBuilder().


This example Phenopacket contains five Biosample objects, each of which is constructed using a function similar to the following code, which represents the bladder carcinoma specimen.

private Biosample bladderBiosample() {
      String sampleId = "sample1";
      // left wall of urinary bladder
      OntologyClass sampleType = ontologyClass("UBERON_0001256", "wall of urinary bladder");
      Biosample.Builder biosampleBuilder = biosampleBuilder(patientId, sampleId, this.ageAtBiopsy, sampleType);
      // also want to mention the procedure, Prostatocystectomy (NCIT:C94464)
      //Infiltrating Urothelial Carcinoma (Code C39853)
      OntologyClass infiltratingUrothelialCarcinoma = ontologyClass("NCIT:C39853", "Infiltrating Urothelial Carcinoma");
      // A malignant tumor at the original site of growth
      OntologyClass primary = ontologyClass("NCIT:C84509", "Primary Malignant Neoplasm");
      biosampleBuilder.setProcedure(Procedure.newBuilder().setCode(ontologyClass("NCIT:C15189", "Biopsy")).build());
      return biosampleBuilder.build();

Normal findings

In the biosamples for the left and right ureter, normal findings were obtains. This is represented by an OntologyClass for normal (negative) findings. We recommend using the following term from NCIT.

OntologyClass normalFinding = ontologyClass("NCIT:C38757", "Negative Finding");

This is used to create a “normal” Biosample object as follows.

private Biosample leftUreterBiosample() {
     String sampleId = "sample3";
     OntologyClass sampleType = ontologyClass("UBERON:0001223", "left ureter");
     Biosample.Builder biosampleBuilder = biosampleBuilder(patientId, sampleId, this.ageAtBiopsy, sampleType);
     OntologyClass normalFinding = ontologyClass("NCIT:C38757", "Negative Finding");
     biosampleBuilder.setProcedure(Procedure.newBuilder().setCode(ontologyClass("NCIT:C15189", "Biopsy")).build());
     return biosampleBuilder.build();


We recommend using the National Cancer Institute’s Thesaurus codes to represent cancer diagnoses, but any relevant ontology term can be used. The following Java code creates a Disease object.

 private Disease infiltratingUrothelialCarcinoma() {
     return Disease.newBuilder()
         .setTerm(ontologyClass("NCIT:C39853", "Infiltrating Urothelial Carcinoma"))
         // Disease stage here is calculated based on the TMN findings
         .addDiseaseStage(ontologyClass("NCIT:C27971", "Stage IV"))
         // The tumor was staged as pT2b, meaning infiltration into the outer muscle layer of the bladder wall
         // pT2b Stage Finding (Code C48766)
         .addTnmFinding(ontologyClass("NCIT:C48766", "pT2b Stage Finding"))
         // pN2 Stage Finding (Code C48750)
         // cancer has spread to 2 or more lymph nodes in the true pelvis (N2)
         .addTnmFinding(ontologyClass("NCIT:C48750", "pN2 Stage Finding"))
         // M1 Stage Finding
         // the tumour has spread from the original site (Metastatic Neoplasm in lymph node - sample5)
         .addTnmFinding(ontologyClass("NCIT:C48700", "M1 Stage Finding"))


The MetaData section MUST indicate all ontologies used in the phenopacket together with their versions. This Phenopacket used HPO, UBERON, and NCIT. We additionally use a Timestamp (Java) object to indicate the current time (at which we are creating this Phenopacket).

private MetaData buildMetaData() {
    long millis  = System.currentTimeMillis();
    Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
            .setNanos((int) ((millis % 1000) * 1000000)).build();
    return MetaData.newBuilder()
                    .setName("human phenotype ontology")
                    .setName("uber anatomy ontology")
                    .setName("NCI Thesaurus OBO Edition")
            .setCreatedBy("Peter R")
            .setSubmittedBy("Peter R")
                    .setDescription("Urothelial neoplasms in pediatric and young adult patients: A large single-center series")

Putting it all together

Finally, we utilize a Phenopacket builder to generate the complete Phenopacket object.

Phenopacket phenopacket = Phenopacket.newBuilder()
    .setId("example case")

Output of data

There are many ways of outputting the Phenopacket in JSON format. See Exporting and Importing Phenopackets for details. The following line will output the entire Phenopacket to STDOUT including empty fields.