2. SOA FHIR Action Items
Creating SOA labeling standard/name space/naming convention for FHIR Operations.
The expectation is that SOA FHIR services will be extensions to the base FHIR spec, to ensure consistent state, context and behavior. The FHIR community may elevate some or all of these extensions into the base spec.
Document the new process
Create boiler-plate for new docs
Create an SFM for FHIR
Establish FHIR community liaison for each spec
Infrastructure tooling workflow review
Do independent validation of process with Brian P. and Bryn Rhodes
Brainstorm how to engage the community
eg: FHIR Connectathon

3. Service Specific FHIR Artifacts
Produce recommended set of service specific enhancements to FHIR Resources.
Produce SOA FHIR Profile for service being developed.
Identify collective set of FHIR Operations to fulfill the needs of the service.
Develop Implementation guide for service.
Apply SOA FHIR naming convention to FHIR Operations of the service.

4. Process Steps Develop SFM STU Reconcile SFM STU Publish SFM STU
Define inputs/outputs/expected behaviors
Iteratively refine FHIR resource STU content
Contribute FHIR resources to FHIR STU
Include FHIR resources in SFM as informative
Ballot SFM
Reconcile SFM STU
Publish SFM STU
Issue OMG RFP
Based on SFM STU
Cite most recent published FHIR ballot
Cite FHIR as a platform specific model
Submission (Technical Spec)
Define Technical interfaces and operational details
Refine STU resources to normative; contribute to FHIR ballot
Normative HL7 artifacts
SFM normative Ballot
Next ballot release of FHIR
Include Operations and Resources from submission

5. OMG HL7 SOA HL7 FHIR Ballot Normative Start STU Dev Publish Normative
Ballot STU
Publish STU
Reconcile
ballot
Reconcile
ballot
HL7 SOA
Include FHIR Resources;
Connectathon
Incorporate feedback
Ballot FHIR
HL7 FHIR
Tech Spec Submission
Tech Spec Publication
Feedback to HL7
Create RFP
Issue RFP
Finalization
OMG

6. Process Outcomes