Health Level Seven Functional Requirements



Table of Contents

Over All Goals 2

Look and Feel 2

Login 3

Home Page 4

About 4

Affiliate Microsites 4

Products and Services / Store 5

History 9

Implement 9

News 9

Participate 10

Work Groups 10

Conference Calls 10

Document Management 12

Search 12

Administrative Interface 12

Development 13

Over All Goals

1. The technical requirements for the new website center around three basic principles: Integration, Performance and Ease of Administration.

2. Integration: The use of consistent navigation and integrated services is a must.

3. The site must be simple for site managers to use. All applications must provide appropriate administrative functions to allow HL7 to effectively manage their use.

4. Administration should be kept in mind when making technology selections for .

5. User orientation features allow intuitive movement within the site structure.

6. Users should be able to navigate, search, and accomplish primary tasks easily and quickly providing greater efficiency across the organization.

7. The site will balance an intuitive user experience with the need to support and automate complex business process.

8. Build a cohesive infrastructure for all applications within the site.

9. Features may be provided by many individual applications; however this should not be apparent to the average user.

10. Administration Functions – Allows for management of the entire system including all of the other modules.

Look and Feel

1. The look and feel of the new will be CSS Driven and will be Priority One W3C compliant for usability.

1. The global navigation for the site will need to integrate not only with the content management system but also each of the individual sub-applications.

2. The site has a polished look to it (a professional look and feel).

3. Consistency across pages and interface (Navigation and other items).

4. User orientation features allow intuitive movement within the site structure.

5. Consistent fonts needed throughout website (CC 452),

1. Have all the custom coded portions match the fonts used on the About HL7 landing page (which I think is OOB MOSS).

1. Ecommerce has a larger, thinner font.

2. Country and State/Province drop downs are a different font.

3. Ecommerce pop-ups (cvv2, check/wire transfer) are in Times New Roman.

Login

1. Login

1. Login should have “Remember Me” feature (CC 163)

1. Remember just the username.

2. Not be tied to the SharePoint “Remember Me” checkbox that allows for session information to transfer through SharePoint Designer and exporting of spreadsheets.

1. This should be always on by default.

2. The users session should stay persistent through the 12 hour session regardless of whether or not the user closes the browser.

3. Form inputs for username and password named using standard naming conventions (username, user_name, password, pass, etc…) (CC 308).

1. This should allow for browsers such as IE to recognize the inputs as username and password and allow the user to save username and password through their browser.

4. When Signing in, have cursor in the User Name text box (CC 346).

1. After clicking Sign In in the upper right corner, I then have to click in the User Name text box, the cursor should be in the User Name text box so I can immediately type in my User Name.

5. Allow user to look up their username and password (CC 449).

1. Links on the login for “Forgot Username” and “Forgot Password”.

2. “Forgot Username” will allow the user to enter their email address and have their username emailed to them.

3. “Forgot Password” will allow the user to enter their username and email their password .

6. The user should have the option to change their password.

1. Add the option to change the password to their profile page (CC 228).

2. Single Sign-on

1. Single sign-on integration with Project Insight and GForge.

1. Username and Password should be stored within the profile.

2. Username and Password will not necessarily match the credentials used for the HL7 website.

3. Each site (Project Insight and GForge) will need its own set of credentials.

4. The user and administrators should be able to edit the credentials used for login.

5. Each user will need their own individual logins, there is not one universal login for all users to user.

6. Multiple users may share a single set of credentials.

7. Users should be notified if a single sign-on fails with a message alerting that they could not be authenticated.

8. It would be ideal, but not required, that the SharePoint search be able to search the Project Insight and GForge systems.

3. Error when clicking on "My Settings" link (CC 467)

1. I get and error when I click the "My Settings" link in the upper right hand corner (mouse over your login name).

The given key was not present in the dictionary.

at System.ThrowHelper.ThrowKeyNotFoundException()

