This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceAlertList FHIR Profile Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}") |
|||
| Line 14: | Line 14: | ||
| − | = | + | =DeviceAlertList= |
<!-- Profile names should meet the following characteristics: | <!-- Profile names should meet the following characteristics: | ||
| Line 34: | Line 34: | ||
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | <!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | ||
| − | * [[ | + | * [[http://hl7.org/implement/standards/fhir/list.html| List]] |
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
| − | * | + | * source = Resource(Device) |
| − | * | + | * subject = Resource(Device | Patient) |
| + | * ordered = True | ||
| + | * mode = snapshot | ||
| + | * entry = Resource(DeviceAlert) | ||
====Extensions to be Applied==== | ====Extensions to be Applied==== | ||
Revision as of 18:15, 3 October 2014
DeviceAlertList
Profile Details
Parent Resource
- [List]
Constraints to be Applied
- source = Resource(Device)
- subject = Resource(Device | Patient)
- ordered = True
- mode = snapshot
- entry = Resource(DeviceAlert)
Extensions to be Applied
- Extension 1
- Extension 2
Example Scenarios
Scope of coverage
Ownership
Owning committee name
Contributing or Reviewing Work Groups
- Work Group Name
- or link
- or "None"
Expected implementations
gForge Users
FHIR Profile Development Project Insight ID
Plans
Timelines
- TargetDateForInternalReview
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