ivci:metrics

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
ivci:metrics [2023/09/03 13:01] fkaagivci:metrics [2024/04/02 15:52] (current) fkaag
Line 3: Line 3:
  
 The metrics identified so far are that a code system should be: The metrics identified so far are that a code system should be:
-  * [[Complete]] +  * [[Complete]], that is able to represent any administered vaccine. Completeness implies also that code system is: 
-  [[Precise]] +    able to represent vaccines administered anywhere in the world. 
-  [[Informative]] +    able to represent vaccines administered anytime in the past (historical) 
-  [[Non-specific]] +    able to represent vaccines that are only partially described (non-specific) 
-  * [[Historical]] +  * [[Precise]], that is able to discriminate across different vaccines.
-  * [[Mappable]] +
-  * [[License]] +
-  * [[Maintained]] +
-  * [[Tolerant]] (inclusive of written trails+
-  * [[Inclusive]] (inclusive of digital trails)+
  
 +Adopting the NUVA ontology as the common transcription for other code systems provides further benefits that are no longer needed to embed within each code system :
 +  * The ability to correlate information bound to other code systems, be it NUVA itself (valences and target diseases), pharmaceutical codes (detailed composition, packaging), logistics codes (stocks and deliveries), or any other (electronic patient leaflet, vaccine information sheets, adverse events following immunization, etc).
 +  * The ability to transcribe to the code system used for any preexisting tool.
 +
 +Other characteristics relate more to the management of the code system:
 +  * a liberal [[license]]
 +  * a managed and efficient [[maintenance]] process
  • ivci/metrics.1693746096.txt.gz
  • Last modified: 2023/09/03 13:01
  • by fkaag