1. Why Domain Committees are formed?

In order to define Metadata and Data Standards for a domain, it is important to possess domain expertise and knowledge. The different Ministries/ government departments would be most suitable to define the entities and data elements for their respective domains. Hence, Domain Committees are constituted.

A Domain Committee, chaired by Joint Secretary/Additional Secretary of that domain, will be responsible for formulating Metadata and Data Standards for that domain while working closely with e-Gov Standards division.

For detailed roles and responsibilities of a Domain MDDS Committee, please refer https://egovstandards.gov.in.

2. How the metadata of generic data elements will be maintained?

Each of the domains will create and maintain its own domain repository of its standardized data elements along with their metadata. A Central Metadata Registry (MDR) will be created which will maintain the standardized generic data elements (along with their metadata) common across domains. This MDR will provide the indexing/linking to different domain repositories.

3. What do you mean by intra/inter domain entities?

Intra domain entities are being referred as the entities which happen to exist among the different applications within a domain.

Whereas, Inter domain entities happen to exist across the domains.

Intra/inter domain can be used synonymously as within/across domains, respectively.

4. What is a Domain Code and its significance?

Domain Code is a 2-digit unique number allocated to each of the domains by e-Governance Standards division. This Domain Code is included while assigning a reference number to different data elements in a pre-defined format.
This helps in tracking the domain to which a particular data element belongs.

5. Why data elements are grouped under an entity?

Entities are defined for logical grouping of data elements, however each data element is supposed to be defined as an independent unit with its own existence.

For example, in Drinking Water & Sanitation domain, data elements related to ‘Scheme’ such as Scheme Name, Scheme Code, Scheme Type/Category, Scheme description, etc. can be grouped and defined under an entity ‘Scheme’.

6. What is an application specific data element?

This type of data element is specific only to an application in a domain and does not affect interoperability among different applications within/across domains. It need not be a candidate for standardization for a particular domain and/or across the domains.

For instance, in the Health domain, the data element “Reason for visit” of the patient, is application specific and may be required only in MIS of an application in Health domain and hence is not required to be standardized.

7. What do you mean by Customized data element?

A data element whose description, format, size etc. can be derived from the already standardized and notified generic data elements, is defined as Customized Generic Data element.

For instance, the data element “Name of the Patient” of Health domain corresponds to the Generic Data Element “Name of the Person” (Generic Data Element specific to Person Identification, defined in MDDS Demographic Ver 1.1) and the standardized description, data formats and size will be applicable as defined.

8. Can a particular domain view the draft Base Papers/ Metadata and Data Standards of other domains?

Yes, the draft Base Papers/ Metadata and Data Standards of other domains are available on the e-Gov Standards portal https://egovstandards.gov.in under the heading ‘Domain Work Area’.

9. While formulation of Domain specific MDDS, how does role of Domain MDDS Committee differ from MDDS Advisory Body?

Domain MDDS committee, under the chairmanship of JS/AS of the specific Domain is responsible for formulation of Metadata and Data Standards for a domain. It maintains the repository of metadata of standardized generic data elements in the domain, along with history of the changes. It also liaisons with eGSD (NIC) for inclusion of approved metadata and data elements, in centralized registry & repository of metadata of standardized generic data elements.

The draft Domain specific Metadata and Data Standards undergo Closed Group/Public review and are revised based on review comments. In case there are any conflicts or issues related to ownership and definition of data and metadata of identified generic data elements, it is the responsibility of MDDS Advisory Body (under the co- chairmanship of DG (NIC) & AS (eGov)) to resolve those issues. MDDS Advisory body will submit the domain specific MDDS finalized after closed group / Public review to Apex Body for approval.

Back to Top