# Definition of the release\_package\_information.json file format

**URL:** https://forums.snomed.org/t/definition-of-the-release-package-information-json-file-format/426
**Category:** Terminology Management Group
**Created:** [October 7, 2025, 5:42am UTC](https://forums.snomed.org/t/definition-of-the-release-package-information-json-file-format/426 "2025-10-07T05:42:19Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mlawley](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/mlawley/32/241_2.png) [@mlawley](https://forums.snomed.org/u/mlawley)
#### Post date: [October 7, 2025, 5:42am UTC](https://forums.snomed.org/t/definition-of-the-release-package-information-json-file-format/426/1 "2025-10-07T05:42:19Z")

</div>

I am trying to find the specification for the format of the `release_package_information.json` file. I believe it should look like this, but cannot find any original information following the confluence site migration.

```auto
"packageComposition" : {
   "essentialComponents" : {
     "[moduleID of package being described]" : {
       "[effectiveTime of package being described]" : {
         "[moduleID + FSN of module 1 being included in package, that must form part of this product whenever it's used]" : "[effectiveTime of module 1 being included in package]",
         "[moduleID + FSN of module 2 being included in package, that must form part of this product whenever it's used]": "[effectiveTime of module 2 being included in package]"
       }
     }
   },
   "optionalComponents" : {
     "[moduleID of package being described]" : {
       "[effectiveTime of package being described]" : {
         "[moduleID + FSN of module 1 being included in package, that can optionally form part of this product whenever it's used]" : "[effectiveTime of module 1 being included in package]",
         "[moduleID + FSN of module 2 being included in package, that can optionally form part of this product whenever it's used]": "[effectiveTime of module 2 being included in package]"
       }
     }
   }
 }

```

---

<div class="post-metadata">

### Author: ![rdavidson](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/rdavidson/32/3_2.png) [@rdavidson](https://forums.snomed.org/u/rdavidson)
#### Post date: [October 7, 2025, 5:44am UTC](https://forums.snomed.org/t/definition-of-the-release-package-information-json-file-format/426/2 "2025-10-07T05:44:57Z")

</div>

I found this in the new Spaces - [https://conf.spaces.snomed.org/wiki/spaces/RMT/pages/131957934/Update+to+the+.JSON+file+metadata+-+addition+of+Package+Composition+data](https://conf.spaces.snomed.org/wiki/spaces/RMT/pages/131957934/Update+to+the+.JSON+file+metadata+-+addition+of+Package+Composition+data).

Can you see it?

---

<div class="post-metadata">

### Author: ![aatkinson](https://avatars.discourse-cdn.com/v4/letter/a/5daacb/32.png) [@aatkinson](https://forums.snomed.org/u/aatkinson)
#### Post date: [October 7, 2025, 10:43am UTC](https://forums.snomed.org/t/definition-of-the-release-package-information-json-file-format/426/3 "2025-10-07T10:43:49Z")

</div>

Hi @mlawley - I’ve added a page to the Release File Spec site, as the original spec was held in an internal page due to it also containing system config info: [Metadata Files | SNOMED International Documents](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-release-file-specification/component-release-file-specification/4.2-file-format-specifications/metadata-files) As you mentioned above (and Rory then tagged) there is an ongoing discussion in the TRAG on how best to extend this, in a similar format to the one you listed. However, as the TRAG haven’t yet reached a consensus on this, the spec currently shows the existing format. Would you like me to push this discussion up the agenda for the October meetings, so we can force a conclusion and move to a new format?