Skip to content

JSON within QIE

JSON stands for JavaScript Object Notation. JSON is pronounced (JAY-sun), although another popular pronunciation is (JAY-sawn). JSON is referred to as a lightweight data-interchange format. QIE can receive or send JSON messages and use a JSON object to store data for access during message processing.

Although its name implies it is JavaScript specific, JSON is language independent and is used in many different languages. JSON is similar to associative arrays, hash tables or keyed lists. In non-programming terms, it can be thought of as a spreadsheet with two columns. The first column is the key and the second is the value. For example, think of a spreadsheet with your bills. In column "A" you enter the name (key) of the bill (Donations, Rent, Electricity) and in column "B" you enter the amount for each item. As a whole, the list of bills is an object. JSON in its simplest form is a collection of key/value variables or sometimes referred to as key/value pairs.

Programming objects are like real world objects like bicycles, cars, et cetera. Objects can be reduced to a "state" and "behavior". For example, a cars current state can be anything from its brand, condition, color, individual components (tire, doors, or seats). Its behavior can be anything from being stopped, running, parked, or driving. An objects state and behavior can be changed with functions or methods. In QIE a "message" is an object and its state and behavior can be changed, for example moving data fields around, changing its format from HL7 to JSON or XML, or re-formatting the data elements such as removing or adding the hyphens to a Social Security Number.

JSON is also commonly used with FHIR resources. FHIR(Fast Healthcare Interoperability Resources) is a new standard that has a great potential for replacing HL7. FHIR message structures can be coded in XML or JSON. While many people are familiar with XML, JSON has a greater potential to be more widely adopted due to its flexibility and ease of use.