DRAFT

Last meeting: 2018-08-08 Weekly meeting

Attendance

Martin Rosner
Ana Kostadinovska
Stefan Karl
John Dyer
John Garguilo
Brian Reinhold
Chris Courville
Koichiro Matsumoto
Michael Faughn
George Dixon
John Rhoads (presiding co-chair & notes)

Agenda

PHD Block Vote 8

PoCD IG group progress report on the IG submission:

Stefan presented the pages and artifacts in the current, near-final state of the FHIR Point-of-Care Device Implementation Guide

References

2018-08-13 PoCD IG Group notes

Material on this process is being gathered on the reference page PoCD IG Prep for 2018-09 Ballot

https://github.com/devices-on-fhir/PoCD-IG README file is an essential reference. These are some key links from that document:

Reminder of the timeline:


General FHIR IG information resources: see DoF Implementation Guide Publishing Publication Process


Martin / Brian 9-0-0

Excerpt from page FHIR Implementation Guides relevant to current stage of work:

Excerpt from Standard FHIR Publishing Layout Pattern  relevant to current stage of work:

Every FHIR related specification has a {canonical} URL: this is the logical master URL at which the content is published. For example, the canonical URLs are fixed for HL7 published FHIR specifications:

The canonical URL is tied to the master web server that hosts the IG. The {root} directory is the physical directory on the web server that the {canonical} URL points to.

Inside a {specification} the content can be any valid static HTML desired. Javascript is allowed, subject to the limitations noted [todo]

The standard home page is 'index.html'

The main layout is 

{root}\directory.html

A master file that lists the formal releases of the specification - typically, milestone drafts for connectathon support, ballot subjects, and final publications. It should also reference the current build

{root}\{specification}

The current formally published version. e.g. STU1. When there is no formally published version, then this should be the latest milestone draft. After this is formally published as an STU, this is not necessarily the latest copy

{root}\{version}\{specification}

Archived past versions of the specification. 

When you post a formal published version, you post it twice: once to {root} and once to {root}\{version}