Last modified by Artur K. on 2026/05/29 14:28

From version 1.7
edited by Helena K.
on 2026/01/15 12:31
Change comment: There is no comment for this version
To version 1.6
edited by Helena K.
on 2026/01/15 12:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -383,6 +383,7 @@
383 383  
384 384  in both cases: important to include only concepts, code lists, and codes actually available / used by the data
385 385  )))
386 +| | | | |
386 386  
387 387  In general, finding the “perfect” data structure is less important for bilateral data exchange. Independent, custom-tailored DSDs may do the job quite well, as harmonization and standardization are typically not of high importance. If the data exchange is just a part of a more comprehensive scenario (e.g. multi-purpose, multi-domain, gateway, or data-sharing scenarios), a master DSD with satellite DSDs is preferable.
388 388  
© Semantic R&D Group, 2026