Create AsciiDoc IHE DEV OID Special Pages

[ToddCooper]

As part of the SDPi specification, an expansion of the DEV OID allocations was required. This was discussed during the April 2022 IHE DEV Spring meetings (see attached slides, #15 to 17 ). The general topic was discussed per the SDPi Topic: SDPi BICEPS Extension Namespace , and a decision was decided at the Gemini 2022-04-08 SDPi Friday (see Discussion Notes (3.a.v)).

Proposal

1. Create an AsciiDoc / HTML page based on the current PCD OID Management wiki page
2. Update the content to reflect DEV, while maintaining the PCD history
3. Update the content to reflect new profiles actors and transactions since the page was last updated
4. Update the content to reflect the SDPi additions (see slide Topic of Interest: Discovery Proxy Actors  #17 below)
5. Publish content on profiles.ihe.net/DEV as a special page (working with IHE Publications)
6. (TBD) Update the IHE wiki OID Management page linked in (1) above

Background

• Gemini SES+MDI Project Update 2022-04-28A.pdf

[ToddCooper]

14 April 2023 Discussion: Add "Special Pages" folder containing a DEV OID folder with the actual content tables.

[ToddCooper]

@d-gregorczyk The actual effort to create this page is pretty straightforward; however, the title says "AsciiDoc" assuming that that's what we want to use so as to embed content that can be programmatically extracted better than simple markdown (whichever flavor IHE (John Moehrke) is using these days. In the end, we have to generate HTML which is what Mary will publish.

ALL TO ASK how hard is it to get an AsciiDoc conversion to HTML using plain vanilla AsciiDoc and doing so in our DEV repo? IOW - What does Dr. David recommend?