DPO Radio

Vietnam National Data Sharing | AesirX ComplianceOne

Overview Image

Why This Overlay Matters

If you run, connect to or supply a national database or public-service portal, these rules shape how you describe, share and publish data. Decree 194/2025/NĐ-CP has applied since 19 August 2025.

This group of rules brings Decree 194 together with:

  • data sharing through public-service portals;
  • the national data architecture;
  • the national data centre strategy;
  • data-creation planning.

Who it is for. Mainly state agencies, national database operators, public-service portals, public-sector integration suppliers and open-data publishers. A private company should treat it as a main framework only if it builds, connects to or relies on these systems.

What you have to keep track of. Ownership, interfaces, shared data fields, lawful reuse, alignment with the architecture, quality controls, feedback and release decisions. ComplianceOne keeps those records linked and reviewable.

What the National Data Cluster Covers

Dimension

Coverage

Scope

National databases, government data exchange, public-service portals and open data. Applies mainly to state agencies, database and portal operators, integration suppliers and open-data publishers

Dataset catalogue

A versioned, field-level data dictionary confirmed by the named data owner. Each field is marked for personal data and linked to your own data registry

Sharing

The receiving body, the legal basis, the channel, the scope, who approved it, the review date, and the dictionary version the receiving body was given

Public Service Portal

Circular 04/2025/TT-VPCP of the Government Office, in force since 25 January 2026, sets which data the National Public Service Portal shares with the systems that handle administrative procedures and with shared state databases, in both directions. A share through the Portal is recorded with the Portal as its channel, apart from sharing between agencies

Acknowledgement

A record of each transfer and whether its acknowledgement came back. An unacknowledged transfer stays visibly pending

Open data

An explicit personal-data check with a named sign-off before publication. Publication and takedown are then kept as history

Correction

The list of recipients is worked out from the transfers and releases that actually happened, including anything already published openly

Architecture

Data domains, owners, stewards, identifiers, shared terms and interfaces

Official reference documents

The Decision 2439 architecture framework, governance framework and shared data dictionary, all Version 1.0. Decision 2439/2025 of the Prime Minister issued them on 4 November 2025 and is in force

National Data Centre

Resolution 175/2023 of the Government (30 October 2023) approved the National Data Centre project. Decision 1751/2025 of the Prime Minister (18 August 2025) approved its data strategy. Both are national plans, kept for reference: ComplianceOne creates no tasks from them

Data-creation planning

Resolution 214/2025 of the Government (23 July 2025), the action plan for creating data. A national plan, kept for reference: ComplianceOne creates no tasks from it

Getting started

Add it to your workspace as a reference first. Use it directly once you have confirmed you run or connect to public-sector data systems

Overview Image

How ComplianceOne Supports National Data Operations

The cluster is available in the Enterprise Unlimited package, through the Sector Overlays module, whether installed directly or for reference.

Describe the data before you share it. You catalogue each dataset and describe it field by field before any sharing decision. Each version of the dictionary is fixed once the named data owner confirms it. A sharing arrangement is recorded against that version, so every transfer shows exactly which description the receiving body was given.

Know which transfers were received. Each transfer carries an acknowledgement. One that never comes back stays visibly pending and is counted, never assumed complete.

Release open data with a named sign-off. Publication goes through a readiness assessment with one required question about personal data and a named sign-off.

Correct errors at every recipient. When you correct an error later, ComplianceOne works out who to notify from the transfers and releases on record. A public release counts as a recipient.

The three official Decision 2439 documents are kept as references to read, not presented as forms to fill in.

Related Modules

Data MappingData Mapping

Holds the dataset catalogue, its dictionaries, and the registry items each field maps to.

Explore Data Mapping

Compliance FormsCompliance Forms

Organizes sharing, open-data, dictionary, portal, and quality records.

Explore Compliance Forms

Task ManagementTask Management

Coordinates reviews, corrections, release approvals, and follow-up.

Explore Task Management

Audit TrailAudit Trail

Preserves data-sharing, quality, publication, and approval history.

Explore Audit Trail

Compare the Difference

Graphic Image

Without Structured Framework Operations

Graphic Image

With ComplianceOne

IconSharing decisions are made on a dataset's name, not its contents.
IconDescribe every dataset field by field before deciding to share it.
IconInterface ownership and authority are hard to trace.
IconRecord each share against the dictionary version it was made on.
IconTransfers go unacknowledged and cannot later be proven.
IconKeep an acknowledgement for every transfer, or show it as pending.
IconOpen-data release decisions lack connected review evidence.
IconRelease open data only after a personal-data check and a named sign-off.
IconCorrections never reach the agencies that already hold the data.
IconWork out who needs a correction from the shares on record.

Built for National Databases, Data Sharing and Open Data Operations

Build For Image

Share on content, not on a name. Your sharing decisions rest on what a dataset contains. The dictionary a share was recorded against is fixed at that moment, so a question about one transfer years later still has the same answer.

Build For Image

Publish without guesswork under pressure. The personal-data question has to be answered, and someone has to put their name to the outcome. A withdrawal stays in the record beside the publication it replaced.

Build For Image

Corrections reach everyone who has the data. The agencies to tell are worked out from the transfers you actually made, including anything published openly. Nobody has to remember who received what.

Background Image

See National Data Governance in Action

See how ComplianceOne handles dataset dictionaries, sharing arrangements, acknowledgements and open-data release evidence.

Demo Image
Ronni K. Gothard Christiansen

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io+84 909 500 760

People Also Ask

Yes. They matter most to state agencies, national database and portal operators, integration suppliers and open-data publishers. Other organisations can add them to their workspace for reference.

The National Data Architecture Framework, the National Data Governance and Management Framework, and the Shared Data Dictionary, each Version 1.0. They are included as official reference documents.

No. They are architecture, governance and dictionary references, not submission forms to fill in.

No. A sharing arrangement is recorded against a confirmed dictionary version, so there is nowhere to record the decision until one exists. The dictionary is the precondition, not the paperwork.

No. It links the relevant evidence to those laws, and each keeps its own obligations and records.

Next Steps

Icon Image

Start a Compliance Pilot

Test one database connection, shared-data interface, or open-data release review.

Icon Image

Discuss Your Compliance Needs

Talk through your public-sector scope, databases, interfaces, architecture and who owns data quality.