-
Update: In a regular SEC meeting a couple of minutes ago, we agreed to use REGISTRY as a working hypothesis regarding name and listen in to other name suggestions and feedback here in Discourse until next meting in another two weeks.
-
@thomas.beale the concrete ENTITY subclasses seem useful. Could we add a concrete GENERIC_ENTITY subclass and perhaps move the optional type_uri there? (The type of other concrete entity children would already be given by the class names and corresponding documentation.) The GENERIC_ENTITY could be used for purposes analogue to GENERIC_ENTRY, e.g. for imports from external systems or as interim solution while considering/testing new design patterns not yet catered for (or not considered generally reusable enough) in existing ENTITY sub-classes.
-
We are workning with precision medicine and modeling e.g. some context around genomic testing. There is quality-report data and other information we’d like to store regarding specific batch runs in genomic sequencers and similar equipment. A batch can contain several samples for several patients. (We want traceability, but do not want to copy all that data into each patient’s own EHR, In individual EHRs we just want something identifying the batch and some sample specific results and quality data). Is there a suitable construct in task planning or an ontological entity that could be used as basis for modeling/archetyping data about multi-patient batch runs by a test instrument/device? Or does it fit somewhere in task planning?