Packaging Health Data

This section helps you understand data packaging, what goes into the main envelope, types of health information and much more. The examples provided in this section only explain the syntactic meaning of the data formats. For expressing symantec meaning via standards, encoding and terminologies please refer to the CDAC NRCeS website or as recommended by NHA.

Developers resource

• You will need to use an FHIR client library to code the JSON samples provided in the sections below. Please refer to the FHIR references for developers and implementers at this link.
• During development, it’s usually a good idea to validate the resource. For this, you may use one of the validators listed in the reference library/resources section. For example, the following example validates the entire file content (json)

FHIR Documents

• As explained in the APIs and Standards section, the following are the Health Information (HI) Types that are currently supported. The document type codes must be specfied as per the defined SNOMED-CT codes specified below. Please check the “Main Envelope” section to see example.

• Please refer to NRCeS’ Implementer’s Guide to create FHIR documents compliant to the FHR standards.

This section covers