Update Bundle Type detection Rules

[ratheesh-kr]

These rules provide a structured approach to categorizing FHIR bundles based on the presence of specific resources, profiles, and coding. Here's a breakdown:

Normalized API Bundle Type Assignment Rules:

1. Rule 1: Multiple Categories in a Bundle

   • A bundle may contain multiple categories. This means a single bundle could potentially be classified as more than one category based on the presence of relevant resource types and profiles.

2. Rule 2: Screening

   • Category: Assigned if:
     • A resource of type Observation is found.
     • The code.coding.code matches any of these:
       • "96777-8", "97023-6", or "NYS-AHC-HRSN".
     • The meta.profile is:
       • http://shinny.org/us/ny/hrsn/StructureDefinition/shinny-observation-screening-response.

3. Rule 3: Assessment

   • Category: Assigned if:
     • A resource of type Condition is found.
     • The meta.profile is:
       • http://shinny.org/us/ny/hrsn/StructureDefinition/SHINNY-SDOHCC-Condition.

4. Rule 4: Referral

   • Category: Assigned if:
     • A resource of type ServiceRequest is found, and the meta.profile is:
       • http://shinny.org/us/ny/hrsn/StructureDefinition/SHINNY-SDOHServiceRequest.
     • OR
     • A resource of type Task is found, and the meta.profile is:
       • http://shinny.org/us/ny/hrsn/StructureDefinition/SHINNYSDOHTaskForReferralManagement.

Usage:

• These rules are used to help identify what category a bundle belongs to based on the resources and profiles it contains.
• If multiple resource types and profiles are found in a bundle, it may be categorized under multiple types, like Screening, Assessment, or Referral, based on the respective rules.