Discharge Data Manager (Public Service Administrator, Opt. 3)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Agency: Department of Public Health - Class Title: PUBLIC SERVICE ADMINISTRATOR - 37015 Skill Option: Management Information System/Data Processing/Telecommunications Bilingual Option: None - Salary: $8,571/month; Full Range $8,571-$12,651 /month - Job Type: Salaried Category: Full Time Number of Vacancies: 1 - Work Hours: Monday - Friday 8:30am to 5:00pm - Anticipated Hybrid Work Schedule Availability: 1 to 5 Days per week in office, depending on operational needs - Headquarters: Chicago - 115 S Lasalle St - Work County: Cook - Agency Contact: DPH.HRRecruiter@illinois.gov - Position Overview: Office: Transformation Bureau: Data and Informatics Division: Core Data The Illinois Department of Public Health seeks a detail oriented, self-motivated professional with excellent interpersonal skills to serve as Discharge Data Manager. Manages the intake of statewide facility discharge data from Illinois healthcare facilities, ensuring appropriate quality control and data security measures. Maintains detailed documentation of the system workflow, analyzes data, and provides discharge data to meet a variety of user needs. - Benefits Statement: list. - Essential Functions: list of duties. - Minimum Qualifications: requires knowledge, skill and mental development equivalent to completion of four (4) years of college. Requires prior experience equivalent to three (3) years of progressively responsible administrative experience in the field of information technology. - Specialized Skills: Requires three (3) years of experience in data intake methodologies, data systems development, data management and data dissemination. - Preferred Qualifications: list many specifics. - Conditions of Employment: driver's license, travel, revolving door restrictions, Statement of Economic Interest, etc. - About The Agency: description. - Why Work for Illinois? (maybe not needed as it's generic but could be considered Benefits? It's more about why work; but we may omit as it's generic fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Work for Illinois?" might be considered boilerplate? It's promotional but maybe keep? The instruction says include a section ONLY when posting has real, specific content for it. That section is somewhat generic but still specific to Illinois. However it's not about the role. Might be considered fluff. Safer to omit. We need sections: About the role (position overview), Responsibilities (essential functions), Requirements (minimum qualifications + specialized skills?), Qualifications (preferred qualifications?), Skills (maybe specialized skills?), Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections to include. We have: - About the role: Position Overview paragraph. - Responsibilities: Essential Functions list. - Requirements: Minimum Qualifications (college, 3 years experience) plus maybe Specialized Skills (3 years experience in data intake...). Could combine. - Qualifications: Preferred Qualifications (Master's degree, SQL experience, etc.) - Skills: Could be same as Specialized Skills? Might be redundant. Perhaps we can put Skills as the specialized skills list. - Benefits: Benefits Statement list. - Pay: Salary info. - Schedule: Work Hours and Hybrid availability. We must not include sections with filler like "commensurate with experience". We have concrete specifics. We must not include duplicated lines. We must not include application instructions, EEO, etc. We must not include Job ID etc. We must not include navigation/legal boilerplate. We must preserve all substantive information. Thus we need to extract substantive info and format. Let's gather: About the role (Position Overview): "Office: Transformation Bureau: Data and Informatics Division: Core Data The Illinois Department of Public Health seeks a detail oriented, self-motivated professional with excellent interpersonal skills to serve as Discharge Data Manager. Manages the intake of statewide facility discharge data from Illinois healthcare facilities, ensuring appropriate quality control and data security measures. Maintains detailed documentation of the system workflow, analyzes data, and provides discharge data to meet a variety of user needs." We could split into two sentences but keep as
. Responsibilities (Essential Functions): List: - Using independent judgment, using analytical and systems design capabilities, takes the lead in evaluating and implementing the Discharge Data Set. - Develops and implements reporting techniques to meet public information requirements of users. - Assists in coordinating the collection, review and maintenance of Patient Safety and Quality related data components. - Provides data compilation and analysis of confidential information to assist the Division staff in conducting local and state health research and planning activities. - Serves as working supervisor - Confers with management to analyze, plan and resolve problems related to streamlining data systems delivery. - Performs other duties as required or assigned which are reasonably within the scope of the duties enumerated above. We need to keep as
- .
Requirements (Minimum Qualifications + Specialized Skills?):
Minimum Qualifications:
- Requires knowledge, skill and mental development equivalent to completion of four (4) years of college.
- Requires prior experience equivalent to three (3) years of progressively responsible administrative experience in the field of information technology.
Specialized Skills:
- Requires three (3) years of experience in data intake methodologies, data systems development, data management and data dissemination.
We could combine into Requirements section.
Qualifications (Preferred Qualifications):
- Master’s Degree with emphasis in management information systems, data dissemination and data analysis.
- Three (3) years of professional experience with data intake and management using SQL. Skills in SQL include indexing and performance tuning ability to run SQL server complete, differential and transaction log backups.
- Three (3) years of professional experience with stored procedures, complex queries, correlated sub-queries, derived tables and Common Table expressions.
- Three (3) years of professional experience using healthcare administrative code (e.g., ICD-10CM) and CPT codes.
- Three (3) years of experience using statistical and/or informatics tools, preferably Excel, SAS or R.
- Three (3) years of professional experience using advanced methods of matching, linking and aggregating patient records from various data sources.
We could list as
- .
Skills: maybe we could treat Specialized Skills as Skills section. But we already used Specialized Skills in Requirements. Might be duplication. Perhaps better: Requirements = Minimum Qualifications; Skills = Specialized Skills; Qualifications = Preferred Qualifications. That seems logical.
Thus:
- Requirements: Minimum Qualifications (college, 3 years admin experience in IT).
- Skills: Specialized Skills (3 years experience in data intake methodologies, data systems development, data management and data dissemination).
- Qualifications: Preferred Qualifications (list).
Check if any content duplicated: Minimum Qualifications vs Specialized Skills vs Preferred Qualifications are distinct.
Now Benefits: list as given.
Pay: Salary: $8,571/month; Full Range $8,571-$12,651 /month.
Schedule: Work Hours: Monday - Friday 8:30am to 5:00pm; Anticipated Hybrid Work Schedule Availability: 1 to 5 Days per week in office, depending on operational needs.
We could also include headquarters location? Not a section; maybe include in About the role? Could add a paragraph about location? But we have no section for location. Could add a
- for any list of duties/requirements/benefits, and
for prose. So we can have
for prose not under a heading? Probably we should wrap prose under a heading. But we can also have
directly under a heading. For location info, we could add a
under About the role heading (makes sense). Or we could create a separate heading like "Location" but not in allowed list; better to incorporate into About the role. Similarly, Agency Contact maybe not needed; but it's substantive. Could add under About the role as well. We need to preserve all substantive info: includes Agency, Class Title, Skill Option, Bilingual Option, Job Type, Category, Number of Vacancies, Work Hours, Hybrid schedule, Headquarters, Work County, Agency Contact, Position Overview, Benefits, Essential Functions, Minimum Qualifications, Specialized Skills, Preferred Qualifications, Conditions of Employment (driver's license, travel, revolving door, Statement of Economic Interest), About The Agency, Why Work for Illinois? (maybe optional). Also includes "This position is a union position; therefore, provisions of the relevant collective bargaining agreement/labor contract apply to the filling of this position." That's substantive. We need to include all that. Thus we need to decide where to place each piece. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put many details under About the role as prose paragraphs (multiple
). That's allowed. Under Responsibilities we put Essential Functions list. Under Requirements we put Minimum Qualifications. Under Skills we put Specialized Skills. Under Qualifications we put Preferred Qualifications. Under Benefits we put Benefits list. Under Pay we put salary. Under Schedule we put work hours and hybrid. We also need to include Conditions of Employment (driver's license, travel, revolving door, Statement of Economic Interest, union position, collective bargaining, etc.) Where to put? Could be under Requirements? Or maybe under a separate heading but not allowed. Could add under About the role as prose. Also About The Agency description. Also "This position DOES contain “Specialized Skills” (as that term is used in CBAs)." Already covered. Also "Revolving Door" etc. Also "All applicants who want to be considered for this position MUST apply electronically..." that's application instruction, should be removed per instruction. Also "State of Illinois employees should click the link..." remove. Also "Why Work for Illinois?" maybe we can keep as prose under About the role? It's promotional but substantive. Might keep. We must remove duplicated lines: there are duplicates of Revolving Door etc. We'll include once. Now craft HTML. We'll start with
About the role
then series ofparagraphs. Paragraphs could include: - Agency: Department of Public Health. - Class Title: PUBLIC SERVICE ADMINISTRATOR - 37015 Skill Option: Management Information System/Data Processing/Telecommunications Bilingual Option: None. - Job Type: Salaried, Full Time, 1 vacancy. - Location: Headquarters Chicago - 115 S Lasalle St, Work County: Cook. - Work Hours: Monday - Friday 8:30am to 5:00pm; Anticipated Hybrid Work Schedule Availability: 1 to 5 Days per week in office, depending on operational needs. - Agency Contact: DPH.HRRecruiter@illinois.gov. - Position Overview: (the paragraph). - About The Agency: description. - Why Work for Illinois: paragraph. - Union position note: This position is a union position; therefore, provisions of the relevant collective bargaining agreement/labor contract apply to the filling of this position. - Conditions of Employment: Requires appropriate, valid driver’s license. Requires the ability to travel in the performance of duties
under About the role? Might be considered extra but not required. The instruction: preserve ALL substantive information. So we need to include location info somewhere. Where to put? Could add a
under About the role or maybe under a separate section like "Location". But we only allowed headings from list. Could we add a
without heading? Yes, we can have
elements anywhere. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
- for any list of duties/requirements/benefits, and