logo
    Abstract:
    Accurate coded diagnostic data are important for epidemiological research of stroke.To develop, implement and evaluate an online education program for improving clinical coding of stroke.The Australia and New Zealand Stroke Coding Working Group co-developed an education program comprising eight modules: rationale for coding of stroke; understanding stroke; management of stroke; national coding standards; coding trees; good clinical documentation; coding practices; and scenarios. Clinical coders and health information managers participated in the 90-minute education program. Pre- and post-education surveys were administered to assess knowledge of stroke and coding, and to obtain feedback. Descriptive analyses were used for quantitative data, inductive thematic analysis for open-text responses, with all results triangulated.Of 615 participants, 404 (66%) completed both pre- and post-education assessments. Respondents had improved knowledge for 9/12 questions (p < 0.05), including knowledge of applicable coding standards, coding of intracerebral haemorrhage and the actions to take when coding stroke (all p < 0.001). Majority of respondents agreed that information was pitched at an appropriate level; education materials were well organised; presenters had adequate knowledge; and that they would recommend the session to colleagues. In qualitative evaluations, the education program was beneficial for newly trained clinical coders, or as a knowledge refresher, and respondents valued clinical information from a stroke neurologist.Our education program was associated with increased knowledge for clinical coding of stroke. To continue to address the quality of coded stroke data through improved stroke documentation, the next stage will be to adapt the educational program for clinicians.
    Keywords:
    Thematic Analysis
    Stroke
    The professional literature concerning teacher evaluation is extensive, but the sources specific to documentation are relatively limited. Here is a practical synthesis of the relevant sources; the five types of documentation memoranda; and the leading lessons for doing documentation successfully.
    Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects' community positively impacted the documentation.
    Internal documentation
    Technical documentation
    Software documentation
    Code (set theory)
    Citations (115)
    ABSTRACT The documentation of seven academic institutional repositories (IRs) was compared and contrasted. This was followed by semi‐structured interviews with six practitioners experienced in the set‐up, management and maintenance of IRs, including representatives of three JISC FAIR projects. The aim was to identify the requirements of policy documentation provided by IRs. Although many issues were found to be handled differently, several common factors emerged. These included the importance of developing documentation in collaboration with academics, departments and senior management. Policies should be formulated only when the aims of the IR have been clearly defined and the documentation itself should be concise and understandable, with the rights and responsibilities of stakeholders clearly presented.
    Internal documentation
    Technical documentation
    Citations (22)
    Good documentation is crucial for frameworks to be used correctly. One important kind of framework documentation are tutorials. They tell how to use the framework and provide additional code examples. However, tutorials are rare compared to other kinds of documentation such as API documentation due to high creation and maintenance costs. In this paper we highlight the problems of writing and maintaining tutorials. Then we present the development environment for tutorials (DEFT), which provides support to address the identified problems.
    Technical documentation
    Code (set theory)
    Internal documentation
    Citations (8)
    Based on the development of China documentation from 20th century to this day,this article summarizes the three characteristics of the documentation research.This paper analyzes from the three aspects: the change of the visual angle,the view of integral documentation coming into being,the development of specialized documentation and research.In the end,the author gives some advices to the documentation developing for the future.
    Research development
    Documentation science
    Technical documentation
    Citations (0)
    It is acvantageous for standardized college documentation to quicken the velocity of documentation and improve the quality of document.The points to realize it read as follows:Ⅰ.Deepening secretary personnel's understanding about standardized college documentation.Ⅱ.Formulating relevant systems to aggrandize the control of documentation.Ⅲ.Strengthening technologic training and study.Ⅳ.Introducing advanced office equipment.
    Technical documentation
    Citations (0)
    Computational notebooks allow data scientists to express their ideas through a combination of code and documentation. However, data scientists often pay attention only to the code, and neglect creating or updating their documentation during quick iterations, which leads to challenges in sharing their notebooks with others and future selves. Inspired by human documentation practices from analyzing 80 highly-voted Kaggle notebooks, we design and implement Themisto, an automated documentation generation system to explore the Human-AI Collaboration opportunity in the code documentation scenario. Themisto facilitates the creation of different types of documentation via three approaches: a deep-learning-based approach to generate documentation for source code (fully automated), a query-based approach to retrieve the online API documentation for source code (fully automated), and a user prompt approach to motivate users to write more documentation (semi-automated). We evaluated Themisto in a within-subjects experiment with 24 data science practitioners, and found that automated documentation generation techniques reduced the time for writing documentation, reminded participants to document code they would have ignored, and improved participants' satisfaction with their computational notebook.
    Code (set theory)
    Internal documentation
    Technical documentation
    Software documentation
    Citations (6)
    Бұл зерттеужұмысындaКaно моделітурaлы жәнеоғaн қaтыстытолықмәліметберілгенжәнеуниверситетстуденттерінебaғыттaлғaн қолдaнбaлы (кейстік)зерттеужүргізілген.АхметЯссaуи университетініңстуденттеріүшін Кaно моделіқолдaнылғaн, олaрдың жоғaры білімберусaпaсынa қоятынмaңыздытaлaптaры, яғнисaпaлық қaжеттіліктері,олaрдың мaңыздылығытурaлы жәнесaпaлық қaжеттіліктерінеқaтыстыөз университетінқaлaй бaғaлaйтындығытурaлы сұрaқтaр қойылғaн. Осы зерттеудіңмaқсaты АхметЯсaуи университетіндетуризмменеджментіжәнеқaржы бaкaлaвриaт бaғдaрлaмaлaрыныңсaпaсынa қaтыстыстуденттердіңқaжеттіліктерінaнықтaу, студенттердіңқaнaғaттaну, қaнaғaттaнбaу дәрежелерінбелгілеу,білімберусaпaсын aнықтaу мен жетілдіружолдaрын тaлдaу болыптaбылaды. Осы мaқсaтқaжетуүшін, ең aлдыменКaно сaуaлнaмaсы түзіліп,116 студенткеқолдaнылдыжәнебілімберугежәнеоның сaпaсынa қaтыстыстуденттердіңтaлaптaры мен қaжеттіліктерітоптықжұмыстaрaрқылыaнықтaлды. Екіншіден,бұл aнықтaлғaн тaлaптaр мен қaжеттіліктерКaно бaғaлaу кестесіменжіктелді.Осылaйшa, сaпa тaлaптaры төрт сaнaтқa бөлінді:болуытиіс, бір өлшемді,тaртымдыжәнебейтaрaп.Соңындa,қaнaғaттaну мен қaнaғaттaнбaудың мәндеріесептелдіжәнестуденттердіңқaнaғaттaну мен қaнaғaттaнбaу деңгейлерінжоғaрылaту мен төмендетудеосытaлaптaр мен қaжеттіліктердіңрөліaйқын aнықтaлды.Түйінсөздер:сaпa, сaпaлық қaжеттіліктер,білімберусaпaсы, Кaно моделі.
    Citations (0)
    One major priority and responsibility of physical therapist educators today is to teach physical therapy students the purposes and the process of documentation. This article reviews the American Physical Therapy Association Documentation Guidelines.1 In addition, it systematically provides educational teaching strategies that assist in the development of documentation skills. Lastly, the article discusses documentation models.
    A definition is established for the terms 'Document' and 'Documentation'. The beginning of documentation has been a result of social forces. The genesis and the development of documentation are under the triangle of the three forces emanating from the great increase in the number of research personnel, in the output of research as documents, and in the inner urge of the library profession to give its best to the well-being of the society. Controversies about the agencies for documentation and about the techniques for documentation have been going on from the beginning of the century. Just now they appear to be nearing a satisfactory end. Incidentally India's role in this matter is mentioned.
    Technical documentation
    Internal documentation
    Documentation science