Health Level Seven

, Inc.
Project Scope Statement
Template Usage Information:
Replace Highlighted Courier New text with appropriate content; do not change the name/format/font of the template sections
To check a box, double click on the box then select the 'Checked' Radio Button under the 'Default alue' heading!
"or assistance in completing each section, refer to #ppendix #!
The $ro%ect #ppro&al $rocess is documented in #ppendix B!
"or "#'s ("re)uentl* #sked 'uestions+, refer to #ppendix C
,ubmit template change re)uests to $-./012!org
1. Project Name, I an! Pro!"cts
The name should be concise, based on the objective and unique among all other projects the group takes on.
Project Insight: Enter into Project Name and Product Type.
lick here to go to !ppendi" ! #or more in#ormation regarding this section.
!n $% &ill be assigned
by Project $nsight
Enter the name of the project here. Healthcare SOA Ontology Project $ro%ect 3D4
5on $roduct $ro%ect6 (7duc! -arketing, 7lec! ,er&ices, etc!+ 8 Documents 6 9nowledge
#rden ,*ntax 8 "oundation : R3-
Clinical Context .b%ect ;orkgroup (CC.;+ 8 "oundation : ocab Domains < alue ,ets
Domain #nal*sis -odel (D#-+ 8 -essages 6 #dministrati&e
7lectronic 0ealth Record (70R+ 8 -essages 6 Clinical
= -essages : #dministrati&e 8 -essages 6 Departmental
= -essages 6 Clinical 8 -essages 6 3nfrastructure
= -essages 6 Departmental 8 Rules 6 >711.
= -essages : 3nfrastructure 8 ,er&ices : ?a&a ,er&ices (3T, ;ork >roup+
8 Documents : #dministrati&e (e!g! ,$1+ 8 ,er&ices : ;eb ,er&ices
8 Documents : Clinical (e!g! CD#+ 6 5ew $roduct Definition 6
#. Project Intent
lick here to go to !ppendi" ! #or more in#ormation regarding this section.
$ndicate i#'ho& this project a##ects a standard. Project Insight: Enter into Project $ntent.
Create new standard
Re&ise current standard
,upplement to a current standard
3mplementation >uide will be created/modified
Reaffirmation of a standard
;ithdraw current standard
5/# ($ro%ect not directl* related to an 012 ,tandard+
(.a. $allot T%pe
$# applicable, $ndicate the type o# balloting the deliverables &ill go through. Project Insight: Enter into Type) additional in#ormation can be
entered into the *isc. Notes te"t bo".
Com
ment
.nl*
3nformati&e
D,T@
5ormati&e
?oint Ballot (with other ,D.s or 012 ;ork >roups+
5/# (pro%ect wonAt go through ballot+
Add any additional ballot information here. If artifact will be jointly balloted
with other H!" #or$ %roup or other S&O' lit the other group.
(.b. P"&lic oc"ment
heck this bo" i# one o# the project deliverables &ill be a publically available document +#or e"ample a government mandated or #unded
speci#ication, or other&ise subsidi,ed publication-. N.TE/ 0hen a deliverable is speci#ied as a Public %ocument, the T1 must make a
determination as prescribed in the 2.* 1ection 34.35, part +d-.
Project Insight: !dd a comment in Project $nsight6s *isc. Notes te"t bo" indicating a public document &ill be created.
$ublic Document(s+ to be createdB
'. Sponsoring (ro"p)s* + Project Team
lick here to go to !ppendi" ! #or more in#ormation regarding this section.
$rimar* ,ponsor/;ork >roup (1 ,an!ator%+ Enter primary Sponor(#or$ %roup here.SOA
Co6sponsor ;ork >roup(s+ ocabular*, ,ecurit*, 70R, -n-
=C=8D=EFD!doc =GFG ?an Release $age F of FF
Health Level Seven

, Inc.
Project Scope Statement
Project Team:
$ro%ect facilitator (1 ,an!ator%+
Enter Project )acilitator name(email here.*ame
+uc$ner ( jame.buc$ner,tate.ma.u
.ther interested parties #RB
-ulti6disciplinar* pro%ect team (recommended+
-odeling facilitator ?im Buckner, ?obst 1andgrebe
$ublishing facilitator 9en Rubin
ocabular* facilitator $hil Barr, Russ 0amm
Domain expert rep 9e&in >eminiuc, Russ 0amm
Data #nal*st facilitator ?obst 1andgrebe, #nn ;rightson
Business re)uirement anal*st $hil Barr, ?im Buckner
Re)uirements process facilitator #nn ;rightson
3mplementers )# ,an!ator% for D,T@ pro%ects+4
F+
=+
-. Project efinition
7.a. Project Scope
lick here to go to !ppendi" ! #or more in#ormation regarding this section. Project Insight: Enter into %escription.
The scope of this project is to develop a Health Interoperability Service Ontology
encompassing the description and classification of healthcare-oriented SOA services into a single,
formal vocabulary. The concepts identified in this ontology will be derived from several sources,
including but not limited to the SAI, the SOA !" #oadmap, and service capabilities identified in
the $%& '$# unctional (odel. The concepts in this ontology will be e)tended to bridge standard
ontologies in associated domains such as enterprise architecture, clinical care, and biomedicine.
The project will*
identify where reference value sets are needed
collect and+or develop use cases to define the objectives of the $ealthcare SOA
Terminology wor,
assess e)isting SOA ontologies for applicability to meet the needs of the healthcare
domain, and recommend the best-fit for $%&
enhance+e)tend, or create a ta)onomy for healthcare SOA services in the event that an
e)isting body-of-wor, is incomplete or insufficient
')isting terminologies, where applicable, will be utili-ed and+or e)tended. !here appropriate
terminologies are not available, they will be developed to meet the needs of the use cases
identified.
Enter a decription of the project that delineate what it i e-pected to
accomplih.
7.b. Project Nee!
This in#ormation is required by !N1$ #or all ballots. Project Insight: Enter into %escription.
In order to effecti.ely manage buine tranaction and to earch the er.ice
in.entory for a er.ice/tranaction or meage that pro.ide a deired real/world
effect' the community will need to be able to ue publihed' tandard ta-onomie to
identify and elect er.ice with deired capabilitie and characteritic.+riefly
e-plain the reaon behind the need for thi project. 0hi may be related to
=C=8D=EFD!doc =GFG ?an Release $age = of FF
Health Level Seven

, Inc.
Project Scope Statement
legilati.e re1uirement' indutry need' or imilar jutification.
7.c. S"ccess .riteria
Project Insight: Enter into .bjectives and %eliverables.
7stablish terminolog* capable of describing healthcare ,.# ser&ices!
Contains capabilit* that satisfies the primar* use cases!
#t least two organiHation pilot the resulting artifact!
$roduce a product that is consistant with the ,#3" "ramework!
Indicate the ucce criteria for the project.
7.d. Project /&jectives + elivera&les + Target ates
lick here #or #urther in#ormation and e"amples. Project Insight: Enter into .bjectives and %eliverables.
0ithin each ro&, enter the e"plicit &ork product+s- ' objective+s-. $ndicate their target date at the right in
02*'8allot ycle #ormat. $nclude the project end date as the last objective.
9or standards project, this date &ill quite #requently be the projected !N1$ approval date.
Target ate +in 02* or
ballot cycle #ormat, e.g.
:(353 1ept 02*6 or
:(353 ;an 8allot6-
Collect candidate use6cases to scope the usage of the 0ealthcare ,.# .ntolog*
effortEnter objecti.e(deli.erable here.
Enter 0arget
&ate23/4A5/6727
Re&iew existing candidate ontologies for fitness to meet healthcare domain ,.#
needs
FI6?@56=GFG
#lign with 012 ,#3" and document re)uirements for the Draft 0ealthcare ,.#
.ntolog* using ,#3" principles
FI6?@16=GFG
Draft ontolog* for peer re&iew 2/A8%/6727
Ballot for comment September 6727
3nformati&e ballot of first edition *anuary 6722
Project End &ate 9all objecti.e ha.e been met: Enter Pjt End
&ate4ay 6722
7.e. Project epen!encies
Project Insight: Enter into %ependencies.
0ealthcare ,.# .ntolog* work will collaborate with ,ecurit* .ntolog* $ro%ect to ensure a product that is aligned
and complementar* with that pro%ectAs approach and results!Enter any dependencie or the name ;
Project Inight I& of project9: that thi project i dependent upon to achie.e it
objecti.e.
7.#. Project oc"ment 0epositor% Location
3ndicate where can one go to find deli&erables/documents created b* the pro%ect team! Project Insight: Enter into *isc. Notes.
Enter the location where upporting project document and other project information
will be $ept' e.g. < H!" #i$i' 0SC #i$i' %)orge' Project Inight' the #or$ %roup=
web page on www.H!".org' etc.SOA Page' wi$i.hl".org>
7.g. $ac12ar!s .ompati&ilit%
3ndicate the backward compatibilit* of the expected pro%ect artefacts/deli&erables, if known!
Project Insight: Backwards Compatibilit*) enter additional in#ormation into *isc. Notes.
#re the items being produced b* this pro%ect backward compatibleB
Jes 5o DonAt
9now
5/#
If deired' enter any additional information regarding +ac$ward Compatibility.
3. Project 4pproval ates
5ote that the ,D and T,C #ppro&al dates donAt need to be captured in this template; this section simpl* reminds pro%ect facilitators about the
need to gather ,D and T,C appro&al! ,D/T,C appro&al dates will be entered into $ro%ect 3nsight as the* occur!
,ponsoring >roup #ppro&al Date Project Insight: Enter into 1tart %ate. #or$ %roup Appro.al &ate
,teering Di&ision #ppro&al Date S& Appro.al &ate
=C=8D=EFD!doc =GFG ?an Release $age 8 of FF
Health Level Seven

, Inc.
Project Scope Statement
Technical ,teering Committee #ppro&al Date 0SC Appro.al &ate
5. 67ternal Project .olla&oration
Click here to go to #ppendix # for more information regarding this section! Project Insight: Enter into ollaboration E##orts.
Include S&O or other e-ternal entitie you are collaborating with' including
go.ernment agencie a well a any indutry outreach. Indicate the nature and
tatu of the 4emorandum of 8ndertanding 94O8: if applicable.Indeterminant at
thi time. 4ay in.ol.e collaboration with O4% Ontology SI% under H!" 4O8 with the
O4%. Other group may be identified with targeted interet' and we will determine
appropriate collaboration a the project unfold and falling within H!" 4O8 with
appropriate organi?ation.
<.a. Sta1ehol!ers + 8en!ors + Provi!ers
$ndicate the associated stakeholders, customers and providers #or &hich this project is intended. heck all that apply. This in#ormation is
required by !N1$ #or all ballots. Project Insight: Enter into 1takeholders ' ustomers ' Providers.
Sta1ehol!ers 8en!ors Provi!ers
Clinical and $ublic 0ealth 1aboratories $harmaceutical Clinical and $ublic 0ealth 1aboratories
3mmuniHation Registries 70R, $0R 7mergenc* ,er&ices
'ualit* Reporting #gencies 7)uipment 1ocal and ,tate Departments of 0ealth
Regulator* #genc* 0ealth Care 3T -edical 3maging ,er&ice
,tandards De&elopment .rganiHations
(,D.s+
Clinical Decision ,upport
,*stems
0ealthcare 3nstitutions (hospitals, long term
care, home care, mental health+
$a*ors 1ab .ther (specif* in text box below+
.ther (specif* in text box below+ 03, 5/#
5/# .ther (specif* below+
5/#
Other< Indicate other ta$eholder' .endor or pro.ider not lited abo.e.
9. 0ealm
lick here to go to !ppendi" ! #or more in#ormation regarding this section. Project Insight: Enter into =ealm
@ni&ersal Realm ,pecific (Enter @8.S.A or name of H!" affiliate here+
:. 0oa!map 0eference
lick here to go to !ppendi" ! #or more in#ormation regarding this section. 9or more detail regarding the =oadmap 1trategies, go to/
http/''&&&.hl>.org'documentcomments'inde".c#m. Project Insight: Enter into =oadmap =e#erence.
Check which Roadmap ,trateg* best relates to *our pro%ect!
#! 1ead the de&elopment of global technical and functional health informatics standards!
B! ,treamline the 012 standards de&elopment process!
C! "acilitate 012 standards adoption and implementation!
D! Define an o&erarching and internall* consistent interoperabilit* framework!
7! 7nsure broad and encompassing stakeholder engagement in the standards de&elopment process!
"! #lign 012's business and re&enue models to be responsi&e to national bodies while supporting global standards de&elopment!
>! 5one of the abo&e appl* to this pro%ect!
=C=8D=EFD!doc =GFG ?an Release $age C of FF
Health Level Seven

, Inc.
Project Scope Statement
Appendix A - Instructions (Delete prior to submitting the completed scope statement)
Click here to return to this section in the template abo&e!
$ro%ect ,cope ,tatement $urpose4
This $ro%ect ,cope ,tatements is intended for products used outside 012, such as pro%ects to produce standards or 3mplementation >uides!
Infrastr"ct"re projects (the 0I,, HL9 maintaine! voca&"lar%, 2rappers, an! metho!olog%+ should also use this scope statement but are
not re)uired to complete all sections as noted in the instructions!
The ob%ecti&e of this template is to communicate the t*pe of acti&ities a group is undertaking to achie&e specific ob%ecti&es or to produce
specific work products! $ro%ect ,copes should pro&ide sufficient information to allow inexperienced indi&iduals to anticipate what a group is
working on and decide if the* wish to become in&ol&ed! $ro%ect ,cope statements should also assist committee chairs to manage the
workload of the committee and help to set priorities and recognise inter6dependencies with the work of other committees!
The ,teering Di&isions, T,C, and other appropriate appro&al bodies, as defined b* the 012 organiHation and $ro%ect #ppro&al and 3nitiation
$rocess, re&iew and appro&e the pro%ect re)uest! This includes anal*sis to a&oid pro%ect o&erlaps or dependenc* gaps! # pro%ect not aligned
with 012 strategies established b* the 012 Board, or re)uiring extensi&e resources ma* not be appro&ed! # KhostedL pro%ect (funded b* an
external source+ ma* be appro&ed as long as the sponsors pro&ide ade)uate resources and the pro%ect is not detrimental to 012 strateg*;
funding ma* be in the form of resources or financial support, grants, etc!
0e;"ire! Information:
The 012 $ro%ect -anagement .ffice ($-.+ will re&iew pro%ect statements to ensure the names and descriptions are clear and unambiguous
across all pro%ects and that re)uired information is pro&ided so as to obtain pro%ect appro&al!
Project Insight Note:
The following instructions indicate how the information in this form is mapped to certain fields in $ro%ect 3nsightAs pro%ect description form! The
fields are mapped to specific fields in the pro%ect description form a&ailable in $ro%ect 3nsight4
http4//healthle&else&en!pro%ectinsight!net/1ogin!aspxBReturn@rlMN=fdefault!aspx
3f *ou need s*stem login setup for $ro%ect 3nsight, contact the 012 Director of the $ro%ect -anagement .ffice at pmo/hl2!org
0ecommen!ation for Non<infrastr"ct"re Projects:
The 012 $roduct 1ifec*cle recommends ballots proceed through Informative STU Normative phases, howe&er, 012 polic* allows
pro%ects to proceed to normati&e ballot without an 3nformati&e or Draft ,tandard for Trial @se (D,T@+ in special circumstances, such as such
the need to respond to go&ernment mandate or resol&e a critical issue raised b* a stakeholder or noted in an existing #merican 5ational
,tandard! B*passing the 3nformati&e and/or D,T@ ballot must be appro&ed b* the T,C! Refer to the 012 >o&ernance and .perations
-anual ,ection F8 : Re&iew Ballot and ,ection FC : 5ormati&e Ballot for additional information!
F! Project Name, I an! Pro!"cts .lic1 here to return to this section in the template abo&e!
The name should be concise, based on the ob%ecti&e and uni)ue among all other pro%ects the group
takes on! Project Insight: Enter into Project Name.
$ro%ect 3D4 # pro%ect 3D will be
assigned b* $ro%ect 3nsight
Pro!"ct)s*: 3ndicate the associated $roduct line(s+; check all that appl*! 5ote4 ;hile this list is representati&e, the authoritati&e list of
products is maintained in $ro%ect 3nsight! Refer to the K$roductsL tab of the worksheet at the following @R1 for the definition of the products4
http4//www!hl2!org/documentcenter/public/wg/sips/$roducts<,er&icesRe&enue-atrix!xls! Project Insight: Enter into Product Type.
=! Project Intent .lic1 here to return to this section in the template abo&e!
3ndicate if/how this pro%ect affects a standard!
Project Insight: Enter into Project $ntent) add notes i# needed, especially #or Project $ntent ? .ther6 +belo&-.
=!a! $allot T%pe
3f applicable, 3ndicate the t*pe of balloting the deli&erables will go through
Project Insight: 1elect a value #rom the Type dropdo&n.
=C=8D=EFD!doc =GFG ?an Release $age I of FF
Health Level Seven

, Inc.
Project Scope Statement
=!b! P"&lic oc"ment
;hen a deli&erable is specified as a $ublic Document, the T,C must make a determination as prescribed in the >.- ,ection GD!GF, part (d+
(a&ailable at4 http4//www!hl2!org/documentcenter/public/membership/012O>o&ernanceOandO.perationsO-anual!pdf+!
Project Insight: !dd a comment in Project $nsight6s *isc. Notes te"t bo" indicating a public document &ill be created.
8! Sponsoring (ro"p)s* + Project Team .lic1 here to return to this section in the template abo&e!
,ome pro%ects are %ointl* sponsored and the name of all sponsoring ;ork >roups should be noted!
7&er* pro%ect must ha&e at least one pro%ect sponsor and a pro%ect facilitator part*; a multi6disciplinar* pro%ect team is recommended, e!g!
domain expert, @-1 modeling facilitator, 012 modeling facilitator, re)uirements process facilitator, data anal*st facilitator, business
re)uirement anal*st! ,ponsorship ma* be in the form of resources or funding!
The $ro%ect "acilitator is mandator* for all pro%ects and should be the contact person if there are )uestions about the $ro%ect ,cope ,tatement!
The $ro%ect "acilitator ser&es as the $ro%ect 1ead; the 'go to' person for the pro%ect who can answer )uestions regarding status, scope,
ob%ecti&es, issues, risks, etc! regarding the pro%ect!
This section should also describe other Pinterested partiesA, e!g! anticipated interactions with other committees or other pro%ects!
3nfrastructure pro%ects, for example, the R3-, 012 maintained &ocabular*, wrappers, and methodolog* are re)uired to name onl* the $rimar*
,ponsor and $ro%ect "acilitator!
Q-odeling, $ublishing, and ocabular* facilitators are formal roles recogniHed b* 012, and highl* recommended as pro%ect participants! 3f
*our pro%ect has not filled this role, please indicate a contact person for the role, for example, *our pro%ect ma* not ha&e a formal &ocabular*
facilitator but a committee participate has &olunteered to ser&e as liaison with the ocabular* Committee!
Implementers )# ,an!ator%*: 3f this pro%ect will produce a standard, identif* at least two implementers who agree to implement a D,T@
prior to normati&e ballot (this is a non6binding agreement+! Contact information is mandator*! The intended implementers must be identified at
pro%ect initiation; howe&er, it is a non6binding agreement! Refer to explanation of Candidate ,tandard &alidation below for additional
information! Project Insight: Enter into Project $mplementers.
Candidate ,tandard &alidation
Candidate ,tandard
&alidation
7xecuting the Candidate ,tandard &alidation approach! 012 will ha&e a modified open approach to candidate
standard &alidation! #ll those participants that made a non6binding commitment when the pro%ect was initiated will be
included if the* choose to honor the commitment! .thers ma* be added to achie&e a balance or for other
necessities for &alidation! The pre&ious notwithstanding, 012 will limit the number of participants to ensure a
manageable process and reasonable time frame!
Candidate ,tandard
&alidation approach
# pro%ect step that ensures that the Candidate ,tandard is &alidated b* external industr* resources before it is
finaliHed as a normati&e standard! ;here the standard is for interoperabilit*, it is expected that the &alidation will
include at least two independent entities (&endors, user organiHations, etc!+ building trial implementations and testing
them together! ;here the standard ser&es another purpose the &alidation approach will in&ol&e a trial effort to use
the draft standard in the manner for which it was created!
#t the planning stage the entities willing to test must make a non6binding declaration of their intent to participate in
&alidation! ;ithout such a declaration the pro%ect should not be initiated!
.omment: This is expected to be a significant hurdle for new pro%ect initiation! #t the same time it helps to assure
that 012 member resources will be concentrated on efforts that ha&e a greater likelihood at industr* adoption!
C! Project efinition .lic1 here to return to this section in the template abo&e!
C!a! Project Scope
The detail should be sufficient that an indi&idual with no pre&ious exposure to the group (or e&en 012+ could understand the expected
acti&ities and results! The scope description should also include high le&el expectations for the pro%ect and indicate alignment with market
demands or other dri&ers for the pro%ect, such as go&ernment mandates, re)uirements from industr* interoperabilit* connectathon, etc!
T*picall* pro%ects to produce standards are routinel* supported b* the &olunteer resources committing to complete the pro%ect, and 012 in
the form of meeting rooms, conference call facilities, etc! 3f additional funding is re)uired, *ou must pro&ide a budget for the pro%ect! #
proposed budget is re)uired for an* pro%ect that will be contracted, for example, website redesign or tooling de&elopment!
Project Insight: Enter into %escription.
=C=8D=EFD!doc =GFG ?an Release $age R of FF
Health Level Seven

, Inc.
Project Scope Statement
C!b! Project Nee!
7xplain the reason behind the need for this pro%ect! This ma* be related to legislati&e re)uirements, industr* needs or similar %ustifications!
This section must be completed for pro%ects containing items that are expected to be #5,3 appro&ed, as it is an #5,3 re)uirement for all
ballots! The information will be used in the 53B form!
Project Insight: Enter into %escription a#ter the Project 1cope verbiage.
C!c! S"ccess .riteria
3ndicate the success criteria for the pro%ect!
Project Insight: Enter into Project .bjectives and %eliverables
C!d! Project /&jectives + elivera&les + Target ates
Click here to return to this section in the template abo&e!
7nter a bullet list of ob%ecti&es the pro%ect is tr*ing to meet! 3f the pro%ect is to de&elop one or more
work products, the work productsA descriptions should be clear, concise and unambiguous! ;ork
products intended to produce a standard should be in terms of the deli&erables4
new elements methodolog* (e!g! a new wa* of deri&ing message specification from a in
information model+
new interface specification for ser&ices or application roles
new functional models
new message specification (e!g! a new message structure that refers a the state
transitions of a new t*pe of clinical act+
new standard profiles (e!g! CD# implementation guide+
new terminolog* subsets or mapping
new tools intended to impro&e producti&it* and support the methodolog*
3n those cases where the ob%ecti&es are not work products, the* should be described so that an
outside obser&er can answer K*esL or KnoL to the )uestion Khas this ob%ecti&e been metBL
#s the pro%ect progresses, ob%ecti&es and work products can be refined!
$ro%ects that ha&e more than one work product to deli&er should list each work productAs expected
deli&er* date, taking into consideration expected dependencies among work products!
Project Insight: Enter into Project .bjectives and %eliverables .
Target Dates
7xact dates are not needed!
7nter in ;>- or ballot c*cle format,
e!g! 4 P=GFG ,ept ;>-A or
P=GFG ?an BallotA!
Target dates in $ro%ect 3nsight are
onl* pro&ided in the abo&e format!

Target dates can be updated!

Example of Objecties ! Delierables ! "arget Dates:
Click here to return to this section in the template abo&e!
The following attempts to con&e* how to identif* &arious ob%ecti&es /deli&erables and their target dates!
/&jective + elivera&le Target ate
Complete anal*sis, design, draft specification work on ,tandard SJT =GGD ,ept ;>-
,ubmit for Comment .nl* Ballot =GFG ?an Ballot
Consider Comments from the Comment .nl* Ballot =GFG ?an ;>-
,ubmit for D,T@ Ballot =GFG -a* Ballot
Consider Comments from the D,T@ Ballot =GFG -a* ;>-
,ubmit to T,C for D,T@ appro&al =GFG ,ept ;>-
D,T@ $eriod : = *ears ?an, =GFF : ?une, =GF=
,ubmit 3mplementation >uide for 3nformati&e Ballot =GFF ?an Ballot
,ubmit ,tandard SJT for 5ormati&e Ballot =GF= ,ept Ballot
Reconcile from 5ormati&e Ballot =GF= ,ept ;>-
,ubmit for 5ormati&e Ballot &= =GF8 ?an Ballot
#5,3 #ppro&es ,tandard SJT =GF8 -a* ;>-
Close $ro%ect (pro%ect end date+ =GF8 -a* ;>-
=C=8D=EFD!doc =GFG ?an Release $age 2 of FF
Health Level Seven

, Inc.
Project Scope Statement
C!e! Project epen!encies
This section is not re)uired for 3nfrastructure $ro%ects!
The dependenc* ma* be the work of another pro%ect undertaken b* this group or b* another group! #nticipating dependencies can allow
groups to coordinate their effort to ensure the o&erall ob%ecti&es of 012 can be met! #n example of a dependenc* is4 The CD# ballot needed
the Data T*pes produced b* 3nfrastructure and -anagement $ro%ect to be through ballot before the CD# ballot could be finalised!
Project Insight: Enter into %ependencies.
C!f! Project oc"ment 0epositor% Location!
3ndicate where one can go to find deli&erables, documents, artefacts created b* the pro%ect team for this pro%ect! 1ocations could be the 012
;iki, T,C ;iki, >"orge, $ro%ect 3nsight
Project Insight: Enter into *isc. Notes.
C!g! $ac12ar! .ompati&ilit%!
3ndicate the backward compatibilit* of the expected pro%ect artefacts/deli&erables, if known!
Project Insight: Enter into *isc. Notes.
I! Project 4pproval ates
=or1 (ro"p 4pproval ate: The date the sponsorAs ;ork >roup appro&ed the pro%ect! Project Insight: Enter into 1tart %ate.
S 4pproval ate: The date the sponsorAs ,teering Di&ision appro&ed the pro%ect! Project Insight: Enter into 1% !pproval %ate.
TS. 4pproval ate: The date the Technical ,teering Committee appro&ed the pro%ect! Project Insight: Enter into T1 !pproval %ate.
R! 67ternal Project .olla&oration .lic1 here to return to this section in the template abo&e!
3nclude ,D.s or other external entities *ou are collaborating with, including go&ernment agencies! 3ndicate the nature and status of the
-emorandum of @nderstanding (-.@+ if applicable!
#greement ,tatus4 -emorandum of @nderstanding (-.@+ or #ssociate Charter ,tatus t*pes are4 5egotiating or signed (please indicate the
date signed!+ 1ea&e blank if there is no agreement in place! Refer to http4//www!hl2!org/about/agreements!cfm for a current listing of 012As
-.@ agreements!
Project Insight: Enter into ollaboration E##orts.
R!a! Sta1ehol!ers + ."stomers + Provi!ers
This section must be completed for pro%ects containing items that are expected to be #5,3 appro&ed, as it is an #5,3 re)uirement for all
ballots! The information will be used in the 53B form!
3ndicate the associated stakeholders, customers and pro&iders for which this pro%ect is intended! Check all that appl*! Project Insight: Enter
into 1takeholders ' ustomers ' Providers.
2! 0ealm .lic1 here to return to this section in the template abo&e!
3ndicate whether the pro%ect is applicable globall* (uni&ersal+, or intended for a specific countr* or region (realm+! 5ote that 5on6@, realm
pro%ect scope statements should be directed to the appropriate 012 #ffiliate!
Project Insight: Enter into =ealm
E! 0oa!map 0eference .lic1 here to return to this section in the template abo&e!
"or more detail regarding the Roadmap ,trategies, go to4 http4//www!hl2!org/documentcomments/index!cfm
Project $nsight/ Enter into #$oadmap $eference%
Appendix & - Project Approal Process (Delete prior to submitting the completed
scope statement)
Click here to return to this section in the template abo&e!
Step Process
1. $ro%ect "acilitator creates a $ro%ect ,cope ,tatement ($,,+! The $ro%ect ,cope ,tatement can be located on the Co6Chair
=C=8D=EFD!doc =GFG ?an Release $age E of FF
Health Level Seven

, Inc.
Project Scope Statement
@tilit* $age at4 Download the ;ord template for the $ro%ect ,cope statement
5ote4 *ou can get to this link &ia the Co6ChairAs @tilit* page at wwwl!hl2!org!
"rom there, Click on PCommitteesA header on the right side!
Click on P@tilitiesA link! $age down to the link labelled Download the ;ord template for the $ro%ect ,cope statement
=! ,ponsoring >roup re&iews and appro&es the $ro%ect ,cope ,tatement!
alidate re)uirements of the $,, ha&e been met
$ro%ect "acilitator resol&es an* issues!
5ote4 T*picall* the ,ponsoring group is a ;ork >roup (formerl* known as TC or ,3>!+
8! The $ro%ect "acilitator emails the $,, to the appropriate ,teering Di&ision(s+ and the 012 $ro%ect -anagement .ffice
(pmo/hl2!org+!
5ote4 T*picall*, this submission corresponds to the =nd ,unda* after the ;>- deadline as stated on the publishing
calendar! This indicates that the ,D and T,C appro&als will occur after this deadline, as the #RB re&iews ha&e in *ears
past!
C! $-. re&iews the ,cope ,tatement (this occurs simultaneousl* with step I+!
$ro%ect "acilitator resol&es an* issues, note that changes ma* need to be communicated to the ,teering Di&ision!
I! The appropriate ,teering Di&ision re&iews and appro&es the $,, for criteria such as4
is this $,, clear in terms of its scope and deli&erable(s+
is it within the scope of the sponsoring committee
how is it related to other pro%ects
how is it related to the acti&ities of other committees
,D indicates priorit* within ,D, if necessar*! $riorit* is based on resources, target dates and technical strategies!
,D re&iew results could be4
#mended scope statement
$ro%ect needs to be re&iewed (%ointl* or separatel*+ b* another ,D
$ro%ect "acilitator resol&es an* issues brought forth b* the ,D!
R! The ,teering Di&ision submits ,cope ,tatement to T,C for appro&al b* creating an issue for the T,C on >"orge and
attaching the $,, to the issue!
T,C appro&al includes the following4
alidate pro%ect is in alignment with 012 strateg*
#ssign a T,C le&el priorit*
T,C re&iew results could be4
Board appro&al ma* be necessar* if the pro%ect re)uires internal or external funding or collaboration with an external bod*
T,C appro&ed pro%ects shall be communicated to the4 Co6Chair and #ffiliate lists!
(The ,D < T,C re&iews replace the former #RB re&iew; howe&er the #RB ma* be called upon to resol&e an* architectural
issues+!
The $ro%ect "acilitator can monitor the status of the $,, b* re&iewing the appropriate issue &ia the Tracker tab on the T,C
>"orge page located at4 http4//hl2pro%ects!hl2!nscee!edu/tracker/BatidM8F8<groupOidMI=<funcMbrowse
2! The $-. audits the $,, appro&al process and enters appro&al dates in $ro%ect 3nsight!
E! $-. and $ro%ect ,er&ices Committee insure that 012 pro%ect methodolog* is adhered to!
Appendix ' ( )re*uentl+ As,ed -uestions
Click here to return to this section in the template abo&e!
>: =hat is the !efinition of a project?
#nswer4
=C=8D=EFD!doc =GFG ?an Release $age D of FF
Health Level Seven

, Inc.
Project Scope Statement
"rom the 012 De&elopment "ramework, ,ection =!=!F, 012 ;ork 7ffort4
#n 012 work effort represents an acti&it* being undertaken b* an existing ;ork >roup or Board appointed committee to achie&e specific
ob%ecti&es or to produce specific work products!
# ;ork >roup shall consider a work effort to be a pro%ect if one or more of the following is true of that work effort4
U in&ol&es a group outside of 012 (ma* re)uire Board appro&al+
U re)uires external funding (ma* re)uire Board appro&al+
U is going to be balloted
U re)uires cross6committee participation
U is determined to be a pro%ect b* the committee
#n 012 pro%ect4
U has an ob%ecti&e (statement of what is going to be produced+,
U will ha&e a finite existence (the end date to be determined b* the resources a&ailable and the start date+, and
U if additional funding is re)uired, it will ha&e a budget (including resources and funding sources+
U will ha&e at least one participant a&ailable to contribute and must ha&e a pro%ect leader, if onl* an interim to get the pro%ect started
U will ha&e at least two implementers (unless the pro%ect is intended to support the 012 infrastructure+
U will ha&e an estimated schedule
$ro%ect -anagement 3nstituteAs $-B.9 >uide and the publication KThe "ast "orward -B# in $ro%ect -anagementL indicate the following4
T*picall*, a pro%ect is a temporar* endea&or undertaken to create a uni)ue product or ser&ice! #ll pro%ects ha&e two essential characteristics!
(F+ 7&er* pro%ect has a beginning and an end! (=+ 7&er* pro%ect produces a uni)ue product! 012 also recogniHes P-aintenanceA pro%ects
which usuall* repeat on an annual basis; these maintenance pro%ects do not need to be re6submitted or ha&e a definite end date!
Temporar* means that e&er* pro%ect has a definite beginning and a definite end! Temporar* does not necessaril* mean short in duration, it
%ust means that pro%ects are not ongoing efforts! "urthermore, pro%ects in&ol&e something that has not been done before and which is,
therefore, uni)ue!
$ro%ects shouldnAt be confused with ongoing operations! .ngoing operations ha&e the opposite characteristics of pro%ects in that the* ha&e no
defined end and the* produce similar, often identical, products! 7xamples of ongoing operations are (a+ an insurance compan* processes
thousands of claims e&er* da*; (b+ a bank teller ser&es o&er FGG customers dail*, pro&iding a few doHen specific ser&ices!
The ob%ecti&e of a pro%ect is to attain the ob%ecti&e and close the pro%ect! The ob%ecti&e of an ongoing operation is t*picall* to sustain the
business!
>: o I nee! to create a Project Scope Statement if m% project isn@t going thro"gh the &allot process?
#4 Jes, all pro%ects need to ha&e a $ro%ect ,cope ,tatement completed and submitted to the 012 $-.! # lot of work done b* 7ducation,
-arketing, 7lectronic ,er&ices, #rB, $3C, etc! does not need to go through the ballot process, howe&er, &isibilit* of that work is necessar*!
$ro%ect ,cope ,tatements are the foundation for communicating pro%ect information! The* also ser&e as a tool for $ro%ect "acilitators to gather
the right information to begin a pro%ect as well as track the pro%ectAs progress!
>: o I nee! to create separate Project Scope Statements for each Implementation ("i!e or other s"pport !oc"ments?
#4 # single $,, can indicate multiple deli&erables for the standard being addressed, so, no, a separate $,, does not need to be created for
each 3mplementation >uide or support document for that standard! ,impl* identif* all of the 3mplementation >uides and documents in the
$ro%ect .b%ecti&es and Deli&erables section that are to be produced for the pro%ect!
>: The scope or o&jective of m% project change!. o I nee! to create a ne2 PSS?
#4 Jou ma* or ma* not ha&e to as it depends on the change! .ftentimes, the scope or ob%ecti&es of a pro%ect ma* change during its lifec*cle,
perhaps due to regulator* changes or t*ing back to a different standard!
3f the change in scope or ob%ecti&es is minor, simpl* update the existing pro%ect scope statement, and within $ro%ect 3nsight, indicate the
modifications in the appropriate fields! Jou can also use the P-isc! 5otesA text box for documentation!
3f the change in scope or ob%ecti&es is ma%or, the $ro%ect "acilitator should submit a new $ro%ect ,cope ,tatement, as man* of the original
information wonAt accuratel* reflect what is being done an*more!
>: I@ve s"&mitte! m% PSS to m% Steering ivision for approval &"t haven@t hear! an%thing from them. =hat sho"l! I !o?
=C=8D=EFD!doc =GFG ?an Release $age FG of FF
Health Level Seven

, Inc.
Project Scope Statement
#4 "irst, check the ,teering Di&isionAs meeting minutes! 1ook to see if *our pro%ect was on one of their agendas, and if so, if it was appro&ed
or the ,D had further )uestions! Jour first point of contact with the ,D should be their $ro%ect "acilitator! 3f *ou canAt contact them, contact the
,teering Di&ision Representati&e and #lternate!
3f the ,D has appro&ed *our pro%ect, the* will submit it to the T,C for appro&al &ia >"orgeAs tracker s*stem! To &iew which appro&als *our
pro%ect has gathered, find *our pro%ect b* using the ,earchable $ro%ect Database tool, located in the Resources column on the www!hl2!org
home page!
>: o I nee! to "p!ate the PSS if I !iscover after it@s approve! that I nee! to coor!inate &allots 2ith other HL9 =or1 (ro"ps?
#4 Jes, we recommend updating the Ballot ,trateg* section of the $ro%ect ,cope ,tatement as well as $ro%ect 3nsight! 3nclude the ballot name
and release/&ersion *our pro%ect is coordinating with!
>: o I nee! to incl"!e &"!get fig"res in m% scope?
#4 T*picall* pro%ects to produce standards are routinel* supported b* the &olunteer resources committing to complete the pro%ect, and 012 in
the form of meeting rooms, conference call facilities, etc! 3f additional funding is re)uired from 012, *ou must pro&ide a budget for the pro%ect!
# proposed budget is re)uired for an* pro%ect that will be contracted, for example, website redesign!
>: =hen 2ith!ra2ing or reaffirming a stan!ar!, !oes a PSS nee! to &e create! an! go thro"gh the revie2+approval process?
#4 Jes, for both cases!
3n this case Pwithdrawing a standardA refers to man* things, such as choosing not to extend a standard that has reached its I *ear end6of6life or
identif*ing the need to sunset a standard! B* creating a $,, and following the appro&al process, *ou gi&e the opportunit* to communicate the
withdrawal to the 012 membership and allow them to weigh in on an* potential work needed to successfull* withdraw the standard!
>.- ,ection FC!F8 has more information on withdrawing a standard!
Reaffirmation of a standard re)uires a normati&e ballot!
>: efine Atas1@ an! Aactivit%@ as relate! to project management.
#4 Theoreticall*, Pacti&it*A is the action &erb within a PtaskA! 0owe&er, for 012 pro%ects, PtaskA and Pacti&it*A can be considered s*non*mous
terms!
Task/acti&ities should be4
,pecific 6 a single, well defined, discrete acti&it*! The E/EG is a good guideline 66 no task should be smaller than E hours or larger than EG
hours!
#chie&able 6 it should be something that can be done as a single deli&erable and can be defined as being completed or done such as a
document being produced!
-easurable 6 it should be an acti&it* that can be measured such as a deli&erable produced, an elapsed period of time or number of
iterations
>: Ho2 sho"l! a =or1 (ro"p !oc"ment ann"al 2or1+maintenance 2ithin Project Insight?
#4 # pro%ect entr* should be opened in $ro%ect 3nsight indicating the annual work and the respecti&e *ears! This pro%ect should ha&e a $ro%ect
,tatus of P8 Jear $lan 3temA; note that a $ro%ect ,cope ,tatement isnAt needed for this entr* because itAs a 8 Jear $lan item and onl* high le&el
information is necessar*! This pro%ect can then remain Pas6isA, or modified so it indicates accurate future *ears!
;hen the ;ork >roup actuall* begins the annual work, the* should complete a $,, indicating the scope of work in&ol&ed and gather the
necessar* appro&als for the $,,! # new pro%ect in $ro%ect 3nsight will be created (and will ha&e a $ro%ect ,tatus of P#cti&e $ro%ectA+! .nce the
scope of work has been completed for this pro%ect, it will be closed/archi&ed!
0ence, the 86Jear $lan pro%ect alwa*s remains open; the P#cti&e $ro%ectA $,, will be the pro%ect reflecting the specific annual maintenance
being done!
#n example of the abo&e situation can be found for $ro%ect ,er&iceAs annual updates to the $,, Template! $ro%ect I8F is the 8J$ entr*
indicating the need for the work in =GFG, =GFF, =GF=, =GF8 and be*ond! $ro%ect IEF was created to identif* the specific work that would be
done for the =GFG updated template! 3n ?anuar*, =GFG, pro%ect IEF was closed because the new $,, template was released to membership,
howe&er pro%ect I8F was modified to remo&e references to P=GFGA and remains open to indicate the need for the work each *ear!
>: Sho"l! a project remain open+active !"ring it@s STU Test Perio!?
#4 Jes, it should! This means that the pro%ect will continue to show up in the ,earchable $ro%ect Database and on $ro%ect 3nsight reports!
=C=8D=EFD!doc =GFG ?an Release $age FF of FF