Lesson finished
Up next: Healthcare Data Analytics, Clinical Decision Support and AI
Unlock all 18 lessons of Medical InformaticsFull course ₹40,000 · paid
Healthcare IT Standards, Computer Basics and Biomedical Coding Systems
A free lesson from Skill-Lync's Medical Informatics course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Module 1 Session 2”
What will you learn in this free Medical Informatics lesson?
The lesson lists healthcare IT standards including HL7, FHIR, OAuth 2.0, OpenID Connect and several IHE profiles. It then reviews basic computer architecture and hypervisors, and explains ICD-10, CPT and SNOMED CT with example codes.
- HL7 versus FHIR and IHE profiles
- OAuth 2.0 authorization versus OpenID Connect
- Computer hardware, software and hypervisors
- ICD-10, CPT and SNOMED CT code structure
What comes after lesson 2?
The next free lesson is lesson 3, “Healthcare Data Analytics, Clinical Decision Support and AI” (23 min). Later in Skill-Lync's Medical Informatics course (paid): lesson 4, Module 2 Session 1; lesson 5, Module 2 Session 2; lesson 6, Module 3 Session 1. The full course has 18 lessons (6 h 42 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
We move to our new section that is healthcare information technology standards. So what are HCIT standards or healthcare IT standards? So let's look at the definition. Healthcare systems exchange information according to a set of standards. HCIT standards are agreed upon methods for connecting systems together. Now standards may pertain to security, data transport, data format, or structure, or the meanings of the codes or terms. Right. So for healthcare system to exchange information efficiently with minimal efforts, healthcare standards were created. So the healthcare standards, the main objective remains that the systems within the healthcare domain should be able to effectively exchange the data.
Traditionally, the HCIT standards were designed especially keeping in mind that in hospital we should exchange data with minimal on-site development efforts. So let's look at the different HCIT standards. One of the most common standards that we have seen for exchange of information within the hospital is the HL-7. So it's one of the most commonly used data interchange standards. The next upcoming standard or the FAST or as the name also suggests, FAST Healthcare Interoperability Resource, is the most upcoming standard that has been put to use widely.
Many healthcare organizations or the hospitals have been changing the system to meet this requirement. The idea of moving from HL-7 to FHIR, which is FHIR, it's pronounced as FHIR, is primarily because FHIR supports web-based tools. Right. It's a web-based platform. In today's time, everything is going web-based on cloud. Hence, the transition from HL-7 to FHIR is on RISE. The other standards that are used in the development of the applications are basically OAT2. This is nothing specific to healthcare, but this standard is used extensively by developing healthcare applications.
So what is OAT2.0? It's a simple authorization framework that enables a third-party application to obtain access to an HTTP service. So OAT2, as the definition says, it is authorization and not authentication. So we must have experienced that when we use some applications, when we log in on some of the websites, it may ask you for some other application credentials, like let's say for Google or Yahoo to log on to their website. So essentially what we do is, we don't share our credentials, we use the existing credentials from some other application and we just authorize third-party application for accessing some of the data.
The other technology that we use is OpenID Connect. Now, OpenID Connect connects basically lets developers authenticate the users across websites and apps without having to own and manage password files. Now, in fact, OpenID helps you both authenticate and it helps provide some basic information. So we must have experienced this and also observed that when we log in to some of the websites, we give credentials from, let's say, Facebook or Google. But the basic demographics like our name and maybe sometimes with the display picture is also passed on to the third-party application.
So these two technologies help us communicate with some third-party application without actually sharing our passwords with that third-party applications. Now, the other standard basically there was a project named direct from the Office of the National Coordinator or ONC. So this ONC, basically it's an American body and they had come up with some supported standards for secure exchange of health information. Similarly, consolidated clinical document architecture that is CCDA was in fact also put to use as a standard for exchange of documents. Now, integrating the healthcare enterprise or IHE is an organization where healthcare experts, they work continuously and they create profiles that are used and that basically defines how systems should cooperate with each other or exchange the data.
So IHE has defined quite a few standards for exchange of information within the healthcare communities. Now, some of the standards are listed here like AT&A, audit trail and node authentication, which is basically for basic security and audit logging. XCA stands for cross-community access, so this standard helps basically query and retrieve patient records held by other communities. So, for example, if you have, let's say, a hospital and a primary care, if they want to exchange the information and if such information are stored in this standard format, then the exchange of information is far more easy.
The other standards like XCPD, which is for cross-community, which is for cross-community patient discovery, that helps basically locates patient record in other communities and resolves different patient identifiers. We have XDR, that is cross-community interchange, and that is used for point-to-point sharing of electronic documents. We have XDS, which is cross-community, which is cross-community document sharing, again used for discovery and sharing of electronic documents. PDQ, that's for patient demographics query. So, consult a central patient information server to look up a patient identity based on demographics. So, you can always, if you want to pull some patient demographics, you can query the server and you can pull the required information.
We have PIX, which is basically queries for patient identity, cross-reference among different sites. Now, there are some other standards like from ONC, that is QRDA. Now, quality reporting document architecture is basically a standard that is used for storing any quality-related reports. Now, when such data is stored in a structured format, retrieving such quality information and for future studies becomes far more simpler. Similarly, we have health quality measure format. Similarly, we have health quality measure format. Now, that is used to, in fact, monitor the quality of the document that gets saved.
There is health relation trust, which is heart. Now, this is a layer that is, in fact, on top of the open ID. Basically, this heart relation trust actually enables patient to basically have control on how and when the data can be shared with whom. So, this is a heart standard that basically that's a layer on top of the open ID connect. There is standards and these are specifically used mostly in US at this moment, but soon international bodies and different countries are adopting to these standards.
The last in the list that we see here is prescription drug monitoring program, which is also known as PDMP. This is primarily used in US for monitoring the usage of opioids and everything that gets prescribed and, let's say, administered. Such information are actually stored centrally with the states of the country and this helps them basically keep a track of the drugs that are being used in what quantity and in which manner. So, these are essential concepts are essential concepts for biomedical computing and coding systems for biomedical data.
So, let's understand the essential concepts of biomedical computing. Now, computer architecture is a set of rules and methods that describe the functionality, organization and implementation of computer systems. So, on the right, the image that we see, there is a central processing unit. And in the central processing unit, which consists of control unit, ALU and resistor, but essentially this is the heart of the. Computer which is called the CPU. We obviously have input devices for instance like keyboard mouse that becomes our input devices and we have memory which stores it temporary and permanently as well secondary and main memory and then we have output devices that is basically let's say a display or printer or any form of output.
So that's how our components of computer consist of. You have an input device, CPU, memory and output device. Now what do we have in computer hardware? So hardware refers to the physical components of the computer. Computer hardware is any part of the computer that we can touch. Let's see what computer software is. So software is a collection of instructions, procedures, documentation that performs different tasks on a computer. Now operating system is the first software that gets loaded when a computer starts. We'll see more of this.
So if you look at hardware. So if you look at hardware and its main heart that is the CPUs. Basically CPUs we have servers which are having high computing powers. Then we have workstations which are like mid-end and then we have laptops or desktops or even mobile devices which are you know at low processing power. On the input side. On the input side we have obviously spoke about keyboard as mouse but in medical industry images from CT, MRI, ECG or ultrasound or even the vital signs from like heart rate, respiration, SPO2 and many other medical related data that we feed in becomes the input.
And then we have the output. And then we have the output devices like as we discussed. Speakers, display printers, robotic machines. We have these days AI enabled machines. So these are all output side of the system. Now if we look the software side in detail. So on top of the hardware we always have the operating system. Right. An operating system is system software that manages the computer hardware, software resources and provides common services for computer programs. Right. So here we can see on the right. So here we can see on the right the image. On top of the hardware we have operating system. And on operating system we install our software and the users uses the application.
Now to add some one more layer to this which makes this basically a virtual environment is on top of the hardware we typically install something called hypervisor. The most popular companies that provide hypervisor is from VMware and also from Microsoft that is called Hyper-V. So the virtualized. So the virtualized environment gets that's one of the operating system that gets installed on top of the hardware and on top of this main operating system that virtualizes we install other operating system like Windows, Linux or any other system on top of the virtualized environment.
So basically it becomes operating systems on top of main operating system. So that helps us virtualize the hardware. Now let's look at the coding systems for biomedical data. International healthcare bodies over the years have created a different coding systems to standardize the healthcare data classification, identify data and to maintain the sanity of data on exchange. Below are the most used coding systems. ICD-10 which stands for international classification of diseases. CPT which is current procedural terminology. SNOMEDCT which stands for systemized nomenclature of medicine clinical terms. Then LOINC which is logical observation identifies names and codes that is used primarily for laboratories and ICNP which stands for international classification for nursing practice and ICPC which stands for international classification for primary care.
Now we will see some of the codes. Now we will see some of the codes mentioned here in detail in the next slide. Let's look at the ICD. ICD stands for international classification of diseases is a globally used diagnostic tool for epidemiology, health management and clinical purposes. Now ICD is maintained by World Health Organization WHO. So ICD 11 version was released on 1st of January 2022 but still ICD 10 version remains the most commonly used as it's been in use since early 2000s. So ICD 10 CM codes consist of 3 to 7 characters. Every code begins with an alpha character which is indicative of the chapter to which the code is classified.
The second and the second and the third characters are numbers. The second and the third characters are numbers. So 3 are the minimum that we have and the 4th, 5th, 6th and 7th can be numbers or letters. So let's look at a couple of examples here. Now for ICD 10 codes for hypertensive disease it is generally classified between I10 to I16. So if you look at these codes. So if you look at these codes. So we have for another code that is for acute upper respiratory inspections we have J00 to J06.
The other commonly used coding system is the current procedural terminology. So in 1966 the AMA that is American Medical Association created CPT codes to standardize reporting of medical, surgical and diagnostic services and procedures performed in inpatient and outpatient settings. So CPT code consists of CPT codes. So CPT code consists of 5 characters. The majority of codes are numeric but some codes have a 5th alpha character such as AF, T and U. So let's look at one of the examples. So let's look at one of the examples. For example, any chest x-ray that is let's say done for a patient and that x-ray record has to be saved with a tag 306F.
So this helps us tomorrow when we do any sort of reporting or exchange of data. Descriptive data is difficult to do reporting on. Hence such codes helps us to keep track of all the procedures that were done. And it also helps us know at the end of any period that how many such procedures were done. And similarly ICD-10 that we just saw helps us keep track of the patients that we have had and what were the infections or disease that they came up with. So for example, for example, the second example here is for removal of sinus TASI implant that is and the code is 0510T. So such codes are there for every procedure that is done in the hospital or even in outpatient setting and maintaining such codes helps us basically at some point of time later to even get a quality reports out of the data that we have saved.
So the other coding system that is in use quite extensively is SNOMEDCT. So SNOMEDCT stands for Systemized Nomenclature of Medicine Clinical Terms. It is a standardized international multilingual core set of clinical healthcare terminology that can be used in electronic health records. So SNOMEDCT codes. SNOMEDCT codes are numerical and are minimum of six digits long. For instance, 211737000 is a unique code for the SNOMEDCT Anemia. And we shall see more of such things in the coming slides. Now, this picture actually gives a representation of how SNOMEDCT is designed, right? We have concepts, we have hierarchies, we have attributes, identifiers, descriptions and relationships.
So SNOMEDCT. So SNOMEDCT, if you see closely here, we have a body structure and everything is related to each other in some of the other way. For example, finding a site, right? And then finding a site is musculoskeletal finding, you have joint finding, you have arthropathy, arthropathy of knee joint, arthritis of knee. So every disease or everything is related to each other. So we have relationships between different concepts code. So once you have some concept code, you can always have some reference to other concepts as well that relates to a similar disease.
Now, this is another screenshot showing how the concept is. For example, for this concept ID, the definition is for viral upper respiratory tract infection. Now, this has some kind of relationships. That is, it is a upper respiratory infection. And this is how there is always relations with different aspects of the disease. You would also have some descriptions for this concept code. Which would state, it is upper respiratory tract infection. It is URTI. And the preferred name is basically viral upper respiratory tract infection. Now, let's look at the definition of SNOMED CT and its concepts.
SNOMED CT terminology is organized in four primary categories of SNOMED CT. That's basically concepts, description, relationships, and reference sets. Now, let's look at the concepts. The concepts or terms are represented by unique codes and human-readable description. Each concept is a unique, clinically relevant thought across a wide range like an abscess, zygote, measurement, procedure, or substance. As example, currently, SNOMED CT contains approximately 352,000 plus concepts and is organized by relationships into hierarchies that range from general to detail. So, as we saw in the previous picture, we have had relationships and hierarchies.
Now, descriptions are human-readable terms linked to concepts. Concepts can have multiple descriptions, each of which is a synonym of the original concept. Now, in order to provide meaning to SNOMED concepts, SNOMED uses relationships between concepts to provide formal definitions and organization. For instance, SNOMED concept of viral pneumonia is a infective pneumonia. Now, infective pneumonia is a infection and similarly, infective pneumonia is a respiratory disease. Right. SNOMED CT also links concepts to the applicable part of the body or a finding site. Example, viral pneumonia finding site is the lung.
Right. So, this is how the relations are maintained in SNOMED CT and references are used to customize a version of SNOMED CT or to provide a collection of SNOMED concepts.