IntelliSense IN SQL SERVER MANAGEMENT STUDIO

SQL Prompt : Write, format, and refactor SQL effortlessly

IN SQL SERVER MANAGEMENT STUDIO AND VISUAL STUDIO

• IntelliSense-style code completion
• Customizable code formatting
• Code snippet library
• Refactor SQL code
• SSMS tab history
• New: SSMS tab coloring
• 

Writing SQL code by hand, even with IntelliSense, is frankly pretty dull

So we made SQL Prompt, which isn’t

An add-in for SQL Server Management Studio and Visual Studio, SQL Prompt strips away the repetition of coding.

As well as autocompleting your code, SQL Prompt takes care of formatting, object renaming, and other distractions, so you can concentrate on how the code actually works.

Whether you need to write, refactor, or explore database code, find out how SQL Prompt makes it effortless by trying it free for 28 days.

Reference :

http://www.red-gate.com/products/sql-development/sql-prompt/

HL7 PID (Patient Identification) Segment

PID: Patient identification segment

The PID segment is used by all applications as the primary means of communicating patient identification information. This segment contains permanent patient identifying and demographic information that, for the most part, is not likely to change frequently.


The HL7 PID segment is found in every type of ADT message (i.e. ADT-A01, ADT-A08, etc.) and contains 30 different fields with values ranging from patient ID number, to patient sex, to address, to marital status, to citizenship. The PID segment provides important identification information about the patient and, in fact, is used as the primary means of communicating the identifying and demographic information about a patient between systems. Due to the nature of the information found in the PID segment, it is unlikely to change frequently. 

SEQ	LENGTH	DataType	Optional/Required	RPT / #	TBL #	NAME
PID.1	4	SI	O	1		Set ID - PID
PID.2	20	CX	B	1		Patient ID
PID.3	20	CX	R	*		Patient Identifier List
PID.4	20	CX	B	*		Alternate Patient ID - PID
PID.5	48	XPN	R	*		Patient Name
PID.6	48	XPN	O	*		Mother s Maiden Name
PID.7	26	TS	O	1		Date/Time Of Birth
PID.8	1	IS	O	1	0001	Sex
PID.9	48	XPN	O	*		Patient Alias
PID.10	80	CE	O	*		Race
PID.11	106	XAD	O	*		Patient Address
PID.12	4	IS	B	1	0289	County Code
PID.13	40	XTN	O	*		Phone Number - Home
PID.14	40	XTN	O	*		Phone Number - Business
PID.15	60	CE	O	1		Primary Language
PID.16	80	CE	O	1		Marital Status
PID.17	80	CE	O	1		Religion
PID.18	20	CX	O	1		Patient Account Number
PID.19	16	ST	B	1		SSN Number - Patient
PID.20	25	DLN	O	1		Driver's License Number - Patient
PID.21	20	CX	O	*		Mother's Identifier
PID.22	80	CE	O	*		Ethnic Group
PID.23	60	ST	O	1		Birth Place
PID.24	1	ID	O	1	0136	Multiple Birth Indicator
PID.25	2	NM	O	1		Birth Order
PID.26	80	CE	O	*		Citizenship
PID.27	60	CE	O	1		Veterans Military Status
PID.28	80	CE	O	1		Nationality
PID.29	26	TS	O	1		Patient Death Date and Time
PID.30	1	ID	O	1	0136	Patient Death Indicator

Reference:
 http://www.hl7soup.com/Features.html

HL7 Soup Software help you to Edit and View HL7 PID Patient Identification Segment 

Design UML Diagram online without Installing the Tool

https://www.draw.io/

Health Language 7 (HL7) Convert HL7 Code to XML

HL7 (Health Language 7) is a "standard" utilized by the healthcare industry to enable messaging between applications i.e. EHR to PMS (practice management system) for example. It is managed and maintained by Health Level Seven International (HL7) which is a not-for-profit, ANSI-accredited standards developing organization. The HL7 standard is often jokingly referred to as the “non-standard standard.” This is not very fair but it does reflect the fact that almost every hospital, clinic, imaging center, lab, and care facility is “special” in terms of how it implements HL7 (really?, why?). The reason is primarily because there is no such thing as a standard business or clinical process for interacting with patients, clinical data, or related personnel.

The HL7 messaging protocol was designed to facilitate high volumes of pre-defined data to be shared across many applications reliably. The protocol selected to make this happen was a traditional file transfer or a TCP/IP socket in both a real-time and batched fashion. HL7 v2.x message structure is complex, flat, and delimited. HL7 has obviously evolved over time. The current version of HL7 is v3.0. However, older versions exist and make up the bulk of the standard used today primarily because of the large number customization that have been done to each HL7 message.

Reference:
https://catalyze.io/learn/hl7-101-a-primer ***

http://www.interfaceware.com/manual/xml.html

http://www.christian-sonek.de/hl7/hl7server_de

http://www.interfaceware.com/manual/full_tree.html **