Comment:

The value set for DiagnosticReport.code is intriguing. I understand the desire to express methodologic information and organize a genetic test discretely. This usage of DiagnosticReport.code is an important key to understanding how mcode is trying to organize genetic information. From this use I would say that mCODE Is trying to use their two variant profiles to capture both the observation and test methodology. I would like to invite mcode team to describe this usage at a CG FHIR-sub group meeting. It is an important divergence. The CG WG uses our artifacts to try to state explicitly (computably) important test methodology. The use of GTR moves this methodological information into a database. Such a move reduces the number of fields needed in the message model (FHIR), but places a dependency on the database (GTR). EMERGE is struggling with related problems. Despite the dependency on GTR there is an attractive simplicity. But to be in better alignment with the CG WG IG, consider creating a slice on code called 'GeneticTestId' or something similar. The goal would be to make the element's use more explicit for developers.

Summary:

consider creating a slice on code or an extension called 'GeneticTestId' or something similar