Skip to content

In Helix labs, OBR-2 and OBC-2 don't match #144

@stefpiatek

Description

@stefpiatek

Definition of Done / Acceptance Criteria

  • Helix lab messages are processed correctly, without errors.

Testing

No response

Documentation

No response

Dependencies

No response

Details and Comments

message type: ORM^O01
sender_application: WinPath

Now getting an error where ORC-2 and OBR-2 don't match, expect this is to do with Helix

Redacted exception with correct unid:

u.a.u.r.i.datasources.ids.IdsOperations  : Skipping unid 389985447 (class class ca.uhn.hl7v2.model.v26.message.ORM_O01)
uk.ac.ucl.rits.inform.datasources.ids.exceptions.Hl7InconsistencyException: ORC-2 30U111111 does not match OBR-2 22222222

I assume that ORC-2 and OBR-2 mismatching is okay, as they look like a UCLH barcode and a Helix internal ID

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions