http://localhost:8080/ or https://localhost8443/
Technical Tips
This blog provides some ready-made tips, tricks, tweaks & interview questions-answers on C, C++, Perl, Shell Scripting and UNIX Commands.
Monday, June 28, 2021
Thursday, May 6, 2021
Name Interface Engines in HL7
Orion Health - Rhapsody Integration Engine
NextGen Connect - Mirth Connect
iNTERFACEWARE - Iguana
Lawson Worldwide - Lawson Cloverleaf
Corepoint Health - Corepoint Integration Engine
Intersystems - Ensemble
Thursday, March 25, 2021
What is modality in HIS-RIS?
Modality is the term used in radiology to refer the therapeutic method in which images are generated/recorded. More generally, in clinical medicine, the term modality is used for different types of procedures and therapies. Modality for radiology orders in ORM^O01 message. we are currently using the OBR-24 field as Modality for radiology orders message.
Thursday, October 11, 2018
What are the minimum segments necessary to generate an ADT message?
MSH - Message header (Required)
EVN - Event type (Required)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
EVN - Event type (Required)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
What are the minimum segments necessary to generate an ORU message?
MSH - Message header (Required)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
OBR - Observation request (Required)
OBX - Observation segment (Required, Repeatable)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
OBR - Observation request (Required)
OBX - Observation segment (Required, Repeatable)
What are the minimum segments necessary to generate an MDM message?
MSH - Message header (Required)
EVN - Event type (Required)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
TXA - Document notification segment (Required)
OBX - Observation segment (Required, Repeatable)
EVN - Event type (Required)
PID - Patient identification (Required)
PV1 - Patient visit (Required)
TXA - Document notification segment (Required)
OBX - Observation segment (Required, Repeatable)
Thursday, August 9, 2018
Get inactive RDP connections logged off
@echo off
color 0a
title Logging off Disconnected RDP(s) . . . . .
cls
::Disconnected user logoff
for /f "tokens=2 delims= " %%a in ('query user ^| findstr Disc') do for %%b in (%%a) do (echo %~n0 script is logging off session id - %%a logoff %%a)
::Active user logoff
for /f "tokens=3 delims= " %%a in ('query user ^| findstr Active') do for %%b in (%%a) do (echo %~f0 is logging off session id - %%a logoff %%a)
title Logging off RDP(s) Complete . . . . .
exit
*Note - You must have administrator privileges.
color 0a
title Logging off Disconnected RDP(s) . . . . .
cls
::Disconnected user logoff
for /f "tokens=2 delims= " %%a in ('query user ^| findstr Disc') do for %%b in (%%a) do (echo %~n0 script is logging off session id - %%a logoff %%a)
::Active user logoff
for /f "tokens=3 delims= " %%a in ('query user ^| findstr Active') do for %%b in (%%a) do (echo %~f0 is logging off session id - %%a logoff %%a)
title Logging off RDP(s) Complete . . . . .
exit
*Note - You must have administrator privileges.
Tuesday, June 6, 2017
C program that prints itself.
#include <stdio.h>
#include <conio.h>
#include <stdlib.h>
int main(int argc, char *argv[])
{
FILE *fp;
if ((fp = fopen(__FILE__, "r")) == NULL)
{
printf("Error! opening file %s\n", __FILE__);
exit(1);
}
while(!feof(fp))
{
printf("%c", fgetc(fp));
}
fclose(fp);
getch();
return 0;
}
#include <conio.h>
#include <stdlib.h>
int main(int argc, char *argv[])
{
FILE *fp;
if ((fp = fopen(__FILE__, "r")) == NULL)
{
printf("Error! opening file %s\n", __FILE__);
exit(1);
}
while(!feof(fp))
{
printf("%c", fgetc(fp));
}
fclose(fp);
getch();
return 0;
}
Sunday, June 4, 2017
Mitrh & Intersystems CacheDB Connecivity Setup
1. Copy CacheDB.jar into C:\Program Files\Mirth Connect\server-lib\database in your Mirth v3.5 installation directory.
2. Update the dbdrivers.xml file ($MIRTH_HOME/conf/dbdrivers.xml) by appending a line defining the driver class (Driver Class = com.intersys.jdbc.CacheDriver) and JDBC URL( jdbc:Cache://<host>:<port>/<namespace>)
<drivers>
<driver class="sun.jdbc.odbc.JdbcOdbcDriver" name="Sun JDBC-ODBC Bridge" template="jdbc:odbc:DSN" selectLimit="" />
<driver class="com.mysql.jdbc.Driver" name="MySQL" template="jdbc:mysql://host:port/dbname" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="oracle.jdbc.driver.OracleDriver" name="Oracle" template="jdbc:oracle:thin:@host:port:dbname" selectLimit="SELECT * FROM ? WHERE ROWNUM < 2" />
<driver class="org.postgresql.Driver" name="PostgreSQL" template="jdbc:postgresql://host:port/dbname" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="net.sourceforge.jtds.jdbc.Driver" name="SQL Server/Sybase" template="jdbc:jtds:sqlserver://host:port/dbname" selectLimit="SELECT TOP 1 * FROM ?" />
<driver class="org.sqlite.JDBC" name="SQLite" template="jdbc:sqlite:dbfile.db" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="com.intersys.jdbc.CacheDriver" name="CacheDB" template="jdbc:Cache://host:port/namespace" selectLimit="SELECT * FROM ? LIMIT 1" />
</drivers>
3. Restart mirth connecct.
Note: CacheDB.jar can be downloaded at following sites
http://www.dbschema.com/cache-jdbc-driver.html
https://www.oxygenxml.com/database_drivers.html
2. Update the dbdrivers.xml file ($MIRTH_HOME/conf/dbdrivers.xml) by appending a line defining the driver class (Driver Class = com.intersys.jdbc.CacheDriver) and JDBC URL( jdbc:Cache://<host>:<port>/<namespace>)
<drivers>
<driver class="sun.jdbc.odbc.JdbcOdbcDriver" name="Sun JDBC-ODBC Bridge" template="jdbc:odbc:DSN" selectLimit="" />
<driver class="com.mysql.jdbc.Driver" name="MySQL" template="jdbc:mysql://host:port/dbname" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="oracle.jdbc.driver.OracleDriver" name="Oracle" template="jdbc:oracle:thin:@host:port:dbname" selectLimit="SELECT * FROM ? WHERE ROWNUM < 2" />
<driver class="org.postgresql.Driver" name="PostgreSQL" template="jdbc:postgresql://host:port/dbname" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="net.sourceforge.jtds.jdbc.Driver" name="SQL Server/Sybase" template="jdbc:jtds:sqlserver://host:port/dbname" selectLimit="SELECT TOP 1 * FROM ?" />
<driver class="org.sqlite.JDBC" name="SQLite" template="jdbc:sqlite:dbfile.db" selectLimit="SELECT * FROM ? LIMIT 1" />
<driver class="com.intersys.jdbc.CacheDriver" name="CacheDB" template="jdbc:Cache://host:port/namespace" selectLimit="SELECT * FROM ? LIMIT 1" />
</drivers>
3. Restart mirth connecct.
Note: CacheDB.jar can be downloaded at following sites
http://www.dbschema.com/cache-jdbc-driver.html
https://www.oxygenxml.com/database_drivers.html
Wednesday, May 31, 2017
What are the differences between a v2.x and v3 message in HL7?
The key differences between a v2.x and v3 message are as follows:
v2.x was primarily meant for clinical communications - medical orders, patient registration etc. whereas v3.x has additional features for use by informaticists and for government reporting requirements.
v2.x was a custom format (barebones text - all coded and separated by a pipe with headers and multiple segments etc.) whereas an HL7 v3.0 message is an XML format - very verbose and detailed.
v2.x was primarily meant for clinical communications - medical orders, patient registration etc. whereas v3.x has additional features for use by informaticists and for government reporting requirements.
v2.x was a custom format (barebones text - all coded and separated by a pipe with headers and multiple segments etc.) whereas an HL7 v3.0 message is an XML format - very verbose and detailed.
Subscribe to:
Posts
(
Atom
)