In the current spec, I opted to follow a FHIR Coding-like approach for representing coded values in the data (as opposed to a simpler but less informative 'code' approach, or a more complex and likely overkill 'CodableConcept' approach). See full description of our approach in the Information Model doc here.
This Coding data type is similar in content/complexity to the OntologyClass type/class that we (e.g. in the Phenopackets spec here) and others have used to capture coded values in a way that includes additional metadata such as the human-readable label and source ontology.
We should discuss if this is the right level given the use cases and context of implementation for the contribution model.
In the current spec, I opted to follow a FHIR Coding-like approach for representing coded values in the data (as opposed to a simpler but less informative 'code' approach, or a more complex and likely overkill 'CodableConcept' approach). See full description of our approach in the Information Model doc here.
This Coding data type is similar in content/complexity to the OntologyClass type/class that we (e.g. in the Phenopackets spec here) and others have used to capture coded values in a way that includes additional metadata such as the human-readable label and source ontology.
We should discuss if this is the right level given the use cases and context of implementation for the contribution model.