Aitem

-- jsonb_select_keys take jsonb and keys and return jsonb
-- contains only given keys
create or REPLACE function jsonb_select_keys (resource jsonb, keys text[] ) returns jsonb
as $$
select jsonb_object_agg(k, v)
from
  (select unnest(keys) k ) k ,
  lateral (select resource->k.k as v) t;
$$ LANGUAGE SQL
IMMUTABLE;

Aitem

#?(:clj
   (defonce styles (atom {})))

#?(:clj
   (defn gen-macro-css [stls]
     (->> stls
          (reduce-kv
           (fn [acc k v]
             (str acc "@import '" k "';\n"))
           "")

Aitem

Data Denormalization

Data DeNormalization

What is Data Normalization?

What about data normal forms?

• Avoid data duplication to reduce data redundancy

Aitem

WITH RECURSIVE pg_inherit(inhrelid, inhparent) AS
    (select inhrelid, inhparent
    FROM pg_inherits
    UNION
    SELECT child.inhrelid, parent.inhparent
    FROM pg_inherit child, pg_inherits parent
    WHERE child.inhparent = parent.inhrelid),
pg_inherit_short AS (SELECT * FROM pg_inherit WHERE inhparent NOT IN (SELECT inhrelid FROM pg_inherit))
SELECT table_schema
    , TABLE_NAME

Aitem

{"foo": "bar"}

Aitem

- resourceType: Patient
  id: ::uuid
  address:
  - city: Flushing
    line:
    - '144-11 SANFORD AVENUE #6K'
    state: NY
    district: QUEENS
    postalCode: '11355'
  meta:

Aitem

1. VillageCare получает данные для sandbox стенда с любого публично доступного URL, это может быть как gist или публичный фаил в S3 бакете
2. URL задается через настройку :sample-data-url
3. Формат данных- yaml. Данные представляют собой массив FHIR ресурсов в FHIR формате
4. Доступные шорткаты
   • ::uuid - генерация uuid
   • ::Observation.id - ссылка на id Observation в данном шаблоне
   • ::Observation.0.id - если ресурсв Observation несколько, то можно указать конкретный

Используемый в данный момент шаблон https://gist.github.com/Aitem/abaa4cfa20668f016f976348d7a0ce91

Aitem

#!/bin/sh


SYNTHEA_JAR="./synthea.jar"

BUNDLE_COUNT=40
BUNDLE_SIZE=25000
OUTPUT_PREFIX=/tmp/synthea
BUCKET=how-to-load

Aitem

Secret Store

Infrabox working with secrets

Infrastructure code in separate repo

• Grant access to infra repo only for CI and Administrator’s/DevOps’s team
• Provide general secrets only for CI and Administrator’s/DevOps’s team (cluster access, repo access and etc)
• Provide gpg keys only for CI and Administrator’s/DevOps’s team
• In CI pipeline

Aitem

{ns       dev
 import   #{skipper infrabox infrabox.alerts}

 cluster
 {:zen/tags   #{skipper/cluster}
  :engine     skipper/k8s
  :context    "kind-kind"}

 deploy
 {:zen/tags   #{skipper/deploy}