This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Patient Administration Resource development"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "__NOTOC__ Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information Return to [...")
 
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
Project Page Template - This template is for voluntary use, but provides guidance for consistent representation of wiki pages reporting project information
+
Return to [http://wiki.hl7.org/index.php?title=FHIR FHIR Mainpage]
 
 
Return to [[Main Page]] - ''include link to return to [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group main page] or [[Main_Page|wiki page]] who sponsored the project''
 
*list project co-sponsors and link to their WG [[Main_Page|wiki page]] or [http://www.hl7.org/Special/committees/index.cfm?ref=nav Work Group web pages]
 
 
 
<noinclude>''This template was developed using examples from other project pagess: Annotated ECG, BRIDG as DAM, Canonical Pedigree, DCM for Dev, EHR Interop, EHR RM-ES, Oncology EHR, RPS, Templates registry, SPL, VMR </noinclude>
 
  
 
==Project Information==
 
==Project Information==
 +
This project will identify and define the initial set of “key” FHIR resources related to the domain of Patient Administration.  These resources will be defined using the available FHIR tooling and in accordance with documented quality guidelines and balloted as part of the initial FHIR specification.  Expected FHIR resources to be produced include: Patient, Person, Group, Organization, Encounter, Appointment, Service Delivery Location, Place 
  
Link to [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm Project Insight Searchable Database] Entry, which contains:
+
In addition, as the committee deems appropriate and time availability permits, it will define a small number of FHIR extensions relevant to domain content and expected to be necessary to support consistent early implementations.
*Brief description of project
 
*Name the project facilitators, (add contact info if desired)
 
*Link to project scope statement
 
*Name the [http://www.hl7.org/listservice/index.cfm? project listserv] if a special one exists
 
  
  
Line 21: Line 13:
  
  
==Status==
+
==Resource development pages==
*If balloting, list ballot name/[http://www.hl7.org/ctl.cfm?action=ballots.home&ballot_cycle_id=523&ballot_voter_id=0 cycle]/[http://www.hl7.org/documentcenter/ballots/2011may/downloads/ISO_IDMP_SUBSTID11238_R1_N1_2011MAR.pdf link]
+
* [[FHIR Person]]
*If in DSTU, link to [http://www.hl7.org/dstucomments/ DSTU comments page]
+
* [[FHIR Patient]]
*If in development, link to [http://gforge.hl7.org/gf/project/work in progress]
+
* ....
*Some projects explicitly list objectives from scope statement and status for each
 
 
 
 
 
==Issues/Hot Topics==
 
*List issues or link to issues tracking repository ([[Template:NEW_V3_Publishing_Issue|wiki pages]] or [http://gforge.hl7.org/gf/project/ GForge])
 
 
 
 
 
==Project Documents==
 
*Link to working documents/[[Main_Page|wiki pages]]
 
*Link to [http://gforge.hl7.org/gf/project/ project GForge]
 
*Link to reference documentation on [http://gforge.hl7.org/gf/project/ GForge], HL7 Web site [http://www.hl7.org/special/Committees/claims/docs.cfm WG Documents/Presentations page], or external web pages
 
 
 
 
 
<noinclude>==Categorization== </noinclude>
 
To include your Project Page in a category listing, just include a statement like <nowiki>[[Category:Active_Projects]]</nowiki>
 
  [[Category:StyleGuides]]
 

Revision as of 00:57, 18 May 2012

Return to FHIR Mainpage

Project Information

This project will identify and define the initial set of “key” FHIR resources related to the domain of Patient Administration. These resources will be defined using the available FHIR tooling and in accordance with documented quality guidelines and balloted as part of the initial FHIR specification. Expected FHIR resources to be produced include: Patient, Person, Group, Organization, Encounter, Appointment, Service Delivery Location, Place

In addition, as the committee deems appropriate and time availability permits, it will define a small number of FHIR extensions relevant to domain content and expected to be necessary to support consistent early implementations.


Meeting Information


Resource development pages