<commit_before>#Interleave

* An application for managing longitudinal clinical research databases and registries that is based on the OHDSI/OMOP Common Data Model (CDM).
* The application layers the following features on top of the CDM.
** Multitenant housing of registires.
** Enrichment of the CDM to include protected health imformation fields.
** Registry-scoped configuration of datapoints and the relationshpe between datapoints.  Dynamic diplay of datapoints per peson per registry.
** Datapoint restriction of the list possible values of CDM concept ID values.
** Provenance tracking per CDM entity back to source system rows.
** Support for the incremental load of data from and outside source sytem.
** A user interface to allow for the creation 'ex nihlo' of any CDM entity.
** A user interface to allow for the overide of any externally imported CDM entity.


* Why did the name 'Interleve'?
* Because clinical reserach databases and registries requrie the 'inteleaving' of manually created data and data automtacially pulled from external systems (EHRs, billing/claims systems)?  Data must be stacked on top of each other and the provenance of each entity must be tracked.

* Setup
** Open a psql command prompt
** CREATE DATABASE interleave_development;
** CREATE USER interleave_development WITH CREATEDB PASSWORD '<PASSWORD>';
** ALTER DATABASE interleave_development OWNER TO interleave_development;
** ALTER USER interleave_development SUPERUSER;
** CREATE DATABASE interleave_test;
** CREATE USER interleave_test WITH CREATEDB PASSWORD '<PASSWORD>';
** ALTER DATABASE interleave_test OWNER TO interleave_test;
** ALTER USER interleave_test SUPERUSER;
** bundle exec rake db:migrate
** bundle exec rake setup:interleave_registries<commit_msg>Some fixes to the README<commit_after>#Interleave

* An application for managing longitudinal clinical research databases and registries that is based on the OHDSI/OMOP Common Data Model (CDM).
* The application layers the following features on top of the CDM.
 * Multitenant housing of registires.
 * Enrichment of the CDM to include protected health imformation fields.
 * Registry-scoped configuration of datapoints and the relationshpe between datapoints.  Dynamic diplay of datapoints per peson per registry.
 * Datapoint restriction of the list of possible values of CDM concept ID values.
 * Provenance tracking per CDM entity back to source system rows.
 * Support for the incremental load of data from an outside source sytem.
 * A user interface to allow for the creation 'ex nihlo' of any CDM entity.
 * A user interface to allow for the overide of any externally imported CDM entity.


* Why the name 'Interleve'?
* Because clinical reserach databases and registries requrie the 'inteleaving' of manually created data and data automatically pulled from external systems (EHRs, billing/claims systems...)?  Data must be stacked on top of each other and the provenance of each entity must be tracked.  The data must be interleaved.

* Setup
 * Open a psql command prompt
 * CREATE DATABASE interleave_development;
 * CREATE USER interleave_development WITH CREATEDB PASSWORD '<PASSWORD>';
 * ALTER DATABASE interleave_development OWNER TO interleave_development;
 * ALTER USER interleave_development SUPERUSER;
 * CREATE DATABASE interleave_test;
 * CREATE USER interleave_test WITH CREATEDB PASSWORD '<PASSWORD>';
 * ALTER DATABASE interleave_test OWNER TO interleave_test;
 * ALTER USER interleave_test SUPERUSER;
 * bundle exec rake db:migrate
 * bundle exec rake setup:interleave_registries
{'fraction_non_alphanumeric': 0.04796633941093969, 'fraction_numerical': 0.0, 'mean_word_length': 5.234265734265734, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3884662', 'n_tokens_mistral': 1004, 'n_tokens_neox': 931, 'n_words': 458}