Sha256: 3f7b7bda384141953bec4449bb61f7f03c4c94a92f9e25e77a75bc46e12dd6e3

Contents?: true

Size: 1.72 KB

Versions: 103

Compression:

Stored size: 1.72 KB

Contents

-- Note that in the example of
-- greatest(count(cca_2_1_to_2_4), 1) we default to a 1 if count is 0 which you think
-- would ff
select
  modality_desc       modality,
  count(patient_id)   patient_count,
  round(avg(cca),2)   avg_cca,
  round(count(cca_2_1_to_2_4) / greatest(count(cca), 1.0) * 100.0, 2) pct_cca_2_1_to_2_4,
  round(count(pth_gt_300) / greatest(count(pth), 1.0) * 100.0, 2)         pct_pth_gt_300,
  round(count(pth_gt_800) / greatest(count(pth), 1.0) * 100.0, 2)         pct_pth_gt_800_pct,
  round(avg(phos),2)  avg_phos,
  max(phos)           max_phos,
  round(count(phos_lt_1_8)   / greatest(count(phos), 1.0) * 100.0, 2) pct_phos_lt_1_8

  from (
    select
    p.id patient_id,
    md.name modality_desc
    from patients p
    inner join modality_modalities m on m.patient_id = p.id
    inner join modality_descriptions md on m.description_id = md.id
  ) e1
  left join lateral (select result::decimal pth  from pathology_current_observations where description_code = 'PTHI'  and patient_id = e1.patient_id) e2 ON true
  left join lateral (select result::decimal phos from pathology_current_observations where description_code = 'PHOS' and patient_id = e1.patient_id) e3 ON true
  left join lateral (select result::decimal cca  from pathology_current_observations where description_code = 'CCA'  and patient_id = e1.patient_id) e4 ON true
  left join lateral (select phos phos_lt_1_8 where phos < 1.8) e5 ON true
  left join lateral (select pth pth_gt_800 where pth > 800) e6 ON true
  left join lateral (select pth pth_gt_300 where pth > 300) e7 ON true
  left join lateral (select cca cca_2_1_to_2_4 where cca between 2.1 and 2.4) e8 ON true
  where modality_desc in ('HD','PD','Transplant', 'Low Clearance')
  group by modality_desc

Version data entries

103 entries across 103 versions & 1 rubygems

Version Path
renalware-core-2.0.147 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.146 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.145 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.144 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.143 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.142 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.141 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.140 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.139 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.138 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.137 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.136 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.135 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.134 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.133 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.132 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.131 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.130 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.129 db/views/reporting_bone_audit_v01.sql
renalware-core-2.0.128 db/views/reporting_bone_audit_v01.sql