at System.Collections.Generic.Dictionary`2.get_Item(TKey key)…

Home Page

1. On the main HL7 page an Hourglass will appear every couple of seconds.  This seems to be tied in with the Benefactor logo changing.  The hourglass should not appear when the Benefactor logo changes. (CC 75).

2. Have the 'Case Studies' link on the home page go to the Implement...Case Studies page (it currently brings up a PDF file of our Ed Summit brochure). (CC 238)

About

1. Individuals such as Staff and Board member (CC 242, 366).

1. Three HL7 Staff members are also on the Board of Directors. It appears the existing membership configuration doesn’t allow for this, as the fields to configure a Board member are also used for Staff members.

11. Create an Advisory Committee page (CC 232)

1. Create a link on the About HL7 landing page; label the link 'Meet the HL7 Advisory Committee'.

2. Have the link go to a page that lists the Advisory Committee members based on their membership DB attributes.

3. Information displayed for each Advisory Committee member should follow the ‘General Rule’ specs in the UserInfoWebpart document located in Project Documents/Work Groups.

12. Unable to have an individual appear in multiple sections of the TSC page (CC 367).

Affiliate Microsites

1. Affiliate Microsites should have the same features as the Work Group sites.

1. Ability to post content.

2. Ability to supply link to affiliate’s external site if they have one.

3. Affiliate can contribute news stories to the affiliate page.

1. System will provide a discreet RSS feed for affiliate news.

2. Affiliate news can be flagged by staff to appear with general news.

4. Supports a wiki.

5. Pull Affiliate chair from membership database and display in place of Work Group co-chair.

Products and Services / Store

1. Interface to upload and administer Products and Services.

6. Product Information

1. Name

2. Description

3. Price (member and non-member)

4. Associated downloads

5. Related documents

6. Conflicting documents

7. In stock

1. Out of stock items should appear in the store with an out of stock message, but not able to be purchased

8. Active

1. In active items should not appear in the store at all

9. Shipping (flat rate prices) (CC 84)

1. Rate Categories

1. US, Canada, Mexico (Typically $5)

2. International (Typically $15)

2. Members can only ship to their own address since they are getting a reduced rate on items.

10. Delivery Options per item (CC 101)

1. Mail via CD

2. Download

11. Requires license agreement to be signed (Yes/No) (CC 65)

1. Members must sign agreement upon purchase? (Yes/No) (CC 53).

1. Members may not have to sign agreements for all documents as their membership agreement may cover it.

2. Don’t allow the user to complete transaction unless they have signed the license agreement for any items requiring an agreement.

3. Email notification of license agreement should be sent to HL7 and the member.

4. Ability to specify what license agreement to show.

1. Different products may have different license agreements.

5. Ability to edit/add/maintain license agreements.

12. Free membership offer with purchase (Yes/No) (CC 364)

1. When a non-member purchases a full standard CD (either V2 or V3 at the moment), they need to be offered a complimentary membership. The cost of purchasing a membership is the same as purchasing the standard.

The most ideal method to handle this would be how handles it. There is an option to add a membership to your cart. Doing so gives you the member price on any additional items you have in your cart. Upon checkout, you are made a member.

I'm sure we'll want to sit down and discuss this since there are many things to consider, and maybe easier to implement options.

13. Is featured item (Yes/No)

1. Determines if the item appears on the store home page or not within its category.

13. The user should be able to access all of their purchased documents through the “My Purchased Standards” page.

1. This page was started but not completed.

2. We have been unable to update the text on this page (CC 334).

14. Checkout

1. Credit card page cleanup (CC 450)

1. No error message appears when credit card number is blank; system only indicates CVV2 needs to be entered.

2. Gray labels should have * indicating they are required. This needs to be consistent across the system.

2. Add a link that prints the Wire Transfer and Check pages during the payment process. These are the pages that come up after the user clicks the link labeled “(Click here for wire transfer details.)” and “(Click here for check details.) (CC 275)

3. When paying by credit card, the on-screen confirmation should have a print page option as this has a confirmation number and username and password on it. (CC 278)

15. Bookstore Order Processing (CC 65)

1. Generate email to orders@ to alert of any items that need manual processing (payment by check or wire transfer; items which need to be shipped)

2. Filter/Report on Orders

1. Provide the ability for staff to filter/report on orders.

2. Order statuses can be: ‘pending payment’, ‘pending shipping’, ‘completed’

3. Search by: name, company, order date range, order status

3. Credit Card Payment

4. Process credit card via Skipjack

5. Purchaser receives email confirmation their payment has been received and their order will be processed

1. If purchase includes a downloadable item, the email should indicate to the purchaser that their purchase is available via download on the website

2. If purchase requires shipping, email notification to orders@ and place in a “pending shipping” status

3. Update history as per history requirements

4. Email template needs to be modifiable by staff

6. Ship item (see below)

2. Check/Wire Transfer Payment

1. Purchaser’s order is placed in a ‘pending payment’ status until staff approves order. 

1. Downloads/files are not available to purchaser until order is approved.

2. Purchaser receives email that their order will be processed when payment is received

1. Email will include check/wire transfer info (address, routing number, etc.)

2. Email template needs to be modifiable by staff

3. Process check/wire transfer payment

1. Provide ability to pull up a list of transactions not yet processed

2. Enter check number / wire transfer ID into history for the purchaser

3. Mark transaction as complete

1. If purchase includes a downloadable item, an email is sent to the purchaser indicating their purchase is available via download on the website

1. Email template needs to be modifiable by staff

4. Ship item (see below)

4. Items that need to be shipped

5. Generate report of items that need to be shipped

1. Search by: name, company, order date range

6. Generate shipping labels for a select list of items from the shipping report

7. Generate packing slip

16. Educational Materials and Implementation Resources areas not completed (CC 259).

1. HL7 Store: Educational Materials

1. A list of items for download and/or items to be shipped (books etc.) which will have the ecommerce interface like the Standards for Sale.

2. There will be a list which is administered from the Admin page similar to the one used for Standards for Sale.

2. HL7 Store: Implementation Resources

1. A list of items for download and/or items to be shipped (books etc) which will have the ecommerce interface like the Standards for Sale.

2. There will be a list which is administered from the Admin page similar to the one used for Standards for Sale.

17. Changes to the HL7 Store layout

1. On the HL7 Store page, change the gray boxes so that they represent the different categories in the store. One for each category: (CC 362).

1. Standards and Implementation Resources - List the top level standards for sale (pretty much what it is doing now).

2. Educational Materials - It would be ideal to have a checkbox to determine which items in this category appear within this box so that we can show 2-3 items that we can change.

3. On-Site Training - The text you have on there is fine, just put it into a box like the others.

4. Promotional Items - Just like the Educational Materials, it would be ideal to be able to mark certain items to appear in the box.

2. Grouping items within the bookstore (CC 363)

1. We'd like to group the items on the bookstore pages into "Current Version", "Older Versions", and "Implementation Resources". So if you are looking at the HL7 Version 2 related bookstore items, it would show Version 2.6 first, following by versions 2.5.1 through 2.0, and then any implementation resources for sale below that. Each section should have a header. We could manually mark what the item is in the list (current version, older version, implementation resource).

18. HL7 Store Checkout - existing or new user? (CC 474)

1. In the HL7 store, when going to Check Out, instead of just having the Log In screen appear, the screen should provide two options - ask user to Log In or Create an Account.

2. For a good example to follow, buy something on via their Marketplace tab.

19. Purchasing conflicting items in the bookstore (CC 365).

1. Standards for sale are setup very similar to how music CD's are currently available. There is a full CD (like V2 or V3) that contains a number of "tracks", and there are also individual "tracks" available for sale. We would like it such that someone should be notified if they put a full CD into their cart that already contains an individual "track" that they also have in their cart. For example, when Dave buys the "Greatest Rock Hits of the 80's" and then tries to purchase the single "Poison - Every Rose Has Its Thorn", the system should confirm (although not prevent) that he wants these despite the fact that this track is already available on the other CD.

Need to confirm the following: Each "track" is only available as a single, on a full CD, or as a single and exactly one full CD. IE, "Poison - Every Rose Has Its Thorn" is available on a single CD, and the "Greatest Rock Hits of the 80's" album, but no other albums (We don't sell "Poisons greatest hits" or the original album the song was sold on). So at most there is one conflict per item. That way there could be a column in the list to point to the master item that contains this item?

History

The current SharePoint system has limited storage of history.

• E-Commerce transactions are stored in SQL.

o These are exported daily into a DBF file using DTS for use in Peachtree accounting.

• Event registrations are stored in a SQL database.

1. eCommerce

2. Date of payment

3. Payment type (CC, Check, Wire)

4. Amount of payment

5. Payment was for?

1. Event Registration

2. Bookstore

1. Include Individual Items Purchased

3. Memberships

Implement

1. On the Certification Directory grouping on the left, the current grouping is as follows (CC 441):

a. Certification Type

b. Certification Location

c. Certified Name / Date

Change to the following:

a. Certification Type (Remove label preceding value)

b. Certification Location / Date (Order by date Descending followed by location) (Remove label preceding value)

c. Certified Name

2. Members Only standards downloads should appear on the standards page (CC 462).

3. Create the Implement...Case Studies page per the specs (the current page indicates 'this page needs content'). (CC 238)

News

1. Allow news releases and press kits to be posted as HTML documents rather than attachments. (CC 69, 71)

2. News Release 'post date' doesn't work; a news release to be published 11/20 showed up on the site right away (11/19). (CC 144)

3. News RSS feeds do not validate. According to the W3C validator, the RSS news feeds do not validate: (CC 466)

Participate

1. Benefactor logo link broken in upper right portion of Participate...Membership; needs to scroll through all of the logos (CC 175).

2. Create Organizational Members Page (CC 289)

6. Similar to the pages that list all the Benefactors or all the Supporters, we need a page that lists all the organizational members. Will need to get this information from the AMS software database.

Work Groups

1. For the Facilitators heading display, when there is nothing under it, have a messages be added here (e.g., No facilitators have been identified for this work group). (CC 230)

2. Document management issues (CC 50)

7. Document description and other meta data is not available for setting or editing when uploading a document.

8. Document expiration date and rules for expiring content is not working.

9. Ability to flag document for certain levels of access. 

3. Remove the HL7 logo from the Work Group area that appears to the right of the Site Name (Work Group Name) in the Work Group template. (CC 471)

4. Change Overview to single HTML web part instead of list. Putting it into a list in the end makes it harder to manage and edit. Make sure that they can have links in the HTML to point to whatever they chose. (CC 472)

5. Co-chairs do not appear on the Electronic Services Co-Chair page after following the steps to create a Work Group from the Template (CC 387).

6. Mark a file as ‘members only’ (CC 59).

7. Specified News items do not show up in the Work Group area (CC 438).

Conference Calls

1. Scheduling

10. Only co-chair and above (Board member, HQ Staff) should be allowed to schedule or edit conference calls. (CC 110)

1. Any user able to schedule calls can schedule calls for any other Work Group.

11. Provide the ability to secure conference calls based on user role

1. A secure call cannot be viewed by users below the minimum role for that call

1. Use Case

1. Board calls should only been seen by board members and HQ Staff

2. Co-chair calls should only be seen by co-chairs, board members, and HQ Staff

2. Even though a call is set to secure, if the user enters email addresses or a listserv with users that do not fit the minimum role, those users will still receive the reminder notices containing the call information, they just can’t see the call in the conference calling center

2. User can select a minimum role that can view the call

1. Role levels

1. HL7 HQ

2. Board

3. Co-Chair

4. Everyone (Default to this)

2. Users should only be presented with roles at or below their level

1. Use Case

1. A co-chair can only set a call to be Co-chair, member, or Everyone

12. Ability to schedule calls weekly, every other week, as well as monthly (CC 209).

13. User must select a Work Group to associate the call with.

14. User must supply the distribution list for the call by selecting either a listserv and/or enter email addresses for conference call reminders and notices to go to (CC 211).

1. Listserv should be a dropdown populated with the lists associated with the selected Work Group

1. A Work Group may have multiple listservs.

2. Listserv Work Group relationship needs an interface to maintain.

15. Call scheduling should show the user a confirmation screen that the call has been added.

16. After the title, have the Work Group appear when viewing the calendar (month view, week view, day view). In the day and week view, the phone number appears under the title; remove phone and replace it with the Work Group. (CC 382)

20. Editing

1. You can change basic information for an individual call, even if it occurs as part of a series of calls.

2. Ability to delete an individual call, series of calls, or an individual call within a series of calls.

1. Cannot delete calls that occurred in the past.

2. Upon cancellation an automatic reminder will go to the listserv the call was assigned to (CC 381).

3. If the call is modified after the call reminder has gone out, send an email reminder to the list associated with the call to let them know the new call information (CC 380).

1. Message should indicate that the call was updated.

4. Call editing/canceling should show the user a confirmation screen that the call has been updated/cancelled.

21. Viewing

1. Any user whose role is greater than or equal to the minimum role for the call can see the calls in the calendar as well as on their MyHL7 page

2. Only members can see the dial in and passcode information

1. Participants will still receive this information in the conference call reminder notices

3. Attached documents should appear when clicking a call item from the Work Group page (CC 43).

22. Reminders

1. Reminders should be sent out 3 days prior to the call (CC 377).

1. Configurable to allow administrator to change this value in the future.

2. If the call is scheduled or modified in less than the number days prior to send the reminder (less than 3 if reminders set to go out 3 days prior), send the reminder immediately (CC 380).

Document Management

1. Document Expiration

2. Ability to assign an expiry date to content.

3. Expired documents can be flagged as searchable or non-searchable.

23. Document Access

1. Be able to flag content access by working group.

2. Be able to flag document access by role (member, non-member, facilitator, board, etc.).

3. Supports Public vs. Private (members vs. non-member) control at Document and Directory Level.

Search

1. Search against predefined attributes.

4. External applications (.e.g, GForge, Project Insight, etc.).

5. Predefined content type (working group documentation, news, wikis, etc.).

1. Work Group should be a drop down of the available work groups.

6. “Sunset” documents (Expired documents).

24. Allows alternate sorting of search results.

25. Allow documents returned from searches to be downloaded with or without payment based on the status of the document and the membership status of the user.

26. Ability to return all documents or minutes for a particular Work Group (CC 22 & 155).

27. Advanced Search criteria results incorrect/inconsistent (CC 385).

1. Searches that didn’t work:

1. Keyword contains keyword;

2. Subject contains subject;

3. Name contains development projects;

4. Created by contains Test Admin;

5. Description contains development project;

6. Last Modified by System Account;

7. Title contains test;

8. Author contains Rudin

Administrative Interface

A challenge of our current website is that administration is difficult and requires a lot of manual intervention.

1. Administrative functions for all of the custom applications should be gathered into one master administration application.

28. Need to be able to easily go from any of the admin link pages back to the Admin ‘home’ page (CC 291).

29. Administrative area needs to be reviewed for security (CC 266).

1. Need to ensure that features in this area are not accessible by non-staff, even if they know the URL.

Development

1. Site wide error handler to trap errors.

2. User should receive an error notification message (“We’re sorry…”).

3. Email webmaster with error details.

30. All custom code must include automated unit test scripts.

-----------------------

Website Strategy

SharePoint/.NET Functional Requirements

Version 1.0

Health Level Seven

Last Updated May 30, 2008

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download