Title

User Type

Synopsis

User type essential: Explain Score user types, their user management authorization, and their restrictions on important aspects of CC, BIE, and Code List lifecycle.

Script

[Opening Scene]

Narrator: "In this video, we'll explore the different user types in Score, their roles, authorizations, and and restrictions regarding Core Components (CC), Business Information Entities (BIE), and Code List lifecycles."

[Scene transitions to the Score logo with a clean, professional background.]

Narrator: "Score classifies its users into two major roles: Developer and End-User. Users in each of these roles may have an additional admin authority. Let's delve into some details of the intention of these roles."

[Scene transitions to describe the developer and end-user roles.]

Narrator: "Developers, short for standard developers, are responsible for creating and revising the standard core components, including code lists. I should emphasize that the term core components include code lists. Developers also build and deploy releases and manage modules of these Core Components or CCs, for short. We should note that Core Components are also correspondingly classified in developer CCs and End User CCs. Developer users only manage only developer CCs and end-users only manage end-user CCs even though end-user CCs can use developer CCs. "

[Scene shows a developer working on CCs, deploying a release, and integrating code lists.]

Narrator: "Developers have full access to the lifecycle of Core Components, allowing them to create, modify, and deploy new versions as needed. They play a crucial role in maintaining the integrity and consistency of the standard."

[Scene transitions to an icon representing an End-User.]

Narrator: "End-Users take the developed releases and apply them to business operations within their specific contexts using Business Information Entities (BIEs). While they can import and utilize predefined code lists, End-Users use these lists for specific business purposes rather than as part of the standard itself."

[Scene shows an end-user applying BIEs in a business context and using code lists for specific operations.]

Narrator: "End-Users have restricted access to Core Components, focusing instead on implementing and customizing BIEs to suit their business needs. This distinction ensures that the core standards remain consistent while allowing flexibility in application."

[Scene transitions to an icon representing an Administrator.]

Narrator: "Administrators oversee the administrative functions within Score, such as account management and user authorizations. They ensure that users have the appropriate access levels and that the system operates smoothly."

[Scene shows an administrator managing user accounts and permissions.]

Narrator: "Administrators do not typically engage with the development or usage of standards directly but play a critical role in maintaining the system's infrastructure and user management."

[Scene transitions to a summary screen showing all three user types.]

Narrator: "In summary, Developers create and deploy standards, integrating code lists as part of the framework. End-Users implement these standards in business contexts using BIEs and utilize code lists for specific purposes. Administrators manage the system and ensure smooth operations."

[Scene transitions back to the Score logo with a final professional background.]

Narrator: "Understanding these user roles and their restrictions helps maintain the balance between standardization and practical application, ensuring Score remains an effective tool for data exchange."

[Closing scene with a call to action.]

Narrator: "Learn more about how Score can benefit your organization. Visit our website to get started."

[Screen fades to the website URL and contact information.]

[End of video]