error building api using gpmr
tman26
#1 Posted : Thursday, September 19, 2013 1:46:26 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 9/19/2013(UTC)
Posts: 1
Points: 3

Thanks: 0 times
Was thanked: 0 time(s) in 0 post(s)
Hi,

I am considering using Everest to handle HL7 v3 messages and have downloaded the SDK and installed the Everest applications locally. I would like to accept and interrogate an incoming referral message. Am I correct in understanding that I must have the MIF files from HL7.org and run them through the gpmr console application to generate the appropriate classes (for a referral) in an API in order to accomplish my goal? I have a rim0241a zip which contains a mif and two coremif files. Running gpmr from a command line throws the following error:

command (template from another post in the forum):
C:\Program Files (x86)\Mohawk College\Everest>gpmr --renderer=RIMBA_CS -c -o C:\
temp\mif --rimbapi-gen-vocab=true --rimbapi-target-ns=MARC.Everest.
RMIM.UV.CDAr2 --optimize=true --combine=true C:\temp\mif\*.*mif --r
imbapi-compile=true --rimabapi-dllonly=true

error:
-- FATAL --

Can't load MIF file 'C:\temp\mif\DEFN=UV=RIM=0241.coremif' into rep
ository
Pipeline took 00:00:03.6922112 to finish execution
-- FATAL --

The execution of the pipeline has failed. No processing can continue

-- FATAL --

Pipeline Execution Failed

Operation completed, following messages were generated:
debug -> 33
information -> 6
warn1 -> 1
fatal -> 3

Thanks in advance
justin.fyfe1
#2 Posted : Thursday, September 19, 2013 4:29:53 PM(UTC)

Rank: Administration

Medals: Mobile Tech Grasshopper: Mobile Tech GrasshopperHealth Informatics MVP

Groups: Registered, Administrators
Joined: 7/22/2010(UTC)
Posts: 96
Points: 297
Man
Location: Hamilton, ON

Thanks: 2 times
Was thanked: 17 time(s) in 17 post(s)
Hello,

Thanks for your interest in using Everest.

Everest is bundled with several pre-compiled libraries for pan-Canadian messaging, CDA, NE2008 and NE2010. You can use the DLL files if you want to just implement a model from those normative editions. If you want to implement HL7 using another version of the HL7v3 standard you're correct that you'll need to compile the models.

The package you have downloaded is for the RIM only which, while technically v3, is the abstract model upon which most jurisdictions will restrict RMIMs for referrals. Your jurisdiction may have published a more complete standard set of MIFs (in Canada our spec is about 400+ files). That being said, if you'd like to compile the RIM from MIF you can do so however I've only tried it with MIF 2.1.4 (2.4 is published with MIF 2.1.6).

There is an XSLT that GPMR applies prior to loading (located in "xsl\2.1.6.xslt" of the install directory) and you can get it to load the MIF files by adding this xsl template:

Code:
<xsl:template match="mif:property"></xsl:template>


So that it ignores the "property" element which is causing the issue. I'll file this bug and release a patch in a few days when we're done testing a few other fixes. You can also download the new XSLT from our SVN site: https://fisheye.marc-hi.ca/svn/Everest/branches/1.2/gpmr/XSL/2.1.6.xslt and replace the installed file.

Cheers
-Justin
justin.fyfe1
#3 Posted : Thursday, September 19, 2013 4:31:35 PM(UTC)

Rank: Administration

Medals: Mobile Tech Grasshopper: Mobile Tech GrasshopperHealth Informatics MVP

Groups: Registered, Administrators
Joined: 7/22/2010(UTC)
Posts: 96
Points: 297
Man
Location: Hamilton, ON

Thanks: 2 times
Was thanked: 17 time(s) in 17 post(s)
After applying this you may want to add "--quirks" to the parameter list so that the compilation process ignores the fact there are no RMIMs
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

SoClean Theme By Jaben Cargman (Tiny Gecko)
Powered by YAF 1.9.4 | YAF © 2003-2010, Yet Another Forum.NET
This page was generated in 0.096 seconds.