IHE Publication of Referenced Artifacts Folder

[ToddCooper]

SDPi requirements are currently published on the profiles.ihe.net/DEV/ via a link to one file: SDPi/referenced-artifacts/sdpi-requirements.json

Now there is a set of other files in that same referenced-artifacts folder, which should also be published along with the standard.

QUESTION: How should we make these additional generated files available at publication time:?

As a single ZIP file?
A ref to a new confluence page with an explanation and list of files? (so you could immediately view the file in your browser - note this is analogous to the ITI Archive page).

[ToddCooper]

@MaryLJ - Let's schedule a quick sync next week and I can show you exactly what we would like to do. How to do it is totally your choice, but it should be relatively simple and there is no "process" to navigate to make the change. The SDPi team reviewed the issue on today's SDPi Friday call 2026.07.17 and all agreed: Whatever Mary wants to do ... !

[MaryLJ]

I am available until 3:00 CDT today and any time tomorrow. Thanks. Mary Jungers Documentation Specialist | IHE International ***@***.******@***.***>

…

________________________________ From: ToddCooper ***@***.***> Sent: Friday, July 17, 2026 9:19 AM To: IHE/DEV.SDPi ***@***.***> Cc: Mary Jungers ***@***.***>; Mention ***@***.***> Subject: Re: [IHE/DEV.SDPi] IHE Publication of Referenced Artifacts Folder (Issue #550) [https://avatars.githubusercontent.com/u/6361944?s=20&v=4]ToddCooper left a comment (IHE/DEV.SDPi#550)<#550 (comment)> @MaryLJ<https://github.com/MaryLJ> - Let's schedule a quick sync next week and I can show you exactly what we would like to do. How to do it is totally your choice, but it should be relatively simple and there is no "process" to navigate to make the change. The SDPi team reviewed the issue on today's SDPi Friday call 2026.07.17 and all agreed: Whatever Mary wants to do ... ! — Reply to this email directly, view it on GitHub<#550?email_source=notifications&email_token=AGDULOMDJCFAQJH2FM57NPL5FIYXBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQZDCNRRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5004216182>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGDULOOVKYDSMMTTYADEJGD5FIYXBAVCNFSNUABFKJSXA33TNF2G64TZHM2TQMBXHE2DCNZXHNEXG43VMU5TIOBZGUZDMMBRGM32C5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AGDULOMXPI24CFPPEOGWL735FIYXBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQZDCNRRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AGDULOLM3VQHSKRZBZLKMR35FIYXBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGQZDCNRRHAZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[ToddCooper]

2026.07.22 Update:
@MaryLJ & @ToddCooper reviewed this Issue, discussed options & priorities and settled on the following:

1. Keep the current approach - A user friendly name for the file with a link to the underlying JSON
2. Here are the name - file correspondences @PaulMartinsen PLEASE REVIEW THESE SHORT DESCRIPTIONS FOR ACCURACY!

• sdpi-content-modules.json "SDPi Content Modules"
• sdpi-deprecated.json "SDPi Deprecated ??? List" ( @PaulMartinsen ... what exactly is being deprecated in this file?)
• sdpi-profiles.json "SDPi Profile Requirements"
• sdpi-requirements.json "SDPi Requirements Compilation"
• sdpi-requirements-deprecated.json "SDPi Deprecated Requirements List"
• sdpi-transactions.json "SDPi Transaction Requirements" (@PaulMartinsen ... are these "requirements" or just detailed info?)
• sdpi-transactions-deprecated.json "SDPi Deprecated Transactions List"
• sdpi-use-cases.json "SDPi Use Case Requirements List"

3. Mary will update when she gets a chance - since this is not a priority, there is no rush

• She may do it soon as time allows, and as a separate publish to the SDPi 2.4.1 current published doc
• May wait until 2.5.0 is ready
• May wait until after 2.5.0 !

NOTE: The current release has two documents published: DEV.SDPi / sdpi-documents / sdpi-standard & / sdpi-supplement
THESE FILES SHOULD ONLY COME FROM the / sdpi-standard / referenced-artifacts directory!

NOTE 2: @MaryLJ in a future release, we will publish BOTH a new IHE "sdpi-supplement" rendering, that will truly be a supplement (IOW it will eventually disappear and be integrated into the IHE DEV TF), and a Gemini "standalone" standard that is the actual standard that is jointly published by IHE and HL7 and is not a "supplement" ... but stands by itself as a standard. More on that ... later!

[PaulMartinsen]

Filename	Friendly Name
sdpi-content-modules.json	Content modules defined in the SDPI specification
sdpi-profiles.json	Transactions, content modules, actors, use cases and profile actor options for SDPi profiles
sdpi-requirements.json	Requirement definitions from the SDPi specification
sdpi-transactions.json	Transaction definitions from the SDPi specification, including actor contributions
sdpi-use-cases.json	Use case definitions, including specification background and scenarios, from the SDPi specification
sdpi-transactions-deprecated.json	SDPi transactions that have been deprecated
sdpi-requirements-deprecated.json	SDPi requirements that have been deprecated
sdpi-deprecated.json	Collection of all deprecated oids (including transactions and requirements)

[MaryLJ]

Thank you!

[ToddCooper]

Thank you!

@MaryLJ - Let us know if you need anything else.

@PaulMartinsen - Thanks!!!

[ToddCooper]

2026.07.24 SDPi Friday -

@MaryLJ - Note that 2.4.x did not have all these referenced-artifacts files. So support for this should be added to the 2.5.x or later publication.