resources-normalized

Description

After the Normalization service performs its tasks against the acquired FHIR resources, the service will produce a ResourcesNormalized event. Depending on configuration and capacity, the cached resources will either be stored in Redis or Azure Blob Storage. The value segment of the event contains the cache key where the patient resources are located. A single ResourcesNormalized event should be produced per correlation Id and query type (initial, supplemental)

Event Information

Value

QueryType: Which query phase the acquired resources were for. The value will either be Initial or Supplemental.

CacheType: Describes the cache destination of the acquired FHIR resources. Currently, Link Cloud supports either Redis or ABS.

CacheKey: Will be the cache destination for all acquired FHIR resources: - Redis: For Redis, the cache key value will represent the hash key name of the Redis. - ABS: For ABS, each cache key will represent the directory where all acquired FHIR resources for the patient are located.

Relationships

flowchart LR
nresources_normalized_28215193["Event: Resources Normalized"]
  nNormalizationService_4A3628B6["Service: NormalizationService"] -->|produces| nresources_normalized_28215193
  nresources_normalized_28215193 -->|consumed by| nMeasureEvalService_67DBAC12["Service: MeasureEvalService"]
  subgraph nCompliance_DBAE25D_domain["Domain: Compliance"]
    nresources_normalized_28215193
  end
  subgraph nReport_4D4FBBDA_domain["Domain: Report"]
    nMeasureEvalService_67DBAC12
    nNormalizationService_4A3628B6
  end