bulk-submit does not report unexpected resource types in status errors

[johngrimes]

Summary

Pathling completes a bulk-submit import even when a bulk file contains a resource type that does not match the manifest output.type, and the status manifest reports no errors.

Environment

• Server: https://demo.pathling.app/fhir (pathling-demo)
• Spec: https://hackmd.io/NlrhAtppTIWGfHaJDfhzpQ.md

Steps to Reproduce

1. Create submission to Pathling demo and submit manifest https://bulk-submit-provider.smarthealthit.org/api/manifests/4.
2. Mark submission complete.

Observed

• The file referenced by the manifest contains an unexpected resource type:
  • curl -sS https://bulk-submit-provider-5dcd741b9746.herokuapp.com/exports/4/AllergyIntolerance.ndjson | jq -r .resourceType | sort | uniq -c
  • Output: 2 AllergyIntolerance, 1 Patient
  • Example line: line 3 has "resourceType":"Patient" in a file declared as AllergyIntolerance.
• Pathling logs show import completed successfully and the status manifest has error: [].
• Submission ID: e4ece52e-321d-4f3d-a5bb-374bd5dd3b04
• Job ID: 2c8eb242-b4e3-4b3e-a23b-71202fea798c

Expected

Unexpected resource types should be surfaced in the status manifest error section as OperationOutcome entries referencing the originating manifestUrl.