This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Catalog FHIR Profile Proposal"
Jump to navigation
Jump to search
| Line 48: | Line 48: | ||
<!--Describe how the current resource will be extended.--> | <!--Describe how the current resource will be extended.--> | ||
| − | * | + | * Add an extension for PublishedDate, unless SD wants to consider that for core |
| − | * | + | * Provide for inclusion of subCompositions (subCatalogs) as an extension |
| + | * Determine how to address lifecycle stage (Draft, Published, etc) | ||
===Example Scenarios=== | ===Example Scenarios=== | ||
Revision as of 15:49, 16 August 2017
This page documents a Pending FHIR Resource Proposal
Catalog (Draft)
- Do we want to be specific and call this Order Catalog?
Profile balloting plans
Profile Details
Profiled Resource(s)
Constraints to be Applied
- Constraint subject to 0..0; Catalog is non patient specific
- Define value sets for documentTypeCode and Composition.class (or constrain out Composition.class)
Extensions to be Applied
- Add an extension for PublishedDate, unless SD wants to consider that for core
- Provide for inclusion of subCompositions (subCatalogs) as an extension
- Determine how to address lifecycle stage (Draft, Published, etc)
Example Scenarios
Scope of coverage
Realm
Realm Neutral
Ownership
Owning committee name
Contributing or Reviewing Work Groups
- Reviewing Work Group:
- Structured Documents
- Contributing WorkGroups:
- Pharmacy
- Clinical Decision Support
- Imaging Integration
- Service Oriented Architecture
Expected implementations
gForge Users
Claude Nanjo, Jose Teixera
FHIR Profile Development Project Insight ID
1010
Plans
Timelines
- Planning for Design Review in time for January 2018 Connectathon
Balloting Requirements
Choose one:
- Ballot with next FHIR DSTU or Normative Edition
- or Ballot independently as DSTU
- or Realm specific ballot
- or No Ballot
Desired Ballot Date
- PutDesiredBallotDateHere
