Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Component/s: Server
    • Labels:
    • Environment:
      Windows + JDK 1.6

      Description

      The HPRIM datatype is a french variant of HL7 piped content.

      It can be handled by the HL7 v2.x datatype, but there is no strict conformance on HPRIM specific rules in HL7 v2.x datatype.
      This patch adds the support of strict HPRIM format for the ORU messages (labs results and demands).
      The library used to read Hprim is libHprim, which is lgpl.
      The others libraries used are :

      • antlr-2.7.7.jar
      • antlr-runtime-3.4.jar
      • hamcrest-core-1.1.jar
      • serializer-2.7.1.jar
      • stringtemplate-3.2.1.jar
      • xalan-2.7.1.jar
      • xml-apis-1.3.04.jar
        which lie under their own licences.
      1. mirth-client-patch.txt
        3 kB
        delabre JP
      2. mirth-client-patch-r6297.txt
        3 kB
        delabre JP
      3. mirth-server-patch.txt
        56 kB
        delabre JP
      4. mirth-server-patch-r6304.txt
        65 kB
        delabre JP

        Activity

        Hide
        delabre JP added a comment -

        Patch for hprim oru support on client and server

        Show
        delabre JP added a comment - Patch for hprim oru support on client and server
        Hide
        Nick Rupley added a comment -

        I've worked with HPRIM before... currently the easiest way to handle them is with Delimited Text. This would be rather easy to add as a separate data type plugin now in 3.0 though.

        Show
        Nick Rupley added a comment - I've worked with HPRIM before... currently the easiest way to handle them is with Delimited Text. This would be rather easy to add as a separate data type plugin now in 3.0 though.
        Hide
        delabre JP added a comment -

        This patch is exactly a separate data type plugin specifically designed for the trunk version of Mirth in cvs.

        In fact, there are 3 kinds of HPRIM :

        • HPRIM Medecin, which is a loosy format to transfer labs results. This format can be readed as a delimited text.
        • HPRIM Xml, which is just Xml and can be handled as any Xml.
        • HPRIM Sante v2.x, (based upon ASTM E 1238 - DRAFT REVISION 4.2), which is widely used in France, and defines 7 kinds of messages :
        • ORM (exam prescription)
        • ORA (exam prescription with administrative datas)
        • ORU (exam results)
        • ADM (administrative datas)
        • FAC (facturation datas)
        • REG (payments datas)
        • ERR (error message)

        Hprim sante v2.x can be readed as an hl7 v2.x datatype in mirth V3b, but it can't validate that the message meets the HPRIM specifications and it accepts badly formed messages.
        This patch enables parsing and validation of HPRIM Sante 2.x ORU message types in the same pass.
        It uses an EBNF grammar in order to enable full validation with co-occurence testings contrary to xml schema validations which lack some kinds of testings.

        Show
        delabre JP added a comment - This patch is exactly a separate data type plugin specifically designed for the trunk version of Mirth in cvs. In fact, there are 3 kinds of HPRIM : HPRIM Medecin, which is a loosy format to transfer labs results. This format can be readed as a delimited text. HPRIM Xml, which is just Xml and can be handled as any Xml. HPRIM Sante v2.x, (based upon ASTM E 1238 - DRAFT REVISION 4.2), which is widely used in France, and defines 7 kinds of messages : ORM (exam prescription) ORA (exam prescription with administrative datas) ORU (exam results) ADM (administrative datas) FAC (facturation datas) REG (payments datas) ERR (error message) Hprim sante v2.x can be readed as an hl7 v2.x datatype in mirth V3b, but it can't validate that the message meets the HPRIM specifications and it accepts badly formed messages. This patch enables parsing and validation of HPRIM Sante 2.x ORU message types in the same pass. It uses an EBNF grammar in order to enable full validation with co-occurence testings contrary to xml schema validations which lack some kinds of testings.
        Hide
        Wayne Huang added a comment -

        The state of the data type plugin architecture is still in flux, so we will revisit this when version 3 is officially released. By all means feel free to update your patch for new beta and RC releases.

        Show
        Wayne Huang added a comment - The state of the data type plugin architecture is still in flux, so we will revisit this when version 3 is officially released. By all means feel free to update your patch for new beta and RC releases.
        Hide
        delabre JP added a comment - - edited

        Uses an xml structure like HL7v2.x
        Integrates with libhprim 3.2.0 and reads any Hprim Sante 2.x messages except ERR messages

        Show
        delabre JP added a comment - - edited Uses an xml structure like HL7v2.x Integrates with libhprim 3.2.0 and reads any Hprim Sante 2.x messages except ERR messages

          People

          • Assignee:
            Unassigned
            Reporter:
            delabre JP
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Development