Jonathan Reis

I need to set a 2nd field of a repeated field. For example, how do I set the second identifier for a patient in the PID-3 field? 

There are many ways to handle values in a repeated field. The following sets of code all set the 2 patient identifier to “12345^^^ALT”.

    // set using named fields
    CX cx = pid.PatientIdentifierList_03[2];
    cx.IDNumber_01.Value = "12345";
    cx.AssigningAuthority_04.NamespaceID_01.Value = "ALT";
    
    // set using the segment
    pid[3,2,1] = "12345";
    pid[3,2,4] = "ALT";
    
    // set using the message and a fully qualified Path
    message["PID-3[2].1"] = "12345";
    message["PID-3[2].4"] = "ALT";
    
    // set using the message with explicit SEG, FIELD, REPEAT, COMPONENT, SUBCOMPONENT
    message["PID", 1, 3, 2, 1] = "12345";
    message["PID", 1, 3, 2, 4] = "ALT";

I would like to debug the code that I have written in HL7Spy. How do I do this?

If you have Visual Studio installed, you can add Break(); to the OnStart() method of your custom code to trigger the Visual Studio debugger to launch when you push the “Run” button in the user interface.

  public override void OnStart()
  {
    this.Break();
  }

Once you are in Visual Studio you can set break-points, watch variables, etc.

Question: How do I remove the OBR segments that do not contain any corresponding OBX records

To do this you can loop through the OrderGroups in the message and remove all OBRs except the first one.

  public override void Run()
  {
    // Get an HL7 Message in parsed format
    HL7Message message = GetParsedMessage();
    foreach(OrderGroup order in message.GetOrderGroups())
    {
       int end = order.OBXs.Count == 0 ? order.OBRs.Count : order.OBRs.Count -1;
       for(int i = 0; i < end; ++i)
       {
          OBR obr = order.OBRs[i];
          message.Remove(obr);
       }
    }

    SaveMessage(message, "Modified");
  }
  

Question: How do I find all ADT messages in a tab where the date/time of the message and the discharge date of the patient is 30 days or more?

To do this you need to need to parse the PV1-45 field into an HL7DateTime and compare it to the MSH-7 date time. There is a shortcut to the MSH-7 field on the message object called MessageDateTime which can be used instead of parsing the MSH-7 field.

 public override void Run()
 {
    // Get an HL7 Message in parsed format
    HL7Message message = GetParsedMessage();

    // if the message is not an ADT, or doesn't have a PV1 segment, skip it
    if(message.MessageCode != "ADT" || message.PV1 == null)
      return;
    
    if(message.MessageDateTime == null)
      return; // if we don't have a message date/time
    
    HL7DateTime dt;
    // try to parse the HL7 DTM
    if(!HL7DateTime.TryParse(message.PV1.DischargeDateTime_45.Value, out dt))
      return; // if we can't parse it successfully, skip it

    TimeSpan delta = dt.DateTimeOffset - message.MessageDateTime.Value;
    if(delta.TotalDays >= 30)
      SaveMessage(message, "old adt"); // save the message if it is older than our OldestDate
  }