CL 5.6: HL/7 variants not showing in trees, etc.

Homepage Clovertech Forums Read Only Archives Cloverleaf Cloverleaf CL 5.6: HL/7 variants not showing in trees, etc.

  • Creator
    Topic
  • #50681
    Jim Kosloskey
    Participant

    All,

    We are just beginning to work with Cloverleaf(R) 5.6.

    Here is something I have seen and I wonderdd if others have experienced the same thing and if this behavior is also true in Cloverleaf(R) 5.7.

    Essentially, if the is no fields file in the formats/hl7/n.n/yourvariant directory, then the 5.6 GUI does not show the variant in the Site Manager container HL7 tree.

    It also does not show up in the HL/7 Configurator tool variant selection.

    I do not recall, but I also think it is not referenceable when attemting to configure or re-configure an Xlate.

    In past releases the fields file was not needed if the variant had no changes to any standard fields or defined user fields.

    We have some variants that were created in 3.5 an previous version that do not have the fields file.

    This is not an issue with Cloverleaf(5.2) (they are addressable in the GUI).

    The resolution is to go to the appropriate directory an (in Unix) touch the Fields file thus creating an entry. Then the variant is visible in the GUI.

    If you do not experience this behavior in Cloverleaf(R) 5.6, please post so I can see if we have something else going on.

    If you experience this behavior in Cloverleaf(R) 5.7 – or not – please post so we can see if this appears to be intended.

    email: jim.kosloskey@jim-kosloskey.com

Viewing 10 reply threads
  • Author
    Replies
    • #67070
      John Mercogliano
      Participant

      Hi Jim,

       We just load 5.6 so I played around with this. I deleted the fields file from one of my play sites I migrated from 5.2 and the hl7 variant disappeared from the site manager as well so it appears to be the new design.  But I was not able to use the variant in a translate just by touching the file or open the variant in the gui because of a missing prologue.  What I did though which is kind of crazy that it works, after touching the file, refresh the site manager so it appears, delete the fields file, open the variant and save it.  This will create the fields file.

      One thing I also noticed is that there are indexes for the message and segment directories now but they are not created when you migrate the site to 5.6.  I hope that does not cause problems for the translation to use the variant properly or less efficiently.  

      Can someone from Healthvision explain the benefit of the index in the variant and what problems we might experience if they are not there?

      Thanks,

      John Mercogliano
      Sentara Healthcare
      Hampton Roads, VA

    • #67071
      Jim Kosloskey
      Participant

      John,

      You are correct.

      I now recall that touch alone does not work because there is no prologue.

      I simply copied another empty fields file (with a proper prologue) from another variant.

      An interesting alternative approach to getting this corrected.

      Also, should not the Cloverleaf(R) upgrade script have taken care of this??

      email: jim.kosloskey@jim-kosloskey.com

    • #67072
      John Mercogliano
      Participant

      I would have thought so, but we followed the upgrade instructions.  I will take one of our sites and go through the migration again just to make sure.

      John Mercogliano
      Sentara Healthcare
      Hampton Roads, VA

    • #67073
      Rob Abbott
      Keymaster

      You may have discovered a bug.  I will follow up.

      Rob Abbott
      Director, Product Management - Infor Cloverleaf

    • #67074
      Rob Abbott
      Keymaster

      I was able to reproduce this issue but couldn’t create a variant without a fields file through the GUI.

      Rob Abbott
      Director, Product Management - Infor Cloverleaf

    • #67075
      John Mercogliano
      Participant

      Jim,

       I reran the site promotion procedures and the index did not get created in the HL7 directory.

      Rob,

       Jim was talking about 3.5.  When I was playing around I manually deleted the field file to duplicate his situation.  

       I was also wondering what benefit the index files for the segment and message directories provided.  I was able to run messages through the hl7 and translator testing tool with and without the idx files and there didn’t seem to be a problem.  

        Is there a reason to open the variants in the qui and resave them to create the idx files?  Is this a bug in the hcirootcopy script? Should it be creating the indexes when we promote a site?

      Thanks,

      John Mercogliano
      Sentara Healthcare
      Hampton Roads, VA

    • #67076
      Jim Kosloskey
      Participant

      Rob,

      Yes some of our variants were created in 3.5 and prior.

      They have not been touched in between.

      On 5.2 there is no issue if the fields file is not there, but with 5.6 there is.

      email: jim.kosloskey@jim-kosloskey.com

    • #67077
      Phil Powell
      Participant

      We just had the same variant problem going from 5.4.1 to 5.6.  Any variant without a field file does not appear in the GUI.  I will try copying another field file for these variants.

    • #67078
      Russ Ross
      Participant

      Here is the script

      Russ Ross
      RussRoss318@gmail.com

    • #67079
      Rob Abbott
      Keymaster

      I think the best workaround for now is to copy an empty fields file (with prologue only) into the migrated variant.

      Rob Abbott
      Director, Product Management - Infor Cloverleaf

    • #67080
      Jim Kosloskey
      Participant

      Thanks Rob.

      email: jim.kosloskey@jim-kosloskey.com

Viewing 10 reply threads
  • The forum ‘Cloverleaf’ is closed to new topics and replies.

Forum Statistics

Registered Users
5,044
Forums
28
Topics
9,200
Replies
34,021
Topic Tags
267