Health Level-7 or HL7 refers to a set of international standards for the transfer of clinical and administrative data between software applications used by various healthcare providers
I am trying to come up with a way to decode the Base64 we receive in an HL7 message into a PDF file and save it in a directory on our AIX machine. I thought I had the following working at one time but I am having issues. Has anyone done this before?
Is it possible to have a, b, c, d, e, and f as a counter instead of the counter being numeric? See below...Epic would like us to set OBX.4 using a alpha numeric combination.
I have an interface that does not send me specific ID's, so I am scanning the AIL3.2 (Text) field for certain characters. The Routing rule is getting pretty big with all the OR statements. Is there a way that I can define what I am searching for in the data lookup table, and not have to scan the whole field that it does by default? Is there a way that I can simplify this?
I started working on Ensemble this year so maybe I am not implementing the right way. I'm trying to connect a Welch Allyn monitor to TrakCare. The workflow is the following:
- User scans patient number with the monitor.
- The monitor sends a QBP_Q22 message to request patient information
- Ensemble (or TrakCare) sends back a synchronous RSP_K22 containing the patient data (name, dob, sex)
- The user checks the patient's information displayed on the monitor, takes vital signs and sends them to TrakCare (via Ensemble)
So this may sound trivial, but I'm seeing conflicting information on this topic and hoping to get clarification.
According to Enslib.HL7.Message class definition, the maxlength of RawContent is 10,000 characters. So when using encoding like UTF-8, that is 10KB. When using Unicode, that should then be 20KB.
But then also coming across some forums and documents where 32KB is maximum size before HL7 fields are truncated.
What is the sure way to determine and modify an interface's maximum supported message size?
In Ensemble, I have a HL7 message that contains several Z segments. I have created a custom schema to represent the new Z segments along with the new DocType Structure and Message Structure
How does Ensemble/Health Connect know which custom schema to use? I believe it has to be indicated in the MSH segment somewhere, but not sure where exactly that would be. Is the version simply updated with the new schema name or is there some other field?
I'm to create a HL7 business operation that uses the Enslib.Email.OutboundAdapter to create and use AttachStream() to create a file attachment of the HL7 contents, using the RawContent property of a Enslib.HL7.Message.
The class compiles okay, however when I send a message to the class I get the following error:
I've got a Service that get ACK Messages originated by another system.
I want to get the details of a Message when the ACK is CE (Failed Message).
I don't know whether this is the best approach but, at the moment, I have a DTL and I would like to search the Cache Database for a Message with the Control ID on the ACK in the MSA segment.
1. I saw there are built in DTLs “FHIR.FromSDA” and “FHIR.ToSDA” to convert SDA -> FHIR and FHIR -> SDA. Similarly Do Intersystems have DTLs for HL7 -> FHIR and FHIR -> HL7?
2. The reason why I am asking is, I see in HSLIB namespace HS->GateWay->HL7->HL7toSDA3 and HS->GateWay->SDA3->SDA3toHL7 DTLs. Like-wise I am trying to locate HL7 -> FHIR and FHIR -> HL7. Please help me to locate them
When turning on the “Archive IO” option within the business operations, it provides us the capability of seeing the input and output communication with external systems. For instance, watching the messages sent out + ACK message sent back .
Our production has got a scheduled task that runs daily (by default I guess, as many others) and is in charge of purging “Errors and log files”. And this is likely to be linked to the “Archive IO” feature, right?
Ensemble 2015. Working on an a way to send NACK'd HL7 messages to a flat file for external review/troubleshooting. (Similar to the way BadMessageHandler deals with validation errors.)
I think I have the Alert piece down, but need assistance with the exact syntax to do an SQL query in the DTL (or a custom function) to pull the HL7 message Raw Content into the Alert, based on the SessionID.
(Also, anything special to write alerts to the File Operation?)
I have created a class that extends file operation, but can't find the object that has the value for the file path. Is that object in pRequest or is there an another object I should be used to see that value?
I have been struggling and could use some help as I think I'm burnt. I am trying to change a Textual 2.5.1 OBX;5 with multiple iterations to a simple non-iterating outbound result. I have played around with $piece but can't seem to get it to work. The outcome I would like is for OBX;5 to look like this: |Positive| and currently it looks like this: |Positive~_~_~_~_~|. Any suggestions would be appreciated.
Is there a way to use a HL7 field value as part of the File Naming in the Business Operation FileOperation class. I know we can do this in a custom class, but I was wondering if it could be done the default FileOperation class?
Example:
MSH-4 contains the value 12345
We would like to name the file 12345_YYYYMMDDHHMMSS.HL7
MSH.4 value here_%Y%m%d%H%M%S.HL7
It may not be possible, but I just want to see if anyone has any information
Using the Data Transformation Builder I see the action if but in my scenario a case statement would be better. Is there anyway to do a case statement? This way I dont need to build a long if else logic.
Suppose I have an image and need to convert that image into a PDF for inclusion in an HL7.
I know that Zen Reports can display an image in a PDF but I do not want to view the image in a web page. I just need to convert the image to PDF in a Process and then include that PDF in an HL7. The workflow would be like this:
Get image -> Convert image into PDF -> Include PDF in HL7 OBX.
I know how to do the last part to include PDF in HL7 OBX. Just need ideas on the first part.
1) What's the correct way to check for an existence of a segment? So far I have been doing this by checking to see if a required field is non-null, and this seems to work but is a bit clumsy. In this case, it’s an X12 message being checked in an IF action in BPL:
I was wondering if InterSystems offers any message profiling capabilities. What I mean by "message profiling" is essentially stats or metrics gathered from a collection of data submissions of a particular type. For instance, average number of segments <XYZ> in a specific HL7 V2 message type. Or the number of sections found in a HL7 V3 CDA documents.
Curious if there is anything like this provided "out-of-box".
We are wondering where is the best place to tie the schema category for an incoming HL7 message? Should we do this within the service (via the message schema category setting) or receive everything and validate in the process (DTL) level?
We want to capture everything that will be sent to that HL7 listener service and then decide what to do with bad messages at the process layer.
Does anyone have any recommendation regarding this? Appreciate your input and decision thought process.
We have a mixture of legacy and new systems, and are grappling with the issue of moving documents between systems.
At the moment we are mostly using file drops and encoding metadata in filenames, but a new supplier (letter transcription) is going to provide a Hl7v2 feed sending MDM^T02 messages with PDF's of letters base64 encoded in the message itself.
We are thinking of asking all our suppliers to go with MDM (or ORU) for sending documents.
I'm interested in the pros and cons of the options; and if there are options I haven't thought of.
I need to process a very large Batch file which contains HL7 charges which we pull using FTP. I need to loop through the file and do some checks and then split the large Batch file in to individual messages. These individual messages then gets process through a different module to create a output batch of different format
Performing LUT table maintenance through Portal impacted Business Service HL7 message processing for one of our inbound feeds causing a message to fail. We are on Healthshare 2014.1.3. Is this a known issue, or is there a right way to modify table?
We have a big problem with spanish accent and special characters using Data Transformation (HL7 Messages).
We have some DT to transform HL7 messages to other type (OUL^R22 To OML^O21) so it copys the PID segment to the new one, but if in the PatienName field has any special character, the transformation stops and it not continues with the transformation.
For testing purposes, I would like to create an EnsLib.HL7.Message from either a %String or a file on disk and pass it into a function in a unit test (outside of an Ensemble context). EnsLib.HL7.Parser appears to do the necessary parsing, but it also sends the message via Ensemble service rather than returning it as a value. Is there a way to leverage the parsing outside of a Ensemble service? Alternatively, is there another way to create an EnsLib.HL7.Message?
I have a project to convert a JSON message with two patient identifiers into an HL7 ADT^A31. Is there any documentation or training that you would think is appropriate?
By update