ga4gh / va-spec

An information model for representing variant annotations.
Apache License 2.0
17 stars 4 forks source link

Value Set definitions for v0 release #56

Open mbrush opened 4 years ago

mbrush commented 4 years ago

It will be important to standardize data for certain attributes by binding them to value sets. We identified a handful of places where we considered this (see below), and agreed on terms to be included in a handful of high priority value sets - but we have yet to document these formally. We need to decide if/where/how we will provide recommended value sets in the v0 VA-Spec release, and document these value sets in a more formal way.

Proposal: Document high value/priority value sets informally for v0, but do not require use of these in v0 release

Next Steps: Create central documentation of value sets in scope for v0, and decide on representational format (in spreadsheet? text/yaml file? describe using FHIR or SEPIO value set models?)

Value Sets relevant for v0 statements:

mbrush commented 4 years ago

Proposal: For v0 release - informally describe value sets in our modeling spreadsheet.

For v1, define a formal representation as part of the spec. Some examples to inform this work may include the FHIR Value Set resource definition, and the SEPIO value set model.