You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although it's possible now to compile custom HL7 structures at runtime, creating these custom structures is still unintuitive.
I wonder if a DSL like the one used for HL7 validation could help, e.g. compare the custom definitions in modules-hl7 (below package org.openehealth.ipf.modules.hl7.parser.groovytest.hl7v2.def.v25, way more than 100 LOC) with:
Although it's possible now to compile custom HL7 structures at runtime, creating these custom structures is still unintuitive.
I wonder if a DSL like the one used for HL7 validation could help, e.g. compare the custom definitions in modules-hl7 (below package org.openehealth.ipf.modules.hl7.parser.groovytest.hl7v2.def.v25, way more than 100 LOC) with:
forVersion('2.5')
.message('MDM', 'T01 T02')
.addSegment('ZBE')
.newSegment('ZBE')
.addRepeatingType('MovementId', EI, 999)
.addType('StartMovementDateTime', TS, 26)
.addType('EndMovementDateTime', TS, 26)
.addType('Action', ST, 10)
The text was updated successfully, but these errors were encountered